Reference

Privacy Policy for galaxybet bet

Our Privacy Policy explains how galaxybet bet handles the data connected with your account, wallet activity and device access.

Account dataWallet recordsDevice choicesCookie controls
galaxybet bet Privacy Policy for galaxybet bet
CONTACT ROUTES

Privacy Help Through Your Account

A clear support path matters when your account data needs attention. Start with the support link shown after sign-in and describe the request in plain English, using the account phone number connected to the issue. For wallet questions, include the payment rail and reference shown in your cashier record, such as QRIS or DANA. We use those details to locate the correct record without asking you to send unrelated documents.

Team online

Account data request

Use the signed-in support route to ask for a copy of account data, explain the account phone number involved and tell us which record you want checked.

Wallet record check

For DANA, OVO, GoPay or QRIS concerns, share the visible transaction reference and payment date through support rather than posting wallet details in a public message.

Correction request

If your phone, name or contact detail is wrong, send the requested correction through account support. We may ask for an account step before changing the record.

HANDLING PRACTICE

Six Ways We Handle Your Data

Our handling process follows the purpose behind each account action rather than collecting details without a reason.

Account creation

When you open an account, we use the submitted contact details and phone verification result to create the account record and connect later sign-ins to the same profile.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us match a wallet request with your account without treating the reference as your full wallet balance.

Device signals

Your browser, device type, login time and network indicators may be recorded to protect account access. They help us examine unusual sign-ins without reading unrelated device content.

Cookie controls

Cookies can keep a session active and remember selected settings. You can adjust browser cookie controls, although blocking certain cookies may interrupt sign-in or account support steps.

Retention periods

We keep account, support and transaction records only for the period needed for their stated purpose, account administration or applicable legal duties, then remove or restrict them where appropriate.

Requesting changes

You can ask us to access, correct or clarify personal data through signed-in support. We may verify account ownership first so another person cannot alter your profile.

Privacy Policy Questions From Indonesia

These Privacy Policy answers focus on the account steps you are most likely to ask about before using galaxybet bet. We cover wallet references, device records, cookies, correction requests and account access in clear terms. If your question concerns a specific record, use the support route inside your account and mention the relevant date or payment reference.

It covers data connected with account creation, phone verification, sign-in, device access, support requests, cookies and wallet references. That can include DANA, OVO, GoPay, QRIS, bank transfer or virtual account records linked to an account action.

Device type, browser path, login time and network indicators can help us examine unusual access and protect your account. We use these signals for account security and do not treat them as permission to read unrelated content on your device.

Yes. Use the signed-in support route and state that you want to access your personal data. Include the account phone number and the record type, such as a profile detail, support message or QRIS transaction reference.

Send a correction request through account support and identify the field that needs changing. We may ask you to complete an account step or confirm the registered phone number before editing a name, contact detail or profile record.

Yes. It covers payment references and status details connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account requests. These records help us match a cashier action with your account and investigate a status question.

Cookies can support an active sign-in session and remember selected settings. You can manage them in your browser, but blocking required cookies may interrupt account access, phone verification or the support route used for a privacy request.

Raise the request through the support path shown in your signed-in account and identify the data concerned. We will assess the request against the record purpose, account needs and applicable requirements; access depends on local law.