Reference

kartu bet 88 Privacy Policy For Indonesia

kartu bet 88 Privacy Policy sets out how we collect, use and protect the details you provide when opening an account, signing in from mobile or checking wallet…

Account clarityWallet recordsMobile privacyLocal-law access
kartu bet 88 kartu bet 88 Privacy Policy For Indonesia
CONTACT THE POLICY TEAM

Three Ways To Ask About Your Data

A clear contact path helps you act on the Privacy Policy rather than guess what happens to your records.

Account privacy request Open the support route after login and state whether you want access, correction or…
Wallet record check For a DANA, OVO, GoPay or QRIS question, send the transaction reference and date.
Access concern If a sign-in or phone verification issue blocks your request, tell us the device…
SIX DATA COMMITMENTS

What We Keep Clear In Our Privacy Policy

We keep this policy practical by tying each data use to an account action you can recognise.

Account details

We may hold the name, phone number and sign-in details you submit during account opening. The phone verification step helps us connect the correct person to the account before protected records are changed.

Device signals

A mobile browser or desktop session can create technical signals such as browser type, session time and security events. We use these signals to protect access and diagnose an unusual login path.

Cookies

Cookies can keep a session active, remember a language choice and help us understand whether a page request completed. You can manage browser cookie settings, though some account steps may then need repeating.

Wallet matching

When you submit a DANA, OVO, GoPay or QRIS request, we retain the reference and status needed to reconcile the account event. Wallet passwords and private wallet login credentials are not requested by us.

Security controls

We use phone verification, session checks and request-level identity checks before releasing or changing protected account data. These controls can add a step when your device or sign-in pattern changes.

Retention requests

We retain records for the period needed for account support, security checks and legal duties. Ask us to correct or remove eligible data through the account support route; we explain any record we must retain.

Privacy Policy Answers For Your Account

These Privacy Policy answers address the account, device and wallet questions we hear before access is opened. Each answer points you toward a practical step, from checking a cookie setting to sending a verified request. If your situation is not covered, use the support route inside your account and describe the exact record or transaction you want us to check.

It covers account details, phone verification, sign-in activity, device signals, cookies, support messages and wallet transaction references. It also explains why we use each category, how long records may be retained and how you can request access, correction or deletion.

We use your phone number to create and verify the account, help protect sign-in and match a privacy request to the correct record. Before changing protected details, we may ask you to complete another verification step.

No. For DANA, OVO, GoPay and QRIS requests, we use the transaction reference, status and related account details needed to reconcile the event. We do not ask for your wallet password or private wallet login credentials.

Yes. Send an access request through the support route shown after login and include your verified phone number. We may confirm your identity first, then explain which account, device and transaction records can be provided.

Use the account support path and name the detail that is wrong, such as a phone number or profile entry. We may require phone verification before making the change, particularly when it affects account access or wallet matching.

We keep records for as long as needed for account support, security checks, payment reconciliation and legal duties. A deletion request does not always remove records that must remain for those purposes, and we explain the reason.

Yes, this policy describes the Indonesia-facing data path, including mobile browser access and local wallet references. Availability and eligibility depend on local law, so the account access conditions shown to you remain important.