Reference

Clear terms before account access

We keep the legal side clear before you open an account, so you can read the rules on access, data use, and request handling in plain English.

India lawData useRequest pathsAccount access

Explore the Lobby Read FAQ

What applies where local law permits

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

Our legal terms explain how access, account use, wallet actions, and record keeping work when local law permits service. We use the same plain language across the page so you can see what applies before you act, rather than hunting through hidden clauses. If a rule

1
changes because of your state, device, payment rail, or verification result, that change is shown in the right section instead of being buried elsewhere. For India, UPI, Paytm, and PhonePe entries are checked by the wallet system, and any request that needs extra confirmation stays pending
2
until the required check is complete. If you want a copy of your terms, a record of a request, or a correction to account details, our support desk can route it to the right team. We do not treat local-law limits as optional, and we apply
3
them whenever they affect access, retention, or contact handling.

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

CONTACT THE LEGAL DESK

How to contact our legal desk

If your question is about the wording of a rule, the path is simple: send it through chat, email, or phone and ask for the legal…

DATA AND ACCESS CARE

How we handle your data

We keep legal requests tied to your account so we can answer them with the right record set.

Data handling

We collect the details needed to run the account, answer requests, and meet local-law duties. That usually includes profile data, request history, and device markers used to spot unusual activity or duplicate access.

Cookies

Cookies help remember session state, language choice, and the path you used to reach the page. They also reduce repeated checks when you return, while still letting you clear them from your browser.

Account security

Changes to email, phone, or withdrawal details are treated carefully. We look for matching account signals before we accept an update, and we may ask for extra proof if the request looks unusual.

Retention

Retention depends on why a record exists. Some items stay only for account handling, while others remain longer for audit, dispute, or law. Once that purpose ends, we archive or remove them.

Request routing

You can ask for a copy of the data linked to your account, the status of a request, or the reason a change was delayed. We send the reply through the same contact path you used.

Corrections

If a detail is wrong, send the corrected version and any proof that helps us match the record. We update what we can, explain what must stay unchanged, and confirm the result in writing.

Questions on access and records

These answers cover access, data, corrections, and contact requests. They focus on what you can ask us to do, how local law changes the result, and where a request goes when it needs checking. If your case depends on your state, your device, or a record on file, we will say so directly rather than leaving you with a vague reply.

Yes. You can ask for the categories we hold, such as account details, device logs, and request history. If local law limits a specific item, we explain the limit and tell you what can still be shared.

Send the change through chat or email with the updated field and the account identifier you use here. We check the request against our records, then confirm once the change is applied or explain what needs more proof.

If access changes because local law changes, we apply the new rule only where it is valid. Your account record shows the result, and our support desk can explain what this means for your current access.

We keep records for as long as they are needed for account handling, dispute response, audit, or local law. After that, we archive or remove them according to the record type and the rule that applies.

The request reaches the team that handles that subject, and only staff who need it for the task see the details. We do not share the thread outside the handling path unless law or a formal request requires it.

Yes. Send the request through support, and we will confirm the steps that apply to your account and location. If any records must remain for legal or audit reasons, we explain that before the request is closed.

Access depends on local law wherever you are. If the service is not available in your location, we will say so in the access check rather than leaving you to guess.

Clear terms before account access

How to contact our legal desk

How we handle your data

Data handling

Cookies

Account security

Retention

Request routing

Corrections

Questions on access and records

01 Can I ask what data you keep?

02 How do I correct account details?

03 What changes if local law differs by state?

04 How long do you keep records?

05 Who sees my request?

06 Can I ask for account closure?

07 Can I use the service outside India?

Related Pages