Reference

ban99 Privacy Policy for Your Account Data

Our ban99 Privacy Policy shows what account, device, cookie and wallet data we handle when you create an account or enter the lobby.

Clear data purposesCookie choicesAccount contact pathIndonesia access
ban99 ban99 Privacy Policy for Your Account Data
CONTACT ROUTES

Questions About Privacy Policy? Contact ban99

A clear contact path matters when you want to ask about the Privacy Policy, correct an account detail or understand a wallet record.

Account contact Open the support route from your signed-in account when asking about the Privacy Policy. Include the email or phone detail linked to your account, but never send a password, wallet PIN or one-time security code.
Wallet records For a DANA, OVO, GoPay or QRIS question, share the payment reference and date shown in your account history. We can use that limited record to locate the transaction without requesting your full wallet credentials.
Access help If a phone verification step or browser session blocks your request, tell us whether you used mobile or desktop access. This gives our support team a practical route for checking the relevant account and device data.
DATA PRACTICES

Six Privacy Controls Behind Your Account

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

Data we collect

We may collect your account contact details, phone verification result, sign-in records, browser type, device signals, support messages and payment references. We collect these categories for account access, security checks, transaction matching and privacy requests.

Cookie settings

Cookies can keep your session active and remember choices made during a browser visit. You can adjust cookie controls in your browser, although removing some cookies may require you to sign in again before reaching the lobby.

Account security

We use phone verification before account access and examine sign-in or device signals for unusual activity. Keep your password and one-time codes private; our support route will not need those secret credentials to discuss this Privacy Policy.

Data retention

We keep account, security and payment records only for the period needed for the stated purpose, account administration, dispute handling or a legal duty. Retention can differ by record type and the local rules that apply to you.

Change requests

You can ask us to correct an account detail or clarify how a record was used through the signed-in support route. Include the affected field, your account contact and a short explanation so we can assess the request.

Privacy contact

Our support team is the first contact for Privacy Policy questions, data access requests and concerns about a wallet reference. We may ask for account verification before sharing account-linked data, protecting your details from an unverified requester.

Privacy Policy Answers for ban99 Accounts

These Privacy Policy answers cover the account actions you are most likely to question before opening an account. We keep the wording tied to real steps: phone verification, mobile browser access, cookie controls and payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account routes. If your request needs account-specific checking, use the support path after signing in where possible. Access and eligibility depend on local law.

The ban99 Privacy Policy covers data connected with your account, phone verification, browser or device session, cookies, support messages and payment references. It explains why we use those details for access, security, transaction matching and handling requests about your personal data.

We may collect the contact details you submit, the result of your phone verification, sign-in activity, device and browser signals, and records needed to match account actions. You should not send passwords, wallet PINs or one-time codes through a support message.

Yes. The Privacy Policy covers payment references connected with DANA, OVO, GoPay and QRIS, plus bank transfer or virtual account matching details. These records help us identify a transaction status without requesting your full wallet credentials or banking password.

Sign in and use the support route shown in your account, then identify the field you want changed and explain why it is incorrect. We may ask for account verification before making a change, so an unverified person cannot alter your details.

Cookies can keep a browser session active and remember selected settings while you move between account pages and rooms such as Auto Roulette. You can adjust them in your browser, but removing required cookies may sign you out or affect access.

Retention depends on the record and the purpose for keeping it. Account, security and payment references may remain for account administration, dispute handling or a legal duty, with the applicable period shaped by local law and the nature of the request.

Yes. Send your Privacy Policy question through the signed-in support route and ask for the privacy contact. Include your account contact and request type, but not secret credentials. We may verify account ownership before discussing account-linked data or making changes.