Reference

bolacc Privacy Policy For Your Account

Our bolacc Privacy Policy explains what account, device and wallet data we use when you open an account, sign in and access titles such as Live Casino or…

Clear data purposesWallet record contextAccount access choicesRequest path included

Explore Our Lobby Read FAQ

DANA And QRIS Data Rules

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

This Privacy Policy sets out how we collect, use, store and disclose data connected with your bolacc account. During account opening, we may receive your contact details, login activity, device signals and verification results so we can identify the account and protect sign-in. When you use

1
DANA, OVO, GoPay or QRIS, related reference codes, wallet status and payment timestamps help us match a transaction to your account without treating your wallet balance as a public profile. We may also record pages opened, including Live Casino, Wild West Gold or Basketball Betting, to
2
keep sessions working and address support requests. Where access or eligibility is discussed, it depends on local law. We may update this policy when our data practices change, and the current page will show the applicable wording. If a payment record needs checking, we use the
3
account path and transaction reference rather than asking you to send a wallet password.

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

PRIVACY HELP ROUTE

Privacy Help For Wallet Records

A clear contact path helps when a data question sits beside a payment question.

SECURITY PRACTICE

Aviator Data And Account Safety

We handle this policy area through practical account controls rather than broad promises. Sign-in events, phone verification and device signals help us detect unusual access, while payment references let us trace a…

Data we collect

We may collect contact details, verification results, device type, sign-in events, pages opened and payment references. These details support account access, security checks, transaction matching and responses to your requests.

Why we use it

We use account and device data to confirm access, identify suspicious sign-ins, connect DANA or QRIS activity to the right account and answer questions about a recorded transaction.

Cookies and devices

Cookies and similar device storage can keep a session active, remember security preferences and help us understand technical errors. You can manage browser storage, though some account functions may then need another sign-in.

Account security

Phone verification may be required before account access or a sensitive change. Never send us a password, wallet PIN or one-time code; our support path does not need those secrets.

Retention approach

We keep records for as long as needed for the stated account, security, payment or dispute purpose, then remove or de-identify them when retention is no longer needed.

Your request

You can ask what eligible data we hold, request a correction or raise a deletion question through account help. We may check identity and explain any legal or operational reason for keeping a record.

Privacy Policy Answers For Your Account

These Privacy Policy answers focus on the searches we hear around account opening, local wallets and device access. If your situation is different, use account help with the relevant reference or sign-in detail, and we will direct the request to the right data record.

It covers account details, phone verification, device activity, cookies, payment references and support records created when you use bolacc. It also explains purposes, retention, security steps and ways to request changes.

No. Our Privacy Policy does not require your DANA or QRIS PIN, wallet password or one-time code. We use transaction references, status and timestamps to match a payment with your account.

Device type, session details and sign-in events help us identify unusual access, protect your account and investigate a support case. These records can also explain why phone verification appears before access.

Yes. Use account help and state which detail is wrong, such as your contact record or verification detail. We may confirm account control before making a correction under the Privacy Policy.

Send a deletion request through the account help route with enough detail to locate your account. We will assess the request, verify control and explain if a payment or security record must remain.

Cookies or device storage may support sign-in, security preferences and technical continuity while you open Live Casino or Aviator. Browser controls can remove them, but another sign-in may then be required.

Yes. Access, eligibility, retention duties and some data requests depend on local law. Where local law permits, we will process an eligible request after confirming the account and request details.

bolacc Privacy Policy For Your Account

Privacy Help For Wallet Records

Aviator Data And Account Safety

Data we collect

Why we use it

Cookies and devices

Account security

Retention approach

Your request

Privacy Policy Answers For Your Account

01 What does the bolacc Privacy Policy cover?

02 Does the Privacy Policy store my DANA or QRIS PIN?

03 Why does bolacc record my device and sign-in activity?

04 Can I ask bolacc to correct my personal data?

05 How can I request deletion under the Privacy Policy?

06 Are cookies used when I open Live Casino or Aviator?

07 Does access to my data depend on local law?

Related Pages