Reference

Open the ban89 Privacy Policy Clearly

The ban89 Privacy Policy explains what we collect when you create an account, verify your phone, enter the lobby, or use DANA, OVO, GoPay and QRIS.

Account dataWallet recordsDevice accessCookie choices
Explore Our Lobby Read FAQ
ban89 Open the ban89 Privacy Policy Clearly
FIND POLICY HELP

Reach Support About Your Privacy

A clear contact path matters when a privacy question affects your account or wallet status. We keep privacy requests separate from ordinary lobby questions, while still giving you a practical route from the account area. Include the phone number linked to your account, the request you want handled, and any relevant DANA, OVO, GoPay or QRIS reference. Do not send a password or full payment credential. We may ask for an account check before discussing personal data.

Team online

Account contact path

Open the support contact route from your account area and select the privacy subject. Tell us whether you need access, correction or deletion, then include your registered phone number so we can locate the correct account record.

Wallet record query

For a DANA, OVO, GoPay or QRIS record, provide the transaction reference and approximate date rather than sending a wallet password. We use those details to separate a payment-status question from a request about the personal data attached to it.

Access recovery check

If you cannot reach the account area, use the login support route and state that your request concerns the Privacy Policy. We may verify account ownership through the phone step before revealing, changing or removing personal records.

DATA HANDLING

Explore How We Handle Your Records

Our privacy process follows the same account path you use to reach the lobby: identify the account, confirm the request, then apply the change or explain why a record must remain.

Account data use

We use your phone number and verification result to create and protect account access. Login events, device details and security signals help us detect unusual entry attempts. We do not need your wallet password to connect a payment reference with your account.

Cookie choices

Cookies and similar storage can keep a session active, remember selected settings and help us understand technical faults. You can manage available cookie choices through the site prompt or device browser controls, although blocking necessary storage may interrupt login.

Payment matching

A DANA, OVO, GoPay or QRIS receipt may be matched with your account reference so we can identify the correct wallet event. Bank transfer and virtual account records serve the same reconciliation purpose and are not treated as your wallet password.

Security protection

We limit account discussions until the phone or account check is complete. Keep your login details private and sign out on shared devices. If a login attempt looks unusual, we may pause the request while checking the account and device signals.

Storage and retention

We keep records only for the period needed for account operation, security review, payment reconciliation, dispute handling or a legal obligation. When a retention reason ends, records are deleted, anonymised or placed beyond routine account access where applicable.

Requesting a change

To ask who holds your data, correct an entry or request deletion, use the privacy contact route and describe the exact record. We may request identity and account confirmation, then explain the action taken or any reason a record must remain.

Browse Privacy Policy Answers for ban89

These answers address the questions we expect before an Indonesian account is opened or a wallet record is queried. They focus on the Privacy Policy rather than game selection, so you can understand the account data, device signals and payment references connected with your access. If your situation is unusual, use the privacy contact path with the smallest useful set of details.

It covers account details, phone verification, device and browser signals, cookie activity, security events and payment references. It also explains why we use those records, how long they may remain, and how you can request access, correction or deletion where applicable.

We use the phone number to create the account, complete the phone verification step and help protect login recovery. It also lets us match a privacy request to the correct account. We will not ask you to send your password with a privacy request.

Yes. The Privacy Policy includes payment references and status records connected with DANA, OVO, GoPay and QRIS. Bank transfer and virtual account references may also be recorded for reconciliation. These records help us investigate a receipt without requesting your wallet password.

You can request access by using the privacy contact route from your account area. State that you are making a Privacy Policy data request and include your registered phone number. We may complete an account check before sharing records linked to you.

Send a correction request through the privacy contact path and identify the inaccurate field, such as a phone number or payment reference. We may ask for account confirmation and supporting context before changing the record, then tell you what action was taken.

You may ask for deletion through the privacy contact route. We assess the request against active account needs, payment reconciliation, security checks and legal obligations. Where a record must remain, we explain the reason; otherwise, it may be deleted or anonymised.

Yes. Account access and eligibility depends on local law. The Privacy Policy applies to data handled through the service where local law permits. If a regional rule affects access or a request, we will explain the relevant account or data-handling position.

Related Pages

ban89 Indonesia FAQ Speed Blackjack Live Access guide European Football Odds