Reference

Privacy Policy for India accounts

UPI, Paytm, PhonePe and Google Pay details, account records and device signals all sit under this Privacy Policy, so you can see what we collect before you open…

Account dataPayment privacyCookie choicesRequest support
n00 Privacy Policy for India accounts
REQUEST ROUTES

Contact paths for privacy requests

Privacy questions should reach the right team without sending the same message again and again.

Privacy email Email our privacy team when you need access to account records, correction of saved details or deletion of data that is no longer required. We reply after we verify the account connection.
Account support chat Use chat for quick questions about cookies, device sessions or payment references shown on your account. The team can direct sensitive requests to privacy handling when identity checks are needed.
Payment data query For UPI, Paytm, PhonePe or Google Pay privacy questions, share the transaction reference and date only. We use that to trace logs without asking for full banking credentials.
CARE CONTROLS

How we handle your privacy choices

Our privacy work is built around clear records, limited access and prompt correction when something is wrong.

Account data

We store the details you provide during account setup, identity checks and support contact. These records help us confirm access, answer privacy requests and keep duplicate or unauthorised account activity under control.

Payment logs

UPI, Paytm, PhonePe and Google Pay activity may create references, timestamps and status records. We use them for reconciliation, withdrawal checks, dispute handling and security screening, not for selling your data.

Cookie choices

Cookies help keep you signed in, remember basic preferences and detect unusual device activity. You can manage browser settings, though some account and security functions may not work as intended without essential cookies.

Access security

We use login records, device signals and session checks to help protect your account. If we notice activity that does not fit your usual pattern, support may ask for verification before sharing privacy details.

Retention periods

Some records are removed when they are no longer needed, while others are kept for legal, tax, payment dispute or security reasons. The period depends on the record type and applicable local requirements.

Correction requests

If your email, phone, name spelling or payment reference is wrong, contact us with the correct detail and proof tied to your account. We update eligible records after identity checks are complete.

Privacy questions for India accounts

These answers explain how privacy requests work when your account includes gameplay, wallet activity and support contact records. They are written for practical account decisions, not legal jargon. If your question needs a personal response, contact us through the privacy email or support chat and we will handle it after verification.

It covers account details, login records, device signals, payment references, support messages and verification data linked to your profile. It also explains why we collect them, how long we keep them and when sharing may happen.

UPI, Paytm, PhonePe and Google Pay records may include reference IDs, status updates, timestamps and limited account matching data. We use these records for reconciliation, withdrawal checks, dispute handling and account security.

Yes. Send a request through the privacy email with your registered contact detail. We may ask for identity verification before sharing records, and we may exclude data that law or security rules require us to protect.

You can request correction of inaccurate details such as email, phone, name spelling or payment references. We may need supporting proof, especially where the change affects withdrawals, verification or account ownership.

You can ask us to delete eligible records. Some data may need to remain for legal, tax, payment dispute, fraud-prevention or security reasons, and we will explain the reason if retention applies.

Cookies and similar tools may remember sessions, device preferences and security signals. Essential cookies support login and account protection, while browser controls can limit non-essential tracking depending on your device settings.

Only teams that need access for privacy handling, verification, payment tracing or security checks can see the relevant records. Service providers may assist under limited access terms tied to the work they perform.