Reference

88bos Privacy Policy For Your Account

The 88bos Privacy Policy explains what we collect when you open an account, sign in, use DANA or QRIS, and contact our support team.

Account dataWallet recordsCookie choicesSecurity requests
88bos 88bos Privacy Policy For Your Account
CONTACT OUR TEAM

Privacy Policy Help Through Support

A clear contact path matters when you want to ask about the Privacy Policy or the information connected to your account. Start with our available support channel and include the email or phone detail used for account access, without sending a password or wallet PIN. We may ask for account-matching details before discussing personal records. This helps us separate a genuine request from an unauthorised attempt, including when a DANA, OVO or QRIS status question is attached to the same message.

Team online

Account access

If you cannot sign in, contact support through the available channel and state that your request concerns the Privacy Policy. We can explain the account-verification route and tell you which identifying detail is needed, while you should keep passwords, one-time codes and wallet PINs out of the message.

Data requests

For a copy, correction or deletion request, tell us which account detail is involved and use the contact path shown on the site. We may verify the request against your account before acting, particularly where the request also concerns a bank transfer or virtual account record.

Wallet records

When a privacy question follows a DANA, OVO, GoPay or QRIS transaction, include the transaction reference rather than your wallet credentials. Our team can use that reference to locate the relevant status record and explain whether the record can be changed or must be retained.

DATA CONTROL POINTS

How 88bos Handles Policy Requests

We handle the Privacy Policy as an account process rather than a general statement. Account details are used for the requested service, payment reconciliation, security checks and support handling.

Collection

We collect details you provide during account creation and phone verification, plus records created when you sign in, contact support or use the cashier path. Device and browser signals can help us identify a session, but they do not replace the account checks required before access.

Payment matching

A DANA, OVO, GoPay or QRIS reference helps us match a wallet status to the correct account. Bank transfer and virtual account records serve the same reconciliation purpose. We do not need your wallet PIN or banking password to investigate a payment reference.

Cookies

Cookies can preserve session settings and help the account path work across a mobile browser and desktop browser. You can adjust cookie controls in your browser. Blocking required cookies may interrupt sign-in, phone verification or the return from a payment page.

Account security

We use the phone verification step and sign-in signals to reduce unauthorised account access. If a device behaves unexpectedly, we may request another account check before discussing records or changing access details. Never share a password, one-time code or wallet PIN with support.

Retention

We retain personal and transaction records for the period needed to provide account support, investigate security events, reconcile payment status or meet applicable obligations. A request to remove data may therefore have limits where deleting a record would prevent an essential security or transaction check.

Change requests

To request access, correction or removal of eligible information, contact us through the support route and describe the exact record involved. We may confirm your identity first. Where local law permits, we will explain the result, any limitation and the next step available to you.

Privacy Policy Answers For 88bos

These Privacy Policy questions cover the account and payment situations you are most likely to encounter before or after opening access. We keep the answers focused on what we collect, why we use it, how you can request a change and what may happen when a record is tied to security or payment reconciliation. If your case is different, contact support with the relevant account reference.

The 88bos Privacy Policy covers account details, phone verification, sign-in records, device signals, cookies, support messages and payment references. It explains why we use those details for account access, security, payment matching and support, and how you can ask about eligible records.

We collect the details you enter during account creation and the information needed for phone verification before account access. We can also create sign-in, device and support records. We do not ask you to send a wallet PIN or banking password to complete a privacy request.

Yes. The Privacy Policy covers transaction references and wallet-status records connected with DANA, OVO, GoPay and QRIS. Bank transfer and virtual account references can also be included. These details help us match a payment event to the correct account without requesting private wallet credentials.

Use the available support channel and identify the account detail or record you want copied or corrected. We may verify your identity against the account before responding. Give a transaction reference when relevant, and do not include your password, one-time code or wallet PIN.

You can ask us to remove eligible information through support, where local law permits. Some account, security or payment records may need to remain for reconciliation, investigation or legal duties. We will explain what can be removed, what must remain and why the limitation applies.

Cookies can keep your session active and support the mobile path from sign-in to the lobby or cashier. You can manage them in your browser settings, but blocking required cookies may affect phone verification, account access or the return from a QRIS payment page.

Contact us through the support path shown on the site and state that your message concerns the 88bos Privacy Policy. Include the account email or phone detail used for access, plus a payment reference if needed. We may request an account check before sharing personal information.