Reference

cloudbet legal terms for India

This page explains how cloudbet handles access, data requests, cookies and account records for India.

India AccessLocal LawData RequestsCookie UseAccount Records

What this page covers in India

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

We keep this section plain: access depends on local law, and any service shown to you is available only where local law permits. If a rule in your state changes, or a device check shows a mismatch, we may restrict registration, login or other account actions

1
until the check finishes. We may also ask for details that help us confirm identity, protect the account and keep the records needed for dispute handling and legal duties. The data we hold is limited to what we need for those tasks, and we do not
2
keep it longer than needed. If you want a copy, correction or deletion request where that is allowed, use the contacts below and state exactly what you want changed. The payment chips here are only context for account handling on India-facing requests: UPI, Paytm, PhonePe and
3
Google Pay. When we update this page, we replace older wording with the current request path so you can act on the latest version.

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

REQUEST PATHS

How to send a request

If you need a copy of this page, want to correct an account detail, or need help with a request tied to access or retention, reach us through the channels below. We separate legal requests from routine account messages so your case lands with the right team. For anything urgent, write from your email on file and mention the state or country you are contacting from so we can find the record faster, check the right version, and reply with the right next step.

Team online

Email requests

Send correction, access or deletion requests from your email on file so we can match the account. Include your full name, state, and the exact change you want, and we will reply on the same thread.

In-account form

Use the contact form inside your account when you want a written trail. Add screenshots if a page shows older wording, and we will check the stored version before replying.

Postal contact

If a signed letter is needed, send it to our postal address listed in the account footer. Mark it for policy handling so the request reaches the team that handles records and access.

DATA HANDLING

Data, cookies and account security

We keep data handling narrow: only the details needed to run your account, check access, answer requests and record legal duties.

Data scope

We keep only the details needed to run the account, confirm access, handle requests and meet record-keeping duties.

Cookie state

Cookies help us remember session state, language choice and whether you have already seen a consent prompt.

Login checks

Account security starts with login checks, device checks and simple alerts when a new sign-in looks unusual.

Retention periods

Retention depends on the record type. We keep dispute files, request logs and mandatory account records only as long as…

Request changes

To change personal details, ask for a copy of your data, or request removal where allowed, write through the channels…

Single contact trail

For anything tied to access, cookies or stored account details, use one contact route only so the same case is…

Questions about access and records

These answers cover who can access the page, what data we keep, how cookies work, and where you can send a request. If your location or the law that applies to you changes, the answer may change too. That is why we keep this page short, current and tied to the account records we actually hold. If you need a copy, correction or deletion request, the support routes below are the right place to start.

Access depends on local law and the place you are connecting from. If your state or device location is not permitted, some actions may be restricted until the check is complete.

We keep the details needed to open, secure and service your account, plus the records needed for legal duties. That usually includes contact details, login history and request logs.

Yes. Send a clear request through the contact route linked on this page, and we will confirm what can be shared or changed under the rules that apply to your account and location.

Cookies remember session state, language choice and whether you have already accepted or changed a setting. They do not change the legal position; they only help the page and account work as intended.

We keep records only for the period needed to meet legal duties, settle disputes or protect the account. When that period ends, we remove or anonymise the data where the law allows.

Use the email, in-account form or postal route listed in the support section. Add your email on file and a brief message about the request so we can route it without delay.

If local law changes, we may adjust access, request handling or stored records to stay within the new rule set. We will rely on the latest page version and the contact route linked here.

cloudbet legal terms for India

How to send a request

Email requests

In-account form

Postal contact

Data, cookies and account security

Data scope

Cookie state

Login checks

Retention periods

Request changes

Single contact trail

Questions about access and records

01 Can I access cloudbet from India?

02 What personal data do you keep?

03 Can I ask for a copy or correction?

04 How do cookies affect this page?

05 How long do you keep records?

06 Where should I send a legal request?

07 What if the law changes after I open an account?

Related Pages