Reference

bolabareng slot Privacy Policy

bolabareng slot Privacy Policy explains what we collect when you open an account, sign in from a phone, or check DANA and QRIS status.

Account dataCookie choicesWallet recordsRequest changes
bolabarengslot.club page image
PRIVACY HELP

Browse support paths for privacy requests

A privacy question should not get lost beside a wallet query. From your signed-in account, use the support path and state whether you need a copy, correction, deletion request, or explanation of a cookie. Include the account phone number only through the protected form; never send a password or wallet PIN. Our team can use the account record and payment reference to locate the right request.

Team online

Account support form

Use the support form inside your account for a Privacy Policy request. Select the data topic, describe the change needed, and include only the contact details required to identify your account.

Login assistance

If you cannot sign in after phone verification, ask for privacy help through the account access route. We may request account details to confirm that the request comes from you.

Receipt matching

For a DANA, QRIS, or bank transfer question, attach the payment reference rather than a wallet PIN. This lets us check the relevant record while limiting unrelated account details.

HANDLING DETAILS

Explore how we protect policy choices

Privacy controls work best when each account step has a clear purpose. We separate sign-in verification from payment references, limit internal access to relevant records, and explain why a request may need…

Data collection

We collect account details you submit, phone verification results, device signals, support messages, and transaction references. We use each category for account access, request handling, security checks, or record matching.

Cookie settings

Cookies can remember a session and your selected privacy preference. You can clear them through your browser settings, although clearing session cookies may require another sign-in and phone verification.

Account security

We use phone verification before account access and may compare sign-in details with earlier device activity. Never share your password, one-time code, or wallet PIN through support messages.

Retention period

We keep account, support, and transaction records only for the period needed for the stated purpose, account administration, dispute handling, or a legal requirement. The applicable period can vary by record type.

Correction request

Ask us to correct an inaccurate phone number, contact detail, or account record through the protected support form. We may confirm ownership before changing information connected to wallet activity.

Access request

You can request a copy of personal data linked to your account and ask how it is used. Include the account contact route, and we will explain any identity check needed.

Check answers before opening your account

These Privacy Policy answers address the searches we hear before account creation. They cover the practical points that matter on an Indonesian phone: what we record, why wallet references appear, how cookies behave, and where to send a request. If your question is not listed, use the protected support path rather than sharing sensitive credentials in an open message.

It covers account details, phone verification, device signals, cookies, support messages, and transaction references. It also explains purposes, retention, security handling, access requests, and correction or deletion requests where local law permits.

Phone verification helps confirm that the person requesting account access or a data change controls the registered contact route. We use the result for identity checks and do not ask for a wallet PIN.

Transaction references and status information may be stored so we can match a wallet action to the correct account, investigate a receipt, or answer support. We do not need your wallet PIN for that process.

Cookies may remember your session and selected privacy preference. You can remove them in Android browser or iPhone Safari settings, but clearing session data can sign you out and trigger phone verification again.

Send a request through the signed-in support form and choose the data access option. State the account contact route, avoid passwords and codes, and complete any ownership check needed before we release account-linked data.

Yes. Use the protected support form to identify the incorrect contact detail or account field. We may compare your request with phone verification and wallet references before making a change.

Start from the support link inside your account and select the privacy topic. This route keeps the request connected to the right account record; access and any available action depend on local law.