Reference

Legal Terms for India Access

Open your account and we will show you the legal terms that shape access, identity checks, data use and record handling on a91.

Local lawIdentity checksRecord trailIndia access
a91 Legal Terms for India Access
REQUEST PATHS

Request Paths for Policy Help

If you need a legal change, contact us from the account email so we can match the request to your records. That path is used for access checks, correction requests, closure requests and disputes about how your data is stored. We keep the process written and traceable, so you have one place to follow up instead of repeating the same details across channels.

Team online

Written request

Send the request from the email linked to your profile. We use that step to confirm it is really you before we change account details, answer a data request, or note a closure instruction.

Account chat

Use the in-account chat when you want a same-thread record. It keeps the question, our reply, and any follow-up in one place, which helps when a legal request needs checking against earlier messages.

Escalation form

If a matter needs extra handling, submit the form and include the date, your account name, and the reason. That gives us enough context to route the request to the right team.

DATA AND ACCESS

Data, Cookies and Account Control

We handle policy data with the same checks we use for login and wallet actions.

Data capture

We record the details you submit, the time of the action, and the device used so we can keep your profile in order. That trail helps us answer legal queries and spot unauthorised changes.

Cookie use

Cookies help us remember session state, language choice and login timing. They also reduce repeated checks when you return, while still letting you clear the browser data if you want a fresh session.

Session security

We use password checks, session timeouts and device prompts to reduce the chance of account misuse. If your device looks unusual, we may ask for another confirmation before showing sensitive record details.

Retention period

We keep records for the time needed to run the account, settle disputes and meet legal duties. After that, we remove or anonymise what we no longer need, subject to any active request or hold.

Access requests

You can ask what we hold about you, and we will reply through the contact path tied to your account. If the request can be fulfilled, we will send the record after verification.

Corrections and changes

If your name, address or contact number changes, send the update request with supporting proof. We compare the new details against the existing record before we edit anything, which protects both you and the account trail.

Common Legal Policy Questions

These questions cover the parts people check before they continue: local access, record keeping, contact paths, and how we handle changes to account data. We keep the answers short so you can read the rule, confirm your position, and decide whether the site suits your location. When a rule depends on local law, we say so plainly and avoid vague wording that leaves you guessing.

Access depends on local law and is available only where local law permits. If your location does not fit the rule set, we will not invite you further and may block the session before any account action continues.

We use identity checks to protect account records, stop misuse, and make sure the person asking for a change is the same person named on the profile. The check also supports lawful handling of sensitive requests.

We keep the details you submit, login logs, device markers, support history and the audit trail around changes. We retain them only for the time needed to run the account, manage disputes and meet legal duties.

Yes. Send the correction request from the contact path tied to your account, then share the updated detail and proof if we ask for it. We compare the request against the current record before making any edit.

Cookies help us remember your session, keep the login state steady and reduce repeated checks. You can clear them in your browser, but that may mean you need to confirm the session again.

Use the in-account message path or the written request form, whichever matches the type of request. That keeps the trail attached to your profile so we can answer without asking you to repeat the basics.

If the law changes, we adjust access, record handling or contact steps to match the new rule. You may see a different path for the same action, and we will ask you to follow the updated process.