Reference

Legal terms for India accounts

This page sets out how your account, data and request handling work on goldbets.

India accessLocal lawData checksRequest handling

How access works where law permits

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

Access is not the same in every place. We make the account path available only where local law permits, and we may narrow or stop access when a rule, bank check or identity mismatch needs a pause. When you send a request, we look at the

1
location tied to your account, the records we hold and the legal duty that applies to that request. If a change needs extra review, we will ask for the missing detail before we move further. Payment chips such as UPI, Paytm and PhonePe may appear only
2
as context for eligible actions, and the set can change if a local rule changes. Nothing on this page creates access where the law does not allow it.

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

HELP PATHS

Where to send policy requests

If you need a correction, a copy of stored data or a location check, send the request through your signed-in account help form.

Account help form Use the form inside your signed-in account when you want a correction, a copy of stored data or a location check. It keeps the request linked to the right account and lets us track each step.

Written request If you need a record of the change, send a written request through the same channel and name the policy point clearly. We reply there so you can keep the thread with your account history.

Access check For a block, mismatch or consent concern, add your account details and the state you are writing from. That helps us answer under the correct local rule and avoid asking for the same detail twice.

DATA SHIELD

How we keep policy records

We collect only the details needed to run the account, answer requests and meet legal duties.

Data collection

We keep contact details, request history and verification records only when they are needed for account use, legal duties or a policy reply. We do not collect more than the task needs, and we avoid using the data for unrelated action.

Cookie use

Cookies help keep your session active, remember language choices and protect the account flow. They are used for access and site function, not for loose tracking that has no clear purpose on your side.

Account security

If a login looks unusual, we may ask for another check before changing anything. That helps prevent unauthorised edits, keeps your account details current and reduces the chance of a mistaken response.

Retention

We keep records only for as long as needed for dispute handling, audit, fraud checks and the legal duties that apply to us. After that, the record is removed or archived under the same rule set.

Contact route

Use the support route on this page for a legal question, a correction or a request to see stored data. We route it to the right team member and keep the thread tied to your account.

Change requests

If you want a correction, deletion or copy, tell us exactly what should change and why. We will review the request against the rule that applies to your location and reply through the same channel.

Questions about access and records

These questions cover the parts people ask us about most: where access is allowed, what we keep, and how to ask for a change. If your request depends on state rules or a bank-side check, we follow the rule that applies at the time you write to us. The same support route handles corrections, copies and access blocks, so your request stays in one thread.

No. Access depends on local law, and some states or territories may not permit the account path. If your location is not permitted, we do not make the service available there.

We keep only the details needed for account use, identity checks, request handling and legal duties. That can include contact data, session records, device logs and the history of changes you asked for.

Send the request through the signed-in support form, state the exact change and add any matching account detail we ask for. If we need another check, we will explain what is missing before we act.

Cookies keep you signed in, remember the language you chose and protect the flow against session mistakes. They support site function and account access rather than loose tracking with no clear purpose.

We keep records only while they are needed for disputes, audit, fraud checks or the legal duties that apply to us. After that period, the record is removed or archived according to the rule that applies.

Use the support channel on this page and mark the request as legal. The team will route it to the right person and reply through the same channel so you can track the thread.

Legal terms for India accounts

Where to send policy requests

How we keep policy records

Data collection

Cookie use

Account security

Retention

Contact route

Change requests

Questions about access and records

01 Can I open an account from any state?

02 What data do you keep about my account?

03 How do I ask for a correction?

04 Why do cookies appear on the site?

05 How long do you keep records?

06 Who can I contact about a legal request?

Related Pages