Reference

king88bet Privacy Policy For Indonesia Accounts

Our Privacy Policy explains how king88bet handles your account details, phone verification, device signals and wallet records when you use the site.

Account dataWallet recordsCookie choicesPolicy requests
king88bet king88bet Privacy Policy For Indonesia Accounts
REQUEST A CHECK

Get Privacy Policy Help Beside Your Account

A clear support route matters when a Privacy Policy question concerns your phone number, wallet record or login device. Sign in, open the account menu and use the support form; include the registered phone number and the request type so we can locate the correct record. If you cannot sign in, use the contact link on the access page and avoid sending a full password or wallet PIN.

Team online

Account support form

Use the signed-in account support form for a copy request, correction request or question about information connected with your king88bet profile.

Access page contact

If phone verification prevents entry, contact us from the access page with your registered number and device detail, without sharing your password or wallet PIN.

Cashier record check

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, quote the transaction reference so our team can check the matching account entry.

DATA HANDLING

Inside king88bet Privacy Controls

We keep this Privacy Policy practical by linking each data use to an account action you can recognise.

Data we collect

We may record your account name, phone number, verification status, device details, login events, selected settings and transaction references linked to DANA, OVO, GoPay or QRIS.

Cookie controls

Cookies can keep your session active, remember language or preserve a setting. You can review cookie controls in your browser and remove stored cookies from that device.

Account protection

Phone verification and device checks help us confirm account access. We do not ask you to place a password, wallet PIN or full payment credential inside a support message.

Retention period

We retain account, payment and support records for the time needed to operate the account, investigate unusual activity and meet applicable legal or accounting duties.

Correction requests

Ask us to correct an inaccurate name, phone detail or account record through the support form. We may request verification before changing information tied to your account.

Data questions

For a copy, deletion question or explanation of a record, contact us through the account path or access page and identify the email or phone detail on file.

Privacy Policy Questions From Indonesia

These Privacy Policy answers cover the account steps you are most likely to ask about before opening access. They also explain how to reach us about wallet records, cookies, device activity and corrections, with access handled where local law permits.

It covers account details, phone verification, device and login signals, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

We use your phone number to create and protect account access, complete a phone verification step and help locate the correct record when you request a Privacy Policy change.

We may record page and session activity, including visits to Sic Bo, Great Rhino or Mobile Legends pages, so we can protect access, diagnose errors and maintain accurate account records.

We retain payment references and status details needed to match an account transaction. We do not need your wallet PIN in a support message, and you can ask us to check a specific reference.

Yes. Send a copy or correction request through the signed-in support form, or use the access page if you cannot enter the account. We may verify your registered phone detail first.

Retention depends on the record and the reason it exists. We keep information for account operation, safety checks, support history and applicable legal duties, then remove or archive it when no longer needed.

Open the account menu and choose support, or use the contact path on the access page. Include your registered phone number and request type, but never include your password or wallet PIN.