Reference

Legal terms that shape your account

Before you open an account, we place our legal terms, privacy rules, cookie use, and account checks in one place so you can see how access works.

TermsPrivacyCookiesLocal law
betdaily Legal terms that shape your account
HELP CHANNELS

Ways to reach us on legal matters

If you want a copy of your data, a correction, or a question about how a clause affects your account, start with support.

Email Send legal requests from your registered email so we can confirm the account, then ask for a copy of records, a correction, or a closure step. We reply with the next action and any documents needed.
Live Chat Use chat when you need a quick read on a policy clause, a data correction, or a payment-name match. We ask only for the account details needed to route the request correctly.
Postal Mail If you prefer a written trail, send a signed request with your account name, registered email, and clear change request. We use it for record updates, retention questions, and formal replies.
RECORD SAFETY

How we handle your records

We keep legal handling simple: only the records needed for account use, request checks, dispute handling, and statutory duties stay in scope.

Data Use

We keep account, payment, and contact data only for legal handling, service delivery, and dispute records. When a request reaches us, we check the profile against stored details before we act on it.

Cookies

Cookies remember your sign-in state, language choice, and consent settings. They also help us spot unusual sessions so we can ask for another check before any sensitive account change.

Account Security

Protect your login with a unique password and a device you control. If you suspect access by someone else, contact support at once; we can pause changes while we verify the request.

Record Hold

We keep some records for a fixed period to meet legal duties, handle payment disputes, and answer audit questions. When the hold ends, we remove or anonymise the data where law allows.

Change Requests

You can ask to correct your name, contact details, or account settings by writing from the registered email address. We may need a match against stored records before we apply the change.

Contact Check

For access, correction, deletion, or a copy of your stored data, send the request to support and include enough detail to identify the account. We reply through the same route after verification.

Questions about your account rights

These answers cover how legal terms work for an Indian account, what data we hold, and how you can ask for changes. We keep the language short so you can find the right path quickly, but the local-law rule still applies to every request. If a regional rule changes, we follow the version in force for your account.

Access depends on local law and is available only where local law permits. If your region restricts a feature, we hide it or stop the action rather than route it through the account flow.

We keep the details needed to run the account, confirm changes, handle payments shown in the wallet, and meet legal duties. That usually includes contact data, login records, and request history.

Write to support from your registered email and ask for a data copy. We may ask for extra account details to confirm identity before we send the stored records.

Yes. Send the updated name, phone number, or email from the registered address, and we will check it against the stored profile before making the change. If we need more proof, we will tell you exactly what to send.

We keep records only as long as needed for legal duties, dispute handling, and account support. After that period, we delete or anonymise them where the law allows. The timeline can vary by record type.

Use support first, and mention the account email plus the action you want us to take. That helps us route the request to the right team and reply through the same channel.

Send a closure request from the registered email, and we will explain any retention duties before we close it. Some records may stay for legal reasons even after access ends.