Reference

Read the bos88 Privacy Policy

Our bos88 Privacy Policy explains what we collect when you open an account, use DANA or QRIS, and move between devices.

Clear data purposesWallet record contextAccount access requests
bos88 Read the bos88 Privacy Policy
CONTACT DATA TEAM

Use the right path for privacy help

A clear contact route matters when a phone number, wallet reference or device record needs checking.

Account support Use the account support route when you want to ask about stored profile details, phone verification records, login history or a correction to your registered contact information.
Privacy request Send a privacy request through the support contact path and state whether you want access, correction, deletion where permitted, or an explanation of how a particular record is used.
Payment reference For DANA, OVO, GoPay, QRIS, bank transfer or virtual account data, provide the transaction reference and date so our support team can locate the matching account record.
DATA HANDLING

Browse how we protect policy rights

We keep this policy practical by linking each data use to an account action you can recognise, such as signing in from a phone or checking a wallet reference.

Account details

We may collect your registration details, phone verification result and account contact data so we can identify the correct account when you sign in or ask for a privacy change.

Cookies and devices

Cookies and device signals can remember sign-in preferences, recognise a returning phone and help us investigate unusual access. You can manage cookie settings through your browser controls.

Security checks

Before changing personal data or discussing a wallet record, we may ask for account verification. We do not need your password in a support message, receipt or privacy request.

Record retention

We retain account, support and payment references only for the period needed for the stated purpose, account protection, dispute handling or a legal requirement that applies where you access us.

Access requests

You can ask what personal data we hold, request a correction or seek a copy through the support route. Include your registered contact detail so we can locate the record.

Policy contact

Questions about this Privacy Policy should identify the section or data type concerned, such as cookies, phone verification, device activity or QRIS payment references, for a focused response.

Browse bos88 Privacy Policy questions

These common questions focus on the records you create while opening an account, signing in and contacting support from Indonesia. We explain the practical route for access, correction and account-data questions, including payment references from DANA, OVO, GoPay and QRIS. If your request involves eligibility or a legal restriction, the outcome depends on local law.

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

We use phone verification to connect the correct person with an account, reduce mistaken access and respond to account requests. It can also help us check whether a login or data change needs confirmation.

Contact us through the account support route using your registered contact detail. State that you want an access request and name the records you need, such as profile, device, cookie or payment references.

Yes, you can ask us to correct inaccurate account or contact details through support. We may verify your account first, and any limitation on changing a retained record depends on local law.

Cookies may remember sign-in preferences and help connect activity to the right session. Your browser settings can control cookies, although changing them may affect account access or require you to sign in again.

We keep payment references needed to match an account action, receipt or status question. Send only the reference and date through support; never include your password or full private security details.

Send a deletion request through the privacy contact path and identify your registered account. We assess the request against account security, dispute handling and legal duties, with the result depending on local law.