Reference

Clear legal terms for India accounts

This page sets out how account use, data handling, cookies and verification work on 0qaa.

Local law firstID checksCookie useAccount records
0qaa Clear legal terms for India accounts
CONTACT PATHS

Ways to reach our policy desk

If you want to ask about access, correction, deletion or a complaint about how we handled your account, use the channels tied to your login.

In-account chat Use the chat inside your account for urgent legal questions, correction requests or a status check on an earlier ticket. We link the chat to your account so we can confirm who is asking before we share any personal data.
Email request Send a written request when you need a copy, a correction or a retention query. Written requests help us keep an audit trail and let us answer with the same record on file.
Contact form Use the form if you need to update contact details, raise a data concern or tell us that a local rule affects your access. We route the form to the team that handles account records.
DATA CARE

How we handle data and access

We keep this policy practical, not vague. Account records are used to verify access, settle disputes and meet legal duties, and cookie data is limited to session, security…

Data use

We use your account details to verify access, process requests and keep transaction logs aligned with the name on file.

Cookies

Cookie data helps us keep you signed in, remember language choice and block repeated login abuse.

Account security

We ask for step-up checks when sign-in patterns change, the device looks unfamiliar or a sensitive request lands on your…

Retention

We retain records only as long as we need them for legal duty, dispute handling and fraud control.

Who to contact

For access, correction or deletion questions, use the contact route tied to your account.

Change requests

If you want to update a name, email, address or transaction note, send a clear request with the matching account…

Common questions on legal use

These answers cover how access, data use and request handling work on 0qaa. If your case depends on local law, the local rule decides what we can do and which records we can keep. For anything tied to your account, use the contact route inside your login so the request reaches the right team with the right audit trail.

Yes. You can ask for the main account fields, transaction records and security logs linked to your profile. We share what the local rule allows and keep anything restricted only where law requires it.

We use cookies for sign-in, session control, language preference and abuse checks. We do not use them to reveal more than needed for the account action you are taking.

Send a correction request through the contact path on your account and include the field that needs fixing. If the change affects identity, we may ask for proof before we update the record.

Access can be limited if local law does not permit use, if identity checks are incomplete or if a security issue needs attention. We restore access when the issue is resolved and the record matches.

We keep records for as long as needed for legal duty, security checks and dispute handling. After that, we delete or anonymise them where the local rule and our internal process allow.

Only the team handling account records and legal requests sees it. We route each request by account reference so it does not get lost in a general inbox.