Reference

betindiaraces Terms and Conditions for Indian accounts

Clear account rules, local-law access, and wallet checks are set out here before you open your account.

Local-law accessAccount rulesWallet checksClause updates
betindiaraces betindiaraces Terms and Conditions for Indian accounts
SEND A QUERY

Where to send a query

Questions about a clause, access, or a change request can come through the channels below.

Email Send the page path, the clause heading, and the email on your account. We use that detail to find the exact rule, check the linked record, and reply with the wording that applies.
In-account chat Use in-account chat after login for questions tied to access, a change request, or a wallet trace. Keeping the thread inside your account helps us match the clause to the right record.
Request form The request form is for corrections, closure requests, and copies of the terms history we hold. We may ask for matching details before any change so the record stays linked to you.
DATA AND ACCESS

Data, cookies, and records

We treat this policy as part of the account record: limited to what we need, traceable, and linked to a real request.

Data use

We collect only the details needed to run the account, confirm requests, and keep a record of the terms you accepted. That can include login history, contact data, and wallet traces tied to UPI, Paytm, or PhonePe.

Cookies

Cookies help us keep you signed in, remember session choices, and spot a change that could affect access. If you clear them, some parts of the account flow may ask you to verify again.

Security

Protect your password, use a device you control, and tell us if you see a login you do not recognise. We may pause the account until the access path is checked and your details are confirmed.

Retention

We keep records for the time needed to run the account, answer a dispute, meet legal duties, and show the version of the terms that applied. After that, we remove or anonymise what we no longer need.

Change requests

If you want a correction, a closure, or a copy of the terms history linked to your account, send the request through support. We may ask for matching name, phone, or payment proof before we act.

Contact trail

For a clause dispute, send the page path, the heading, and a short note about what you want checked. That gives us a clear trail and helps us answer the exact term instead of sending a broad reply.

Questions on these terms

These questions cover how the terms work when you open an account, how local law changes access, what records we keep, and how you can ask for a correction or closure. If a rule depends on your region or on a wallet trace, we point you to the exact clause instead of sending a broad reply. That keeps the answer tied to the same record you used.

They apply when you open or use the site, and they stay in force until you close the account or access ends under this policy. If we post a change, the new wording applies from the stated date.

Yes. Access depends on local law and is available only where that law permits it. If a region has a different rule, that local rule comes first and may affect what you can open or complete.

We may ask for your name, phone, email, date of birth, device trace, or a wallet record when we need to confirm an account action. We only ask for what is needed to check the request.

We post the new text on this page and use that version from the effective date shown here. If an update changes how an account request is handled, the new clause governs future use, not past periods.

We keep records for the period needed to run the account, handle disputes, meet legal duties, and answer later requests about the terms you accepted. After that, we remove or anonymise what no longer serves that purpose.

Send the page path, the clause heading, and your question through support. That lets us answer the exact term, link it to your account if needed, and avoid a vague reply.