Reference

Privacy Policy For Your bolaselot Account

Our Privacy Policy explains how we collect, use and protect the details connected with your bolaselot account, including phone verification, wallet status and the device you use to…

Phone verificationWallet recordsDevice controlsCookie choices
bolaselot Privacy Policy For Your bolaselot Account
CONTACT ROUTES

Privacy Help Beside Your Account

A clear contact path matters when a privacy request concerns an account, wallet record or sign-in device. Use the support route shown inside your bolaselot account and include the phone number linked to the account, the subject of your request and any relevant payment reference. We ask for enough detail to locate the correct record, not for your password or a complete wallet credential.

Team online

Account privacy request

Send a request through the account support channel when you want to ask what personal details we hold, why a phone verification record appears or which account step created a particular record. We may ask you to confirm account ownership before discussing private details.

Wallet record question

For a DANA, OVO, GoPay or QRIS reference, include the date, amount shown in your account and the payment route used. We use those details to find the relevant record while avoiding unnecessary wallet credentials. Never send a password or one-time code.

Correction or deletion

Tell us which detail needs correction or which account record you want assessed for removal. We check identity first, then explain whether legal, security or transaction-retention duties require us to keep part of the record before we act where local law permits.

DATA PRACTICE

Six Practical Privacy Controls

Privacy is handled through ordinary account steps rather than hidden settings. We separate sign-in details, wallet references, device signals and support messages so each record has a clear…

Account details

When you open an account, we use the details needed to create and maintain that account, including your phone verification…

Wallet references

A DANA, OVO, GoPay or QRIS record can show a route, reference and status connected with your account.

Device and sessions

We may handle browser type, device signals, session times and sign-in events to keep your account session active and identify…

Cookies

Cookies can remember a session, preserve a selected setting and help us understand whether a page request completed.

Security steps

We may ask for phone verification or account details before disclosing private records, changing account data or discussing a withdrawal…

Retention and requests

We keep records only for the period needed for account operation, security checks, dispute handling and applicable legal duties.

Privacy Policy Questions From Indonesia

These answers address the privacy searches we hear most often before an account is opened or a wallet is connected. They cover phone verification, payment references, mobile sessions, cookies, retention and requests for access or correction. If your question concerns a specific account record, use the support route described above and avoid sending passwords or one-time codes.

The bolaselot Privacy Policy covers account details, phone verification, device and session signals, cookie choices, support messages and payment references. It explains why we use each category, how we protect account discussions and how you can ask for access, correction or deletion where local law permits.

Phone verification helps us connect a request with the correct account before we discuss private details or change account data. It can also help identify unusual sign-in activity. We do not ask you to send a password or one-time code through the privacy support route.

Yes. The Privacy Policy covers references and status records created when your account uses DANA, OVO, GoPay or QRIS. It can also apply to bank transfer and virtual account references. We use these records to match an account action and investigate an incomplete payment step.

We may handle browser type, device signals, session times and sign-in events connected with your account. These details help keep a mobile or desktop session working and help identify access that does not fit the account pattern. They are handled for account, security and session purposes.

Where local law permits, you can ask for access to personal details held about your account or request a correction. Use the account support channel and identify the record clearly. We may first confirm account ownership, then explain the result and any records that must remain.

The Privacy Policy does not treat every record the same way. We retain account, security, support and transaction references for the period needed for their purpose, dispute handling and applicable legal duties. If you request deletion, we explain when a legal or security reason requires continued retention.

Use the support route shown inside your bolaselot account and describe the privacy question in plain English. Include your linked phone number or a relevant DANA, OVO, GoPay or QRIS reference only when needed. Do not include your password, one-time code or full wallet credentials.