Reference

bolagg Privacy Policy For Your Account

Our Privacy Policy explains how bolagg handles the details you provide when creating an account, verifying your phone, entering the lobby, or checking DANA, OVO, GoPay and QRIS…

Account dataWallet recordsCookie choicesPhone checks

Explore Our Lobby Read FAQ

Open The Privacy Policy Before Account Access

bolagg Service availability depends on jurisdiction. Users are responsible for checking local law before access.

This Privacy Policy applies to information we receive when you open a bolagg account, complete phone verification, sign in from a mobile browser, or contact us about wallet status. We may handle account identifiers, device and session details, security events, support messages, and transaction references needed

1
to match a deposit or withdrawal request with your account. DANA, OVO, GoPay and QRIS can appear in payment records, while bank transfer or virtual account references may help us trace a cashier step. We use this information for account protection, payment reconciliation, service operation and
2
legal requests where local law permits. Access and eligibility depends on local law. The policy does not promise that every method or feature will appear for every account. You can ask us about the data connected to your account, request a correction, or ask how long
3
a record is retained through the contact path described below.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT ROUTES

Check Privacy Questions Beside Your Account

A clear contact route helps when a privacy question is tied to a real account step.

DATA PRACTICE

Explore How We Handle Your Privacy

Privacy work follows the same account path you see when moving from phone verification to the lobby or checking a wallet receipt.

Data we receive

We can receive details you enter during account creation, phone verification and support contact, together with session, device and transaction references generated while you use the account.

Cookie handling

Cookies and similar browser storage can keep a session connected and help us identify security events. You can clear browser storage, although this may require another sign-in step.

Account security

Phone verification helps connect account access to the registered contact. We also examine unusual session activity and may ask for account details before discussing private records.

Retention periods

We retain account, support and payment references for the period needed for service records, security checks or legal duties. Ask us which category applies to your specific record.

Corrections and changes

If your account detail is wrong, send the requested correction through support with the registered phone detail. We may verify the request before changing the stored record.

Deletion requests

You may ask whether a record can be removed. Some account, security or payment records may need to remain for legal or operational reasons, and we will explain the outcome.

Find Answers About Privacy Policy

These Privacy Policy answers cover the searches we hear most often before an Indonesian account is opened. They explain what happens around phone verification, wallet references, browser sessions and requests for account records. If your case involves a particular DANA, OVO, GoPay or QRIS transaction, include its reference when contacting us.

It covers account details, phone verification, browser and device session data, support messages, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account steps.

Phone verification helps connect a sign-in request to your account and supports security checks. We may use that detail when responding to a private data request or correcting account records.

Yes. The Privacy Policy covers payment references we receive for supported DANA and QRIS activity, along with OVO, GoPay, bank transfer or virtual account records used for reconciliation.

You can send a data access request through the account support path. Include your registered phone detail, and we may verify ownership before explaining which records are connected to your account.

Use the support route and describe the incorrect field clearly. Include the registered phone detail, but never send a password or security code; we may complete an ownership check first.

Cookies or browser storage can maintain a session and help identify unusual access. Clearing them may sign you out, so you may need to complete phone verification again.

You can ask us to assess deletion through support. We will explain whether the record can be removed, since security, payment reconciliation or legal duties may require certain records to remain.

bolagg Privacy Policy For Your Account

Check Privacy Questions Beside Your Account

Explore How We Handle Your Privacy

Data we receive

Cookie handling

Account security

Retention periods

Corrections and changes

Deletion requests

Find Answers About Privacy Policy

01 What does the bolagg Privacy Policy cover?

02 Why does bolagg need my phone verification detail?

03 Does the Privacy Policy cover DANA and QRIS records?

04 Can I ask bolagg for the data held about me?

05 How do I request a correction to my account data?

06 How does bolagg use cookies on my mobile browser?

07 Can I request deletion under the bolagg Privacy Policy?

Related Pages