Reference

v2026 Privacy Policy Explained Clearly

Our Privacy Policy explains how v2026 collects, uses, stores and protects the details you provide when opening an account or using the Indonesia lobby.

Account dataWallet recordsCookie choicesSecurity requests
Explore the lobby Read FAQ
v2026 v2026 Privacy Policy Explained Clearly
CONTACT THE TEAM

Three Ways To Ask About Privacy

A direct question is the quickest way to understand how the Privacy Policy affects your account. Tell us whether your request concerns phone verification, a DANA receipt, a QRIS transaction, a cookie choice or another stored detail. Include the account email or verified phone number when appropriate, but do not send a password or one-time code. We route privacy questions to the team handling account and wallet records.

Team online

Account desk

Use the account help route when you need to ask about phone verification, sign-in records or the personal details attached to your profile. We may ask you to confirm the verified phone number before discussing account data, which helps us avoid disclosing details to the wrong person.

Wallet checks

For a privacy question tied to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity, send the receipt reference and approximate time through support. We use those details to locate the relevant transaction record without asking you to share your wallet password.

Security channel

If you notice an unfamiliar device session or an unexpected account change, contact support through the account path as soon as possible. We can explain the security record, check recent access and tell you which verification step is needed before account changes proceed.

DATA CONTROL POINTS

Six Practical Privacy Safeguards

The Privacy Policy is connected to everyday account handling, not kept apart from it. We limit requests to details needed for account access, wallet reconciliation, security and support.

Account collection

We collect details such as your contact information, verification result and account activity when those details are needed to create or maintain access. Phone verification happens before account access, giving us a practical account step for confirming that the profile belongs to you.

Payment matching

A DANA, OVO, GoPay or QRIS reference lets us match a wallet event with your account without requesting the wallet login itself. Bank transfer and virtual account records are handled for the same reconciliation purpose, including checking a receipt or pending status.

Cookie settings

Cookies and similar session tools help keep your sign-in and page choices connected while you move between account pages. You can ask support what type of cookie is involved and request help with a choice that affects your browser session.

Device security

We may retain device, browser and session signals to identify unusual sign-in behaviour. If you switch from a mobile path to desktop and the account check changes, support can use the session record to explain the prompt and protect the account.

Retention timing

We keep personal and transaction records only for as long as needed for the stated account, security, support or legal purpose. A deletion or access request is assessed against active obligations, unresolved transactions and the reason the record was collected.

Change requests

You can ask us to correct inaccurate profile data, explain a stored record or raise a deletion request through support. We verify the requester first, then confirm what can be changed and whether an account or transaction record must remain.

Privacy Policy Questions For v2026

These answers address the questions we expect you to ask before opening an account or sending a wallet transaction. They cover the Privacy Policy, account access, payment records, cookies and requests for control over personal data. If your situation is different, contact us with a safe reference such as a receipt number rather than a password or one-time code.

The v2026 Privacy Policy covers account details, phone verification, device and session signals, wallet and bank transaction records, cookies, security checks, support requests and retention. It explains why we use each category and how you can ask about access, correction or deletion.

We use your phone number for account creation and verification before access. This step helps connect you with the correct profile and supports security checks when a sign-in or account change looks unusual. We do not need your one-time code in a support message.

Yes. The Privacy Policy includes transaction references and status details connected with DANA, OVO, GoPay and QRIS. It also covers bank transfer and virtual account records when those rails are used. We use these records to reconcile activity and answer receipt questions.

Contact our account desk and state that you are making a personal data request. Provide the account email or verified phone number when asked, plus a clear description of the records you want. We verify your identity before sharing account-related details.

You can request a correction or deletion through support. We first confirm which record is involved and verify the requester. Some account, security or transaction records may need to remain for an active purpose or applicable requirement; we explain the result and next step.

On mobile, cookies and session tools can connect your sign-in, account pages and preference choices. The Privacy Policy explains their role in the browser session. If a cookie prompt or setting is unclear, contact support with your device type and page path.

Use the security channel through your account support path and report the approximate time, device type and account change you noticed. Do not send a password or one-time code. We check the relevant session record and explain the verification needed to secure access.

Related Pages

v2026 Indonesia La Liga Match Bet About Us Balloon Mobile Play Account information