Reference

Legal Terms for Indian Access

This page explains how we handle legal terms, access conditions, account records and content use on g6pd.

Local lawData useCookie handlingRecord retention
g6pd Legal Terms for Indian Access
HELP CHANNELS

Where Legal Requests Start

For legal queries, send us the account email, the state or territory involved, and a clear description of the request.

Email checks Use the email linked to your account when you ask about consent, access, correction…
Chat desk For urgent legal flags, open chat and share your registered name, state and account…
Help form If you need a formal change request, submit the form with the account email…
DATA HANDLING

How We Handle Legal Records

We keep legal records narrow and specific: account creation data, consent logs, device signals, payment references and support transcripts only when they are needed for verification, disputes or audit trails.

Data scope

We collect only the details needed to run the account legally: name, contact route, device signals, transaction references and support history. We do not add extra fields unless a local rule or your request requires them.

Cookie use

Cookies keep your session signed in, remember language choice and help us spot unusual access. You can clear them in browser settings, but the next visit may ask you to verify again.

Account security

When you change password, device or payout details, we may ask for a one-time check before we accept the change. That helps us block unauthorised edits and keep the account history accurate.

Retention windows

We keep legal and tax records only for the period needed to meet local duties, resolve disputes or complete security checks. After that, we remove or anonymise them under our retention rules.

Verified contact

Use the support route linked to your account email for any legal request. If the message comes from a new address, we may ask for extra proof before we discuss your records.

Change requests

To correct, export or erase stored data where the law allows, state the request clearly and name the account details involved. We check the legal basis first, then send the next step in writing.

Questions About Access And Records

These questions cover the parts of the legal page most often used by Indian accounts: access permission, stored records, correction requests, cookies and the contact route. If your state or territory has a specific rule, that rule takes priority and we follow it before any general wording here. Keep your request linked to the account email so we can verify it faster.

Yes. If a state or union territory rule changes, we may pause access to the affected feature until the new rule is clear. We keep the account open only where local law permits and where our checks are complete.

We keep the records needed to run the account legally: identity details, consent logs, payment references, support history and security events. We do not keep extra data once the retention need ends, unless another law asks us to.

Send the request from your verified email and name the exact detail that needs correction. We compare it with the stored account record, then confirm the change or explain why a legal hold prevents it for now.

Yes, where local law allows. After we verify the account, we can share the data we hold, subject to any redaction needed for security, tax or another person's privacy.

Cookies help us keep you signed in, remember language choice and detect unusual access. If you clear them, you may need to verify again when you return or when a session expires.

Use the support path linked to your account email and include the state or territory, the request type and any reference number. That lets us verify the case and route it to the right team.

Where local law allows, yes. We first verify the account, then check whether we must keep any records for tax, dispute or security reasons before we act.