Reference

bisabet Privacy Policy For Your Account

The bisabet Privacy Policy explains how we collect, use and protect details connected with your account, from phone verification to wallet status for DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesContact requests
bisabet bisabet Privacy Policy For Your Account
CONTACT ROUTE

Ask About Privacy Before Account Access

A clear contact route matters when you want to ask about the Privacy Policy, correct an account detail or check why a wallet record is attached to your profile.

Policy question Send your question through the account support route and name the Privacy Policy section you mean. We can explain why a phone check, device signal or DANA receipt reference appears in your account record, without asking you to share a password.
Data correction If your contact detail or wallet status is inaccurate, tell us which account step needs correction. We may ask for a matching account detail before changing the record, helping us avoid altering DANA, OVO, GoPay or QRIS data for the wrong person.
Access request You can ask what personal details we hold and request a copy or deletion where local law permits. Include the account contact used for sign-in, and we will use the verification step to protect the request from unauthorised changes.
DATA PRACTICES

What Our Privacy Policy Covers Daily

We wrote this Privacy Policy around the account actions you actually take: opening access, checking a wallet, moving between the lobby and cashier path, and contacting us about a record.

Account creation

We collect the details needed to create and maintain your account, including contact data used during phone verification. That step helps connect your sign-in with the correct profile before you reach the lobby, and it gives us a clear account reference for privacy requests.

Wallet references

A DANA, OVO, GoPay or QRIS record may include a wallet name, payment reference and status rather than the full contents of your wallet. We use that data to match a receipt or pending status to your account and to investigate a cashier question.

Device signals

When you move from a mobile browser to desktop, we may record device and browser signals linked to account security. These signals help us recognise unusual access patterns and protect the account path; they are not a request for files stored on your device.

Cookie choices

Cookies can keep your session active, remember a selected page and help us understand whether a policy page loads correctly. You can manage browser cookie controls, although turning some off may require another sign-in before the Live Dealer Lobby opens.

Retention period

We keep account, support and transaction references only while they serve an account, security or legal purpose. When a record no longer has that purpose, we remove it, restrict its use or make it less directly connected with your account.

Change requests

To request access, correction or deletion, contact us through the account support route and identify the relevant profile detail. We verify the request first, then assess it under applicable law, including any reason a transaction or security record must remain.

Privacy Policy Answers For Indonesian Accounts

These Privacy Policy answers address the searches we expect before you open an account or connect a local wallet. We explain what we collect, how device access works, why phone verification appears and how to contact us about a record. Where a request depends on local law, we will assess it against the applicable rule and the account details available to us.

The bisabet Privacy Policy covers account details, phone verification, device and browser signals, cookies, wallet references, transaction records and support messages. It also explains retention, security handling and the steps for requesting access, correction or deletion where local law permits.

Phone verification connects your sign-in with the correct account before account access. We use it to reduce mistaken profile changes and help protect wallet status details. If you ask about the verification record, contact us through the account support route.

Yes. The Privacy Policy covers DANA and QRIS references such as a selected wallet, receipt reference and status. We use those details to match a cashier event with your account. We do not ask you to send a password through the support route.

We may handle browser and device signals connected with sign-in, session continuity and unusual access checks. These signals help protect your account when you switch from mobile to desktop. They do not give us a request to inspect unrelated files on your device.

Use the account support route and identify the contact detail connected with your profile. We verify that you control the account, then assess the request under local law. Where local law permits, we can provide the relevant personal data we still hold.

You can request a correction or deletion through the same account support route. Tell us which record is wrong or no longer needed. We may retain a transaction, security or legal record when applicable rules require it, even after another detail changes.

We keep records while they support account access, security, support handling or a legal need. After that purpose ends, we remove the record, restrict its use or reduce its direct link to you. The exact outcome depends on the record and local law.