Reference

Privacy Policy for angkabet88 Indonesia

angkabet88 Privacy Policy explains what we collect when you open an account, use DANA or QRIS, and access the lobby from your phone or desktop.

Clear data purposesWallet privacy detailsAccount request pathIndonesia access terms
angkabet88 Privacy Policy for angkabet88 Indonesia
PRIVACY HELP DESK

Where To Ask About Your Account Data

A clear contact route matters when a phone number, wallet reference or device record looks unfamiliar.

Account support path Open the support route after signing in and describe the Privacy Policy request in…
Payment record check For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account question, attach the…
Access request Ask us for the personal data connected with your angkabet88 account through support.
DATA CONTROL POINTS

What Our Privacy Policy Does With Records

We keep this policy practical: each data action should connect to account access, wallet reconciliation, security or a request from you.

Account details

We use your phone number, login identifier and verification result to connect you with the correct account. The clear phone verification step before account access helps us distinguish your request from an attempt made with someone else's credentials.

Device signals

When you move from a mobile browser to desktop, security records can show a device type, session time and connection signal. These details help us identify unusual access, protect the account session and investigate a login you do not recognise.

Cookie choices

Cookies can keep a session working, remember a language or connect a page to the correct account flow. You can manage cookie controls in your browser, although limiting them may require another login step before account details appear.

Wallet references

A DANA, OVO, GoPay or QRIS reference tells us which payment record needs reconciliation; it does not give us your wallet PIN. Bank transfer and virtual account references serve the same matching purpose when a receipt needs a status check.

Account security

We may ask you to confirm the phone linked to the account before discussing private records. Do not share your password, verification code or wallet PIN with support. That account step protects your data when a request arrives from an unfamiliar device.

Retention and changes

We keep records for as long as their account, security, dispute or legal purpose requires, then assess whether they can be removed or de-identified. You can request correction, access or deletion through support, subject to checks required by local law.

Privacy Policy Answers For Your Account

These Privacy Policy answers cover the searches we hear most often from Indonesia account holders. You can use the same signed-in support route for a personal request, a wallet record question or a concern about a new device. We may need to confirm your phone before discussing private account data, and access remains where local law permits.

The angkabet88 Privacy Policy covers account details, phone verification, device signals, cookies, payment references and support requests. It explains why we use each category, how we protect account access, how retention is assessed and how you can ask to see, correct or delete connected personal data.

For DANA or QRIS, we may store a payment reference, amount, status and time so we can match a receipt with the right account request. We do not need your wallet PIN for that check. OVO, GoPay, bank transfer and virtual account records follow the same purpose.

Yes. Send an access request through the signed-in account support path and identify the phone number linked to your account. We may ask for phone verification or another account step before sharing records, because the Privacy Policy must protect your data from a request made by another person.

Contact support from the account connected to the incorrect record and state what should change. Add the relevant DANA, OVO, GoPay or QRIS reference only when it helps locate the entry. We check the request against account details before making a correction or explaining why a record must remain.

Yes. Cookies can keep your mobile session connected, remember a language choice and return you to the correct account path. Browser controls let you limit them, but doing so may remove session continuity and cause another phone verification step before private account details are displayed.

We keep a record while it serves an account, security, payment reconciliation, dispute or legal purpose. We then assess whether removal or de-identification is possible. The exact period can differ by record type and local requirements, so you can ask support for the reason a particular entry remains.

You can submit a deletion request through the signed-in support route. We verify the account and assess whether the data is still needed for security, a payment record, an unresolved dispute or a legal requirement. Where local law permits, we remove or de-identify eligible records and explain any exception.