Reference

Privacy Policy For Your Account

goodbet Privacy Policy explains what we collect when you open an account, verify your phone, use DANA or QRIS, and move between the casino lobby and wallet area.

Account clarityWallet recordsCookie choicesPhone verification
Explore Our Lobby Read FAQ
goodbet Privacy Policy For Your Account
HELP WITH PRIVACY

Get A Clear Route For Data Questions

A privacy question should not leave you guessing which account screen to use. Our support path connects policy requests with the account-help route, so you can raise a correction, access or deletion…

Account access request Ask us what account details we hold and why they are used. We may ask you to confirm your phone or another account step before sharing a response, so a stranger cannot request private details through the support route.
Correction request If your phone, email or account record needs a change, send the existing detail and the corrected version through account help. We check the request against your account before updating the relevant record or explaining why a field must remain unchanged.
Wallet record question For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference, include the date and visible status rather than sending a full wallet credential. We can investigate the payment record while limiting the personal data included in your message.
DATA CARE DETAILS

Know What We Do With Your Details

Privacy is handled at the points where an account actually creates data: registration, phone verification, device sign-in, wallet activity and support contact.

Account data

We may collect the account details you submit, including contact information and phone-verification status. We use them to create access, respond to account requests and protect the correct account; we do not ask you to place private credentials in a support message.

Payment references

A wallet action can create a provider reference, amount, timestamp and status for DANA, OVO, GoPay or QRIS. Bank transfer and virtual account records can carry similar matching details. We use these records for reconciliation, status checks and account queries.

Cookies and sessions

Cookies can keep a session active, remember a selected setting and help identify unusual sign-in behaviour. On your browser or device, you can manage cookie controls, although restricting necessary cookies may interrupt account access or require another sign-in.

Security checks

When you sign in from a different phone or desktop, we may request an account step such as phone verification before revealing protected details. Keep your sign-in credentials private and contact account help if a device shows activity you do not recognise.

Retention approach

We retain account, payment and support records only for as long as they serve the stated account, security, dispute or operational purpose. When a record is no longer needed and no valid hold applies, our handling process removes or separates it from active use.

Policy changes

If a change affects how we handle your personal data, we place the updated Privacy Policy on this page and identify the effective point where applicable. Check this page before opening an account or after a material account-flow change.

Privacy Policy Answers For goodbet

These Privacy Policy answers focus on the questions that arise before account access, during phone verification and after a wallet record appears. If your situation does not fit one of these answers, use the account-help route with the smallest amount of personal detail needed to identify your request. We will confirm ownership before discussing protected data.

The goodbet Privacy Policy covers account details, phone verification, device sessions, cookies, payment references, support messages, retention and requests about your personal data. It explains how we use each category for access, security, status checks and account support where local law permits.

Phone verification helps us connect an account request with the person who opened the account and adds a check before protected details are discussed. We may use that step when you sign in on a new device or ask about a private DANA or QRIS record.

Yes. The Privacy Policy covers payment references created when you use DANA, OVO, GoPay or QRIS, including status, timestamp and matching details. These records help us investigate a receipt or cashier question, while wallet credentials should remain outside your support message.

Use the account-help route and ask for a data access request. Include the account email or phone reference, but do not send your password or full wallet credential. We verify ownership first, then explain which records can be provided under local law.

You can request a correction through account help when your contact or account record is inaccurate. Tell us the existing detail and the proposed correction, then complete any ownership check we request. We will update eligible data or explain the restriction under the Privacy Policy.

On mobile, cookies and related session tools can remember sign-in state, selected settings and security signals. You can manage browser controls, but blocking necessary cookies may end a session or require phone verification again. The Privacy Policy describes their role without treating cookie data as a public profile.

We keep payment and support records for as long as they support the stated account, security, dispute or operational purpose, subject to applicable requirements. The Privacy Policy does not promise one fixed period for every record; it explains when active use should end and removal can occur.

Related Pages

goodbet Indonesia goodbet Casino About Us Live Roulette Royal Access guide