Reference

Privacy Policy For Your got24 Account

got24 Privacy Policy explains what we collect when you open an account, sign in from a phone, or use DANA, OVO, GoPay and QRIS.

Clear data choicesWallet record contextAccount access help
got24 Privacy Policy For Your got24 Account
HELP WITH RECORDS

Three Ways To Ask About Privacy Policy

A clear request helps us find the right account record without exposing more of your details than needed. Use the contact route shown inside your account when you need a copy, correction or explanation of data connected with a wallet status, sign-in or support case. If you cannot sign in, describe the problem without sending your password or one-time code. We will use the account details you provide to check the request and respond through the available support path.

Team online

Account data request

Ask for the account details linked to your phone verification, sign-in history or support case. Include the contact detail on your account and the change you want, but never include a password or one-time code. We may ask for an account check before disclosing records.

Wallet record question

If a DANA, OVO, GoPay, QRIS, bank transfer or virtual account status looks wrong, contact us from the account support route. Share the transaction reference and date rather than a full wallet credential, so we can compare the record safely.

Sign-in privacy help

When your phone or device path stops at verification, tell us which step failed and whether you were using mobile or desktop. We can explain the Privacy Policy process and account checks while keeping your login secret out of the conversation.

DATA HANDLING

Six Privacy Policy Commitments Inside got24

Privacy controls work best when they follow the same steps you already take to reach the lobby.

Account details

We collect details you enter to create and maintain your account, such as a phone contact and verification result.

Device and sign-in signals

A mobile or desktop session may create technical records such as sign-in time, device type and security events.

Cookies and session tools

Cookies or similar session tools help keep your sign-in step, language choice and account route working.

Payment references

A payment record may include a rail name, reference, amount status and timing linked to your account.

Security and retention

We retain records only as long as needed for account security, support handling, dispute checks and applicable legal duties.

Changes and contact

To request a correction, ask about access, or query a Privacy Policy change, use the contact route available from your…

Privacy Policy Questions About got24

These answers cover the questions we expect before an account is opened or a wallet is connected. They focus on the records created by phone verification, sign-in, payment status and support contact, rather than describing the casino or sportsbook generally. If your situation is not listed, send a focused request through the account support route. Do not include passwords, one-time codes or complete wallet credentials in that request.

The got24 Privacy Policy covers account details, phone verification, sign-in and device signals, cookies, support messages and payment references. It explains why we use those records, how we protect access, when we retain them, and how you can ask for access or correction.

We use payment references and status details to connect a DANA, OVO, GoPay or QRIS event with the correct account and resolve a receipt or pending-status question. We do not need your wallet password or one-time code for that support check.

Yes. Send a correction request through the contact route shown in your account, identify the record or account step involved, and explain the requested change. We may complete an account check first so a private record is not disclosed to the wrong person.

Use the account support path to ask what personal records are connected with your account, including phone verification, sign-in events or a payment reference. Give us the account contact detail and request scope, while keeping passwords and one-time codes out of your message.

We keep account, security, support and payment-reference records only for the period needed for the stated account, security, dispute or legal purpose. The precise period can depend on the record and local requirements. You can ask support to explain the retention basis for your case.

Cookies support required sessions, sign-in continuity and account settings. Browser controls can limit optional cookies, but blocking required session tools may stop phone verification or wallet-status checks. Our Privacy Policy explains these uses, and support can help if a browser change interrupts your account path.

Access and eligibility depend on local law. Our Privacy Policy does not change those conditions. If you need to understand how a local access question affects your account data or support request, contact us through the available route without sharing confidential login details.