Reference

Privacy Policy for Your Account Data

This page explains how we handle your account details, device signals, cookies, and support messages when you use googlebet.

Account dataCookie useSupport recordsLocal law
googlebet Privacy Policy for Your Account Data
CONTACT ROUTES

Who Handles Privacy Requests

For access, correction, deletion, or a copy of your data trail, our support desk routes the request to the privacy queue.

Email Send your request with the account email, the change you want, and any date…
Live chat If you are already signed in, chat is the fastest way to flag a…
Request form Use the form when you want a written trail for access, correction, or removal.
WHAT WE KEEP

How We Handle Data

We keep the policy narrow and tied to account use. Identity details, cookies, device signals, and support messages are handled for security, fraud checks, and service history, while payment references are limited…

Data scope

We collect the details you enter, the device and browser signals needed to keep the session stable, and the support thread that proves what you asked us to do. We avoid extra fields that do not serve the account.

Cookie use

Cookies help us remember language, login state, and page flow so you do not repeat the same steps on every visit. You can clear them in your browser, but some forms may ask you to sign in again.

Account security

We check the email address, password, and matching account markers before we accept a sensitive request. That extra step reduces mistakes, keeps change requests tied to the right file, and protects you if someone else reaches your inbox.

Retention

We keep records only for the time needed to run the account, settle a dispute, or meet a legal duty. Once that period ends, we remove or anonymise the data so it is no longer tied back to you.

Change requests

If your name, contact route, or stored detail changes, send the request through support with the account email and a clear note. We update what we can after verification and tell you if a field must stay for legal reasons.

Contact trail

You can reach us through email or live chat when you want a copy of the data we hold or want to question a record. We keep the correspondence on file so there is a clear audit trail.

Privacy Questions We Handle

These are the privacy questions we hear most often from Indonesia accounts. We answer them in plain English, with the same rules for every request: verify the account first, share the minimum needed detail, and apply local law where it matters. If your concern is about cookies, retention, or correction, the same support path handles it and keeps the record attached to your file.

We keep the fields you submit, the device and browser signals needed to secure the session, and the support history linked to your account. We do not ask for extra details unless they help verify a request or resolve a dispute.

Yes. Cookies help us remember login state, language choice, and page flow, so the next visit starts faster. If you clear them, the site still works, but some settings and forms may ask you to sign in again.

We keep records only while the account is active, a dispute is open, or a legal duty still applies. After that, we remove or anonymise the file so it no longer links back to you.

Yes. Send the account email, the field you want changed, and a short note through email or live chat. We verify the file first, then update what we can and explain any field that must stay.

Only staff who need the data to run the account, check security, or answer your request can see it. We keep access narrow, and we log sensitive actions so there is a clear trail behind each change.

Yes. If access or eligibility is discussed, it depends on local law and is available only where local law permits. That rule also shapes what we can store, how long we keep it, and when we must decline a request.

Use email, live chat, or the request form from the support section. We ask for the account email and one matching detail, then route the case to the privacy queue and reply in the same thread.