Reference

Privacy Policy For Your Indonesia Account

Your account, wallet checks and device signals are handled under one privacy flow before you enter Live Football Odds, Sweet Bonanza or Rocket Crash.

Account data explainedDANA and QRIS contextCookie choicesSupport contact paths
king188 Privacy Policy For Your Indonesia Account
CONTACT PATHS

Reach Us About Privacy Requests

Privacy questions should reach the team that can read account records, not a generic inbox. Use the same phone number or email linked to your account so we can match your request to the correct profile. We answer through live chat, email and wallet-case follow-up, with identity checks before we discuss personal data.

Team online

Live chat privacy desk

Open live chat from the account menu between 09:00 and 23:00 WIB. Share your registered phone number and the privacy topic, then we route the case without asking for your password.

Email data requests

Send account-access, correction or deletion questions from your registered email. Include the last four digits of your phone number and payment rail used, such as DANA or QRIS, for matching.

Wallet case follow-up

For payment privacy questions, attach the transaction time, amount and rail name. We use those details to locate the wallet record, then reply with what data is stored and why.

ACCOUNT SAFETY

Data Controls Inside king188

A privacy policy only helps when the account flow follows it. We limit personal data to account operation, wallet verification, security checks, support handling and cookie preferences.

Account collection

We collect details you enter during account creation, including phone number, login name and contact email when supplied. That data supports login access, account recovery and privacy replies tied to you.

Payment records

DANA, OVO, GoPay and QRIS activity creates wallet references, timestamps and transaction status logs. We use those records to reconcile deposits, check withdrawal questions and answer payment privacy cases.

Device signals

Your browser, device type, IP signal and session time help us spot unusual access. If a new desktop login follows a mobile session, we may ask for account confirmation.

Cookie choices

Cookies keep your session active, remember basic preferences and help us measure page errors. You can clear cookies in your browser, though doing so may require a fresh login.

Retention approach

We keep data only for account operation, transaction checks, security records and support history. Retention periods may differ by record type because wallet disputes and access questions need traceable logs.

Change requests

Ask support to correct contact details, review stored account data or explain a record. We verify your identity first, then tell you what can be changed or removed.

Privacy Questions Before You Join

Before you open an account, you may want to know what happens to your name, phone number, wallet references and device data. These answers focus on privacy handling inside the account and payment flow, so you can decide what to share and how to contact us later.

We collect the details needed to create and protect your account, such as login name, phone number, contact email when supplied, device signals and session timestamps. We also keep wallet references when you use DANA, OVO, GoPay or QRIS.

We keep payment references so deposits, withdrawals and support questions can be matched to your account. The record usually includes rail name, time, status and transaction reference, not your full wallet password or private app login.

Yes, you can ask support for account data details where local law permits. We verify your identity through registered contact details first, then explain the main account, device, cookie and wallet records connected to you.

Cookies keep your session active, remember basic preferences and help us understand page errors. If you clear cookies on Chrome, Safari or another browser, you may need to log in again and reset some preferences.

You can request a correction through live chat or email using your current registered details. We may ask for wallet context, such as a recent QRIS or GoPay reference, before changing contact data.

Only the support and account teams assigned to your case should read the messages needed to answer it. We do not ask for your password, and we keep case details tied to the account record.

Retention depends on the record type. Account access logs, payment references and support cases may be kept while needed for security checks, transaction disputes, audit history and privacy request follow-up where local law permits.