Reference

goldbets Privacy Policy for Indian accounts

This page explains how we collect, use and store your details when you open an account, move money or contact our team.

IndiaAccount dataCookiesSecurityLocal law
goldbets goldbets Privacy Policy for Indian accounts
REQUEST ROUTES

Where to send privacy requests

If you want to ask how we hold or use your data, send a message through the contact path below and tell us which detail you want checked.

Email us Send the message from the email linked to your account and mention the detail you want changed, checked or removed. Add your mobile number or wallet reference so we can match the file without delay.
In-chat message Use chat when you need a quick clarification on how a record is held. Keep the same contact details in every follow-up so we can connect the thread to the right account.
Written request If you need a written trail, send a clear request with the time range and the record type involved. We will tell you what proof is needed before any update is made.
RECORD CARE

How we handle your records

We keep the policy controls around your account tied to the smallest set of records that still lets us process payments, answer requests and check misuse.

Data use

We collect the details you submit, plus technical logs from the browser and device, so we can run your account, match transfers and answer disputes. We avoid collecting extra fields that do not serve those tasks.

Cookies

Cookies help remember your session, language choice and basic site settings. You can clear them in your browser, but some pages may ask you to log in again or repeat a check.

Account security

Keep your password private and do not share one-time codes with anyone. If you spot a sign-in you do not recognise, change the password and contact us so we can check the record.

Retention

We keep records only for as long as we need them for payment checks, dispute handling, misuse control or legal duties. After that period, the file is deleted or stored without direct identifiers.

Change requests

If a detail is wrong, tell us exactly which field needs correction and send the matching proof. We will verify the file, make the change where allowed and confirm the action through the same channel.

Contact path

For any privacy request, use the contact route listed on this page. We answer after verification and keep the thread attached to the same account so your request does not drift across cases.

Privacy policy questions you may ask

You may want a quick read on how your records are used, who can see them and how you can ask for changes. These answers stay close to the policy itself: collection, cookies, retention, correction and contact steps. If local law needs a different process for a specific request, we follow that process for the related record. That keeps the answers focused on your data, not on general site use.

We collect the details you submit, plus device and browser logs that help us run the account, process requests and check misuse. We do not need extra fields that do not serve those tasks.

Cookies help remember your session, keep basic settings in place and reduce repeated checks while you move through the pages. You can clear them through your browser, though some functions may ask you to sign in again.

Only the staff and service partners who need the record for processing, support, misuse checks or legal duties can see it. We limit access by role and ask partners to handle the data under strict terms.

Yes. Tell us which detail is wrong, add the matching proof and send the request through the contact path on this page. We check the file first, then update the record where local law allows.

We keep records only for the time needed to run the account, settle payment checks, handle disputes and meet legal duties. After that, we delete them or keep only what cannot identify you directly.

Use the support route listed here and say which record or right you want to discuss. We may ask for verification before acting, so the request reaches the right file without delay.