Reference

bandungtoto88 Privacy Policy For Your Account

Our Privacy Policy explains what we collect when you open an account, sign in from a mobile device, or connect DANA, OVO, GoPay and QRIS.

Account dataWallet recordsDevice choicesPolicy requests
bandungtoto88 bandungtoto88 Privacy Policy For Your Account
POLICY HELP DESK

Get Privacy Policy Help Near Account Access

A clear contact route matters when you want to understand a record or correct an account detail.

Policy contact form Use our account contact form to ask which personal details are held, why a verification record is needed, or how to request a correction. Include your account identifier, but do not send a password, wallet PIN or one-time phone code in the message.
Site support chat Our site chat can explain where the current Privacy Policy is displayed and help you find the account route for a data request. For a request involving DANA, OVO, GoPay or QRIS, we may ask for a transaction reference rather than the full wallet details.
Account access route If you cannot sign in to submit a request, tell support the phone number linked to the account and the device path you used, such as mobile browser or desktop browser. We use those checks to reduce mistaken changes to another person’s account.
DATA HANDLING

How We Apply This Privacy Policy

The practical details below show how we handle common privacy questions across account access, wallet records and mobile browsing.

Account creation

When you open an account, we collect the contact details needed for account access and phone verification. We use them to connect your sign-in activity with the correct account, not to request your wallet password. Where local law permits, an incomplete verification step may limit access until the required detail is confirmed.

Wallet references

A DANA, OVO, GoPay or QRIS payment record can include a reference number, amount, status and time. We use that information to match a cashier event with your account. We do not need the private PIN used inside your wallet, and you should never place that PIN in a support message.

Device signals

A mobile browser may provide device, browser and session signals that help us identify unusual sign-in behaviour. The same applies when you move from a phone to a desktop browser before opening a room such as Lightning Roulette Room. These signals support account protection and are handled under this policy.

Cookies and choices

Cookies can remember a language choice, sign-in session or page preference so you do not repeat the same step on each visit. You can manage cookie settings through your browser, although blocking certain cookies may affect account access or the way a Privacy Policy request form works.

Retention periods

We keep account, security and payment-status records only for the period needed for the stated service, dispute handling or legal duties. When a record is no longer needed, we remove it or separate it from direct account details where our systems and legal obligations allow.

Change requests

To ask for a copy, correction or deletion of eligible personal data, contact us through the policy form or site chat after signing in. We may verify your phone-linked account before acting, and access to bandungtoto88 remains subject to local law and any record-keeping duty.

Privacy Policy Answers For Indonesian Accounts

These answers address the questions we hear before an account is opened or a wallet record is checked. If your situation is unusual, use the policy contact route with only the details needed to identify your account.

The Privacy Policy covers account details, phone verification, sign-in records, device signals, cookies, support messages and payment-status references. It also explains retention, security and requests for access or correction. The policy applies where local law permits service access and depends on local law.

Phone verification links account access to the contact detail you provide and helps us detect mistaken or suspicious sign-ins. We may use the verified phone route when handling a data request, but you should keep one-time codes private and should not include them in support messages.

No. A DANA, OVO, GoPay or QRIS record may provide a reference, status and time needed to match an account event, but your private wallet PIN is not required for that purpose. Never send a wallet PIN, password or one-time code through our contact routes.

Sign in and use the policy contact form or site chat, then ask for an account-data copy. Tell us the phone-linked account identifier and the records you mean, such as device sessions or wallet references. We may verify ownership before responding, where local law permits.

Yes, you can ask us to correct eligible account details through the same policy route. State which field is wrong and what should replace it; do not send extra identity documents unless support requests them. We may keep a change record when a legal or security duty requires it.

We retain payment-status records for the time needed for account security, dispute handling, service administration or legal duties. A record may contain a DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference. When no longer needed, we remove or separate it where permitted.

You can manage cookies in your mobile or desktop browser, but blocking session cookies may stop sign-in or prevent a policy request form from working correctly. Essential account and security functions may still require certain cookies, and your access depends on local law.