Reference

Open bon189 Privacy Policy Clearly

bon189 Privacy Policy shows how we use account details, phone verification records, wallet references and device data when you access our lobby.

Account dataCookie choicesAccess requests
bon189 Open bon189 Privacy Policy Clearly
CONTACT THE DESK

Switch To Support For Privacy Requests

A clear contact route helps you resolve a Privacy Policy question without sending sensitive details through a game chat. Sign in first when you can, describe the request, and include the phone number linked to your account only through our account support route. Our desk is available daily from 09:00 to 23:00 WIB through account chat and the support email shown in your account area.

Team online

Account chat

Use the signed-in account chat for a request about your profile, phone verification or a cookie setting. We can ask follow-up questions inside the same case and avoid placing account details in an open lobby conversation.

Support email

Send a Privacy Policy request to the support email displayed after login. Include the subject, account phone number and the change you need; do not attach wallet passwords, one-time codes or full payment credentials.

Status checks

If a DANA, OVO, GoPay or QRIS record looks unfamiliar, tell us the date, amount reference and wallet name through support. We compare the event with account logs and explain the next step without exposing another account's data.

HOW DATA WORKS

Browse Our Account Data Practices

Privacy Policy decisions affect the quiet details behind every login, from a cookie that keeps your session open to a security check that pauses an unfamiliar device.

Account records

We may store your phone number, login identifier, verification result and support messages to maintain account access. We use these records to answer your request and protect the account, not to publish your identity beside lobby activity.

Cookie controls

Cookies can keep a session active, remember a language choice and help us understand security errors. Your browser settings can block or clear them, although removing session cookies may require you to sign in again.

Device signals

We record practical signals such as device type, browser version, approximate network location and login time. These signals help us compare a familiar phone with an unusual sign-in and trigger an account check when needed.

Wallet references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity may leave a reference, status and timestamp in our records. We use that trail to reconcile account events; we do not need your wallet PIN.

Retention period

We keep data while it supports account operation, security, support or required record keeping. When a retention reason ends, we remove, anonymise or restrict the record unless another lawful need requires continued storage.

Request a change

You can ask us to access, correct or delete personal data where local law permits. We may verify your phone or account session first, then explain any data that must remain for security or required records.

Ask About bon189 Privacy Policy

These Privacy Policy answers address the searches we hear most often before account access: what we collect, how wallet references are used, whether cookies can be removed and where a request should go. Read them with the full policy and contact us when your situation needs an account-specific answer.

The Privacy Policy covers account details, phone verification, login and device signals, cookies, support messages and payment references. It explains why we use each category for access, security, support and record keeping, plus how you can request access, correction or deletion where local law permits.

We use a DANA or QRIS reference, status and timestamp to connect a wallet event with the correct account and investigate a missing or unfamiliar entry. We do not ask for your wallet PIN or one-time code, and support will never need those secrets.

Yes. Send an access request through signed-in account chat or the support email shown in your account area. We first confirm that you control the account, then explain the available records and any lawful reason a particular security or transaction record must stay restricted.

Session cookies help keep you signed in while moving between account pages and the lobby. You can clear or block them in your browser, but doing so may end the current session or remove a saved setting. The Privacy Policy explains the cookie purposes in plain terms.

We retain payment references, status details and related account records while they support reconciliation, security, support or required record keeping. Once the purpose ends, we remove, anonymise or restrict them unless applicable rules or an unresolved account matter requires longer retention.

Contact us from the signed-in account route and identify the field that needs correction, such as a phone number or profile detail. We may verify the request before changing it, and we will explain if a verification or transaction record cannot be edited.

You can request deletion through account chat or the support email listed after login, where local law permits. We verify the account first and review security, support and record-keeping needs. If some data must remain, we explain the reason and restrict its use.