Reference

bolagila Privacy Policy For Your Account

Our Privacy Policy explains how we collect, use and protect the details connected with your bolagila account, from phone verification to wallet status.

Account dataWallet recordsCookie choicesPolicy access
bolagila bolagila Privacy Policy For Your Account
CONTACT PATHS

Get Privacy Policy Help Inside Your Account

A clear support route helps when you want to understand a record rather than guess what it means.

Account request Send a Privacy Policy question from the support area after login.
Wallet record For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account query, include the…
Access concern If an unfamiliar device appears in your account history, tell us through the logged-in…
DATA PRACTICE

Six Ways We Handle Your Privacy

We keep the policy practical by tying each data use to an account action you can recognise.

Account details

We use your registered contact details and phone verification result to create, maintain and protect your account.

Device signals

Browser type, device markers and login events may be recorded to spot unusual access.

Cookie controls

Cookies can remember session settings and help the mobile browser path load the right account state.

Payment references

We retain payment references and status details for DANA, QRIS, bank transfer and virtual account activity.

Retention period

We keep each category only as long as needed for account service, security checks, dispute handling or legal duties.

Your request

You can ask what personal data we hold, request a correction or ask about deletion where local law permits.

Privacy Policy Answers For bolagila Accounts

These Privacy Policy answers address the searches we hear most often before account access. They explain what we collect, why wallet references appear, how cookies work on mobile and how to send a request without exposing sensitive credentials. If your question is not listed, use the logged-in support route and include only the details needed to locate your account.

It covers account details, phone verification, device signals, cookies, login events, support requests and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

We use the verification result to match you with the correct account, reduce mistaken access and respond to account requests. We do not ask you to place a wallet PIN in support messages.

Yes. The policy covers the mobile browser path, including session cookies, device signals and login events. Cookie settings on your phone may affect whether the account page remembers your session.

We use transaction references and status details to connect a DANA or QRIS event with your account, investigate a missing status and answer a support question. Wallet credentials are not needed for that check.

Yes. Send a correction request through the logged-in account support area and identify the detail that needs changing. We verify the requester first and handle the request where local law permits.

Retention depends on the data type and the reason it was collected. We may keep records for account service, security, payment disputes or legal duties, then remove or de-identify them when no longer needed.

Use the support path inside your account and include a relevant account or transaction reference. We can explain the request process, but you should never include your password, wallet PIN or full security code.