Reference

Legal terms for India account access

Our legal page sets out the terms, privacy handling, cookie use and account rules that apply when you deal with aagame.

India legal accessPrivacy rightsCookie choicesUPI contextSupport routes
aagame Legal terms for India account access
CONTACT ROUTES

Three contact paths for legal matters

Legal questions need a clear trail, so we separate them from routine account chat wherever possible.

Legal email Send formal privacy, terms or account-access queries by email so the full thread is dated and searchable. Attach only necessary files, hide unrelated banking details, and mention whether the matter concerns identity, data or eligibility.
Live chat handoff If you begin in chat, ask us to route the matter to legal support. The chat team can collect your account ID and issue summary, then move the case without asking for sensitive passwords.
Account document check When we need identity or ownership proof, we will tell you which document type is required and why. Send documents only through the account flow or the legal email route we confirm.
DATA PRACTICE

Six practices behind your legal rights

Our legal handling covers more than a terms page. It includes how we collect account details, how cookies support login safety, how payment references are stored, how long records are retained, and…

Account data

We collect the details needed to create and maintain your account, such as contact data, login records and account activity. Legal access to that data is limited to staff who need it for checks.

Payment references

UPI, Paytm, PhonePe and Google Pay references may be stored with wallet activity to match deposits or withdrawals. We use those references for reconciliation, dispute checks and lawful record keeping.

Cookie use

Cookies help us keep login sessions stable, detect unusual access patterns and remember lawful consent choices. You can manage cookies in your browser, though some account security functions may need them.

Security checks

We may require a one-time code, device confirmation or document check before changing sensitive details. These steps protect your account record and help us respond correctly to legal ownership requests.

Retention period

We keep account, payment and support records only for as long as needed for legal, dispute, tax, security or operational reasons. When retention is no longer required, records are deleted or anonymised.

Change requests

You can ask us to correct inaccurate contact details, update account data or explain a record we hold. We may verify your identity before making changes to protect the account history.

Seven legal questions before you join

These answers explain the legal points we are asked about most often before an account is opened or updated. They cover access, data rights, payment records, document checks, cookies and contact routes. If your issue involves a court order, regulator notice or law-enforcement request, use the legal email path so the matter is handled with a dated record.

Access depends on local law and is available where local law permits. We may restrict, pause or close access if your location, identity details or account activity does not satisfy the legal checks we apply.

We collect data needed to operate and protect your account, including contact details, login records, transaction references and support messages. We use it for identity checks, dispute handling, security monitoring and lawful record keeping.

Payment references help us match your wallet activity with the instruction received from UPI, Paytm, PhonePe or Google Pay. They also help us check disputes, confirm ownership and meet record-keeping duties.

Yes. Send the correction request with your registered contact details and supporting evidence. We may verify your identity first, then update the record where the evidence shows the stored detail is inaccurate.

Retention depends on the record type and the legal reason for holding it. Account, payment and support records may be kept for disputes, audits, security checks, tax needs or lawful requests.

Access may be paused if identity details are incomplete, location checks fail, payment ownership is unclear, misuse is suspected or a lawful request requires action. We may ask for documents before restoring access.

Cookies record session status, consent choices and security signals. You can adjust cookie settings in your browser, but disabling some cookies may affect login checks, account protection or proof of consent.