Reference

betindiaraces Privacy Policy for India

We set out how betindiaraces handles the details you give us when you open an account, send a payment, or ask us to check a request.

Account dataCookiesLocal lawSupport
betindiaraces betindiaraces Privacy Policy for India
CONTACT PATHS

Ways To Reach Our Privacy Team

If you want a copy of your data, a correction, or a deletion request, use the contact path that matches your account.

Privacy email Write to us when you want to check what we hold, correct a record, or ask how a payment reference is stored. We link the message to your account before any change.
In-account form Use the form inside your account for requests about access, removal, or contact changes. It helps us match your request with the right record without asking for extra details.
Chat handoff If you prefer chat, start there and ask for the privacy team. We move the thread into the right queue and keep the case attached to your account file.
STORAGE PRACTICE

How We Keep Records Safe

The policy works because each step leaves a clear trail. We record where the data came from, limit access to staff who need it, and keep payment references only as long as…

Collection

We only collect details you enter, plus device and browser signals needed for login, cookie control, and request handling. We do not add extra fields just to fill a record.

Cookies

Session and preference cookies help us keep you signed in, remember language choices, and spot errors when a page does not load as expected. You can clear them in your browser.

Security

Access to privacy records is limited to staff who need it for account checks, support work, or payment matching. We use protected connections when data moves between your browser and our systems.

Retention

We keep records for the period needed to run the account, answer disputes, and meet legal, tax, or audit duties. After that, we delete, mask, or archive them depending on the file type.

Access

You can ask what we hold, request a correction, or ask for removal where the law allows. We may ask you to confirm the contact route linked to the account before changing stored details.

Changes

If your phone number, email address, or payment route changes, send us the new details through the account channel. That helps us keep the privacy record matched to the right person.

Common Privacy Questions From You

These questions answer how we collect, hold, and share personal details tied to your account. If something in your record changes, use the same privacy contact path shown above, and we will check the request against your account before we act. When local law limits access, we follow that rule and explain what we can still share so you can plan your next step.

We collect the details you enter into the account forms, plus device and browser signals that help us keep login, session control, and cookie choices working. We keep the record tight and use it only for the reasons set out here.

Cookies help us remember your session, save simple preferences, and spot errors when pages do not load as expected. You can clear them in your browser, though some settings may need to be entered again after that.

When you send money through UPI, Paytm, PhonePe, or Google Pay, we keep the matching payment reference so the account record stays accurate. That helps us match credits, check withdrawals, and answer any privacy request tied to the transaction.

Yes. You can ask for a copy of the details we hold, request a correction, or ask us to remove items where local law allows it. We may ask you to confirm the contact route linked to your account first.

We keep records only for the time needed to run the account, answer disputes, and meet legal, tax, or audit duties. After that period, we delete, mask, or archive them depending on the file type and purpose.

If local law limits access, we follow that rule and only share the parts that are allowed. Where access is possible, we keep the request tied to your account and reply through the contact path you used.

Use the privacy email, the in-account form, or chat handoff shown here. Tell us what you want changed, and we will verify the request before we update the stored record or close the case.