Reference

Privacy Policy for India accounts

We keep your data, cookie choices and request paths in one Privacy Policy built for India, so you can see what we store and why in plain English.

Data useCookiesRetentionRequests
4c2 Privacy Policy for India accounts
REQUEST CHANNELS

How to reach privacy support

If you want to ask about your data, use the privacy mailbox, the in-account form or the help panel after login. Each path reaches the same team, but the in-account route helps us match the request to your profile faster and cuts back-and-forth. Where local law permits, you can ask for correction, deletion or a copy of the data we hold. Please share the email or number linked to your account.

Team online

Privacy mailbox

Write to our privacy address when you want access, correction, deletion or a copy of stored data. Include the email or phone on your account so we can match the request before we act.

In-account form

Use the form after login if you want the request tied to your profile. That path keeps the message linked to your account record and helps us answer without extra steps.

Help panel

If you are unsure which request to send, start in the help panel and choose the privacy topic. We route it to the same team that handles records, cookies and account changes.

DATA HANDLING

How we handle your data

Our privacy handling starts with data minimisation: we ask only for the details needed to open, secure and service your account.

Data we keep

We collect only the details needed to run the account, confirm identity, track consent choices and answer support requests. That usually includes contact details, login events, device signals and the record of any payment rail used.

Cookies and consent

Cookies and similar storage remember your session, language and preference settings. You can clear them in your browser, though some choices may reset until you sign in again and set them once more.

Security checks

Security checks help us stop unauthorised access. We may ask for a code, a device check or a document match before changing data, updating contact details or releasing sensitive account history.

Transaction logs

Transaction logs show the amount, status, time and channel for deposits or withdrawals. We keep those records because they help settle disputes, confirm balances and meet legal duties tied to the account.

Retention period

We keep support and account records only as long as needed for service, safety, tax or dispute duties, then delete or archive them according to retention rules that apply in your jurisdiction.

Request handling

If you want access, correction, deletion or a copy of stored data, send the request from your account or the email linked to it. We will reply with the next steps and any limits set by law.

Privacy questions you may ask

These answers cover the questions we hear most about data, cookies and request handling. They explain what we store, why some records stay longer, how you can ask for access or correction, and what happens when local law limits a request. If you need a faster route, send the request from the account that matches your email or phone number so we can verify it correctly.

It covers the data we collect, why we use it, how long we keep it, and how you can ask for access, correction or deletion. It also explains cookies, device signals and account security checks.

We may store your name, contact details, login history, device data, cookie choices and transaction logs linked to the account. We keep only the pieces needed for service, security and legal duties.

Cookies help remember your session, language and consent choices. They also help us spot repeated sign-in attempts and keep the account working properly across devices without asking you to reset everything each time.

We keep data only for as long as needed for the service, dispute handling, tax duties or security checks. After that, we delete it or archive it in line with the relevant rules.

Yes. Send the request from the account or contact address linked to your profile, and tell us what should change. We will verify the request before making corrections or sharing a copy.

Some requests can be limited by local law or required recordkeeping duties. When that happens, we explain the reason and keep the part that must remain, while acting on what can be changed.

Use the privacy mailbox, the in-account form or the help panel after login. Those paths reach the same team, and the in-account route is usually the fastest for account-linked requests.