Reference

Privacy Policy for India Accounts

This page explains what we collect, why we keep it, and how you can ask for a correction or removal.

IndiaUPIPaytmPhonePe
betandyou Privacy Policy for India Accounts
HELP CHANNELS

How to Reach Us About Data

If you want to ask what we hold, correct a field, or ask for deletion where the law allows, write through the channel that matches your…

Email request Send the request from your registered email and include the data area you want…
Chat If you are already signed in, use chat for quicker routing.
Web form Use the form when you want a clean written trail.
HANDLING STEPS

How We Keep Policy Handling Clear

We keep policy handling narrow and practical: collect only what is needed for account access, payment matching, support, and security checks.

Data scope

We keep to the details needed to run your account, such as name, contact fields, login events, and payment references. We avoid collecting extra fields unless you send them in a request or the law requires a check.

Cookie use

Cookies store session state, language choice, and basic security flags. They help us recognise repeat visits on the same device, keep the page stable, and reduce repeat verification prompts when your session is active.

Account security

We expect you to keep your password private and use a device lock where possible. If we spot a login from a new device, we may ask for extra checks before showing private account data.

Retention

We retain account and payment records only as long as needed for support, dispute handling, audit, and legal duties. When the retention period ends, we review the record and remove or anonymise it where allowed.

Access requests

You can ask for a copy of the data tied to your account, and we will send it after we confirm identity. If a law blocks release of a field, we will explain that limit.

Change requests

To correct a name, phone number, or address, send the updated detail from your registered contact point. We will update the record where possible and keep the prior value only if a rule requires it.

Questions About Data Use and Access

These questions cover the parts of our policy that matter most when you join, send a request, or want to know what we keep. We answer in plain English so you can see how access, correction, and retention work without legal jargon. If your case is unusual, send us the account details and we will point you to the right channel.

We collect the details you submit, such as name, contact fields, and login credentials, plus device and session data that helps us secure access. If you send a payment reference, we may store that too.

Device and login records help us spot unusual access, keep sessions stable, and trace account activity if you ask for support. We use them for security checks, not for unrelated profiling.

Yes, when those records appear in your account history, we may keep the reference, time, amount, and status so we can match the entry and handle support questions. We do not keep more than needed.

You can ask for a copy by sending a request through the channel linked to your account. We will verify your identity first, then share the record set we can provide under local law.

Yes. Send the updated name, phone number, or email from your registered contact point, and we will update the record after verification. If a field must stay unchanged for legal reasons, we will explain why.

Send a deletion request through email, chat, or the web form, and include the account reference so we can verify you. We will remove or anonymise data where local law allows and retention is no longer needed.

Access depends on local law and is available where local law permits. If a rule or location check affects your account, we may limit access until the check is complete.