Reference

Read balontoto Privacy Policy Before Opening

balontoto Privacy Policy shows how we collect, use and protect details connected with your account, device and wallet activity, including DANA, OVO, GoPay and QRIS steps.

Account dataWallet activityDevice controlsPolicy requests
balontoto Read balontoto Privacy Policy Before Opening
ASK ABOUT DATA

Contact Us About Your Privacy Policy

A direct support route helps when you need to understand a record, correct an account detail or ask why a wallet event appears in your history.

Account access If phone verification or a sign-in check is unclear, send the account support request from the help area. We explain which account detail is being checked and what you can do next.
Wallet records For DANA, OVO, GoPay or QRIS records, include the rail name and transaction reference shown in your account. We use that context to separate a payment status question from a data request.
Privacy requests Ask us to access, correct or clarify personal data through the same support path. We may check account ownership before responding, so your records are not disclosed to the wrong person.
HOW WE HANDLE IT

Explore balontoto Data Controls Clearly

We treat privacy as an account operation, not a detached page. Sign-in, phone verification, wallet status and device activity each have a practical reason for being recorded.

Collection purpose

We collect account details to create access, complete phone verification and maintain account records. Payment selections such as QRIS or bank transfer are used to connect a wallet event with the correct account.

Device signals

When you move from phone login to the lobby, we may receive device and connection signals related to that session. These signals help us identify unusual access without treating your device as a separate account.

Cookie choices

Cookies can remember session settings and help us understand whether a page request belongs to an active sign-in. You can manage browser cookie controls, although some account steps may then need to be repeated.

Account security

We use phone verification and account checks before discussing private records. Never send your password in a support message; we only need the identifying details required to locate your request.

Retention approach

We keep records for as long as needed for account operation, security checks, dispute handling and legal duties that apply where local law permits. Retention can differ by record type and account status.

Changes and contact

If your phone number, wallet detail or personal data needs correction, contact us through account support with the affected field. We may request an ownership check before applying or explaining a change.

Browse Privacy Policy Answers First

These Privacy Policy answers address the account, device and payment questions you are most likely to ask before opening access. If your situation is different, use the account support route and mention the specific record or verification step involved.

It covers account details, phone verification, device signals, cookies, wallet records and support requests connected with your access. It also explains purposes, retention, security checks and ways to request clarification.

Yes. The policy covers payment-rail details needed to match an account event, including DANA, QRIS, OVO, GoPay, bank transfer and virtual account records. We do not need your wallet password.

Phone verification helps connect account access with the person who opened it and supports account recovery or security checks. We may ask for an ownership check before discussing private account records.

It may include session, browser, device and connection signals linked to a sign-in. These details help us identify unusual access and keep a phone-to-lobby session connected to the right account.

You can ask for access, clarification or correction through account support. Include your registered phone number, the field or record involved and the relevant date; we may verify ownership first.

Retention depends on the type of record, account status, security needs, dispute handling and duties that apply where local law permits. Support can explain the reason for retaining a particular record.

Use the support path inside your account and describe the privacy concern in plain terms. For wallet records, add the rail name and reference; for access issues, include the phone verification step.