Reference

Your legal terms in one place

This page explains how bet24 handles access, account use, data, and request paths for India.

Local lawAccount useData useRequest paths

Browse Lobby Read FAQ

What applies to your account

bet24 Service availability depends on jurisdiction. It is the user's responsibility to check local law before access.

We keep our legal terms practical: they cover who may use the account, what data we collect, how records are kept, and how changes move through our support team. If a clause depends on state rules, identity checks, or payment verification, it applies only where local

1
law permits and only after the relevant check is complete. When you use UPI, Paytm, or PhonePe, the same recordkeeping rules apply so we can match a transaction to your account and answer a query later. If a rule changes, the version shown in your account
2
area or on this page is the one that counts for that moment. You can ask us to explain any clause in plain language before you act on it.

Service availability depends on jurisdiction. It is the user's responsibility to check local law before access.

CONTACT PATHS

Ways to reach the legal team

If you need a correction, a copy of your account record, or a question on how a clause applies, reach us through the registered-email route, the in-account message form, or the support…

Registered email Send the request from the email linked to your account so we can verify the sender, locate the record, and reply on the same thread with the exact clause or change path that applies.

In-account form Use the contact form inside your account for correction requests, policy questions, or a copy of stored account data. That keeps the message tied to your profile and helps us track the response.

Support mailbox If your query relates to access, local-law wording, or a transaction record, write the support mailbox shown in the footer and include the date, amount, and payment route used.

CARE AND RECORDS

How we handle policy data

We collect only the details needed to run your account, confirm transactions, and answer legal requests.

Data handling

We collect only the details needed to run your account, confirm transactions, and answer legal requests. That usually means registration data, device data, and selected payment records, never more than the task needs.

Cookies

Cookies keep your session active, remember language choices, and help us recognise the browser that last opened your account. Clearing them may sign you out and can reset stored preferences on the next visit.

Account security

Your password, device behaviour, and verification steps protect account access. If a change looks unusual, we may pause it until you confirm the request through the same contact channel linked to your profile.

Retention

We retain account, payment, and support records for as long as needed to meet legal duties, resolve disputes, and complete checks. After that period, the records move to archive or removal under our retention rules.

Change requests

If you want a correction, send the exact field, the reason, and any proof that supports the update. We will check what can be changed and tell you what must stay for legal or audit reasons.

Contact trail

Every request is logged with a time stamp, the channel used, and the account it relates to. That trail helps us answer later follow-ups and show which version of the wording applied at the time.

Questions about legal terms

These answers cover access, records, cookies, corrections, and the request paths tied to your account. If a rule depends on your state or on a payment check, we apply it only where local law permits and only after the relevant verification step is done. If the wording on this page and the wording in your account area ever differ, the in-account version for your current request takes priority until we update it.

Access depends on local law and on the details linked to your account. If a restriction applies in your state or to a specific payment path, we show that clearly before you continue.

We use account, device, and transaction data to run the service, verify requests, and keep records. We do not use more data than needed for those purposes, and we only share it when law or a service step requires it.

Yes. Send the request through your registered email or in-account form, and we will confirm the identity linked to the account before sharing the available record set and any limits that apply.

Cookies help keep you signed in, remember language choice, and link a session to the device you used. You can clear them in your browser, but some account screens may ask you to sign in again.

We keep legal, security, and transaction records for as long as needed to meet law, dispute handling, and audit duties. After that period, we archive or remove them according to our retention rules.

Write the account team with the exact field that needs changing, the reason, and any proof that supports the change. We will check the request, update what we can, and explain any part that must stay as it is.

Your legal terms in one place

Ways to reach the legal team

How we handle policy data

Data handling

Cookies

Account security

Retention

Change requests

Contact trail

Questions about legal terms

01 Who can use the account?

02 How do you use my data?

03 Can I ask for my records?

04 How do cookies affect access?

05 How long do you keep records?

06 How do I ask for a correction?

Related Pages