Reference

Privacy Policy For Your bias88 Account

Our Privacy Policy explains what we collect when you open a bias88 account, sign in from a phone, or use DANA, OVO, GoPay and QRIS.

Account dataWallet detailsCookie choicesAccess requests
bias88 Privacy Policy For Your bias88 Account
CONTACT YOUR WAY

Three Paths For Privacy Policy Help

A clear contact route matters when you want to ask about the Privacy Policy or change an account detail. Start from the support path linked near your account and cashier area, then include the email or phone number connected to your profile. If you are in Medan, the same request process applies as it does elsewhere in Indonesia, subject to local access rules.

Team online

Account request

Ask us to confirm which account details we hold, such as your contact record, sign-in history or verification status. Include the email or phone number tied to your bias88 account so we can locate the correct profile before discussing any personal data.

Wallet query

If a DANA, OVO, GoPay or QRIS receipt appears with the wrong status, send the transaction reference through our support path. We use the receipt details and account record together to check the issue without asking you to share a wallet password.

Policy contact

For a Privacy Policy question, request for a copy of stored data or correction request, contact our support channel from the signed-in account where possible. State the action you want, and we will explain the next verification step before making a change.

SIX DATA CHECKS

What We Do With Account Details

We keep the Privacy Policy practical by separating account operation from wallet credentials. Login events, device behaviour and verification steps help us detect unusual access, while cookie settings help remember choices on…

Account creation

When you open an account, we collect the details needed to identify the profile and send account messages. A clear phone verification step can be required before account access, helping us connect the right person with the right wallet and login record.

Sign-in security

We use sign-in records, device behaviour and verification signals to protect your account. A new phone or browser may trigger an additional check. These signals help us investigate unusual access without treating your device history as a public profile.

Cookie controls

Cookies can remember a session, language choice or security setting on your device. You can manage browser cookie controls, although switching them off may require you to repeat a login or verification step when returning to the lobby.

Wallet matching

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we use references and status data to match a payment with your account. We do not ask for your wallet password, card PIN or banking login through support.

Record retention

We keep account, support and payment-status records only as long as needed for service operation, security checks, dispute handling or legal duties. When a record is no longer needed for those purposes, our handling follows the applicable retention process.

Change requests

You can ask us to correct an inaccurate detail, explain a data use or consider deletion where applicable. Send the request through the signed-in account when possible; we may verify ownership first so another person cannot alter your profile.

Privacy Policy Questions From Indonesia

These Privacy Policy answers address the account and wallet questions you may have before opening access. We keep the wording direct so you can understand what happens when you sign in from a mobile device, select a local payment rail or ask us to change a personal detail. Account availability depends on local law.

The bias88 Privacy Policy covers account details, sign-in records, device signals, cookies, support messages and payment-status data. It explains why we use each category, how we protect it, how long records may remain and how you can contact us about access, correction or deletion where applicable.

Yes. Our Privacy Policy covers the payment references and status details connected with DANA, OVO, GoPay and QRIS. We may use those details to match a transaction with your account and investigate a receipt, but we do not need your wallet password or banking login.

We may collect the contact details you submit, account credentials, phone verification status, sign-in events and device security signals. The Privacy Policy also covers support messages and payment references connected to your account. We use these records for access, security, service communication and legal duties.

Contact support from your signed-in account where possible and ask for a copy or description of the personal data linked to your profile. Include the email or phone number on the account. We may request an ownership check before releasing details, and handling depends on local law.

You can request correction of an inaccurate account detail or ask whether deletion is available for a particular record. Send the request through the account support path and explain which data you mean. Some records may need to remain for security, payment disputes or legal duties.

Our Privacy Policy covers cookies and similar device storage used for sessions, security settings and remembered choices. You can manage these controls in your browser or device settings. If you clear them, you may need to sign in and complete phone verification again.

Use the support contact shown beside the account and cashier path, then describe your Privacy Policy concern in clear terms. For a wallet-status question, include the payment reference rather than a password. We will explain the verification step and route the request to the appropriate team.