Reference

Legal terms for your India account

Before you open an account, this page sets the rules that govern access, data use, wallet checks, and how we handle requests from India.

India accessData useWallet checksLocal law
dafabc Legal terms for your India account
REQUEST PATHS

Ways to send a legal request

For legal requests, use the contact path that matches your account. That helps us confirm identity before we share records, change details, or close an entry.

Email Send the request from your registered email and say whether you need a data…
Live Chat Use chat if you want a fast handoff.
Web Form If you prefer a written trail, fill the form with your account email, country…
DATA CONTROLS

How we handle data and records

We handle legal data with a narrow purpose: access control, payment checks, dispute handling, and messages you ask us to send.

Data Use

We collect only what we need to open, verify, and service your account: name, contact route, device signals, and payment traces. That keeps the legal record aligned with the wallet activity you ask us to process.

Cookies

Cookies remember your language, sign-in state, and session handoff across pages. They also help us spot unusual access. You can clear them in your browser, but some settings will need to be set again.

Account Security

We ask for matching details before any change to the account, payment path, or recovery route. That reduces misuse and helps us confirm that the request came from you, not from a copied message.

Retention

Records stay only for the time needed to run the account, answer disputes, meet legal duties, and handle payment checks. After that period ends, we remove or anonymise them where law allows.

Change Requests

If you want a correction, send the exact field and the new value from the contact linked to your account. We verify identity first, then update the record or explain any legal block.

Who To Contact

For access, data, or closure questions, use the support path in this page rather than a fresh message thread. That keeps the case together and makes it easier to confirm your identity.

Common questions on access and records

These questions cover how we handle access, records, cookies, and contact requests. We keep the answers narrow because legal rules change by region and by request type. If your question depends on local law, the answer may vary by where you are and what document you submit. Use the contact path tied to your account when you need a correction, copy, or closure. We reply through the same route so you can keep a clean trail of the exchange.

Access depends on local law and is available only where local law permits. If the rules in your region change, we may pause sign-in or some wallet actions until the position is clear again.

We keep the details needed to verify your account, handle deposits and withdrawals, and answer support requests. That can include name, contact route, device data, and payment traces from UPI, Paytm, or PhonePe.

Yes. Send the request from your registered contact path and tell us what copy you need. We may ask for extra proof to confirm identity, then share the record we can lawfully provide.

Cookies keep the session stable, remember language and device choices, and help us spot account misuse. You can clear them in your browser, but some page settings may need to be set again.

We keep records only for the period needed to run the account, resolve disputes, meet legal obligations, and finish payment checks. Once that period ends, we delete or anonymise data where law allows.

Use the support path tied to your account and tell us what to change. We may verify identity first, then update the record or close the account when the request matches the legal rules.