Reference

bimaspin Privacy Policy For Your Account

The bimaspin Privacy Policy explains what we collect when you open an account, use the Live Dealer Lobby or check a DANA, OVO, GoPay or QRIS transaction.

Account dataWallet recordsCookie choicesSecurity requests
bimaspin bimaspin Privacy Policy For Your Account
HELP WITH PRIVACY

Get A Clear Route For Privacy Requests

A clear contact route helps you act on the Privacy Policy without guessing which team to reach.

Account access questions If you cannot reach your account or need to understand a verification record, contact…
Wallet record checks For a DANA, OVO, GoPay, QRIS, virtual account or bank transfer record, send the…
Privacy change requests To request a correction, removal where available or a copy of your stored details…
CONTROL YOUR DETAILS

Know What We Store And Why

The Privacy Policy gives you a practical view of the records behind account access rather than treating privacy as a general promise.

Account creation

When you open an account, we collect the details needed to create and protect that profile. Phone verification can be part of the access path, and we use the result to reduce mistaken identity when you return from a mobile browser or another recognised device.

Device behaviour

A browser or phone may send technical details such as session signals, language settings and error data. We use these details to keep the lobby reachable and investigate failed access; they are not a reason to request wallet passwords or unrelated contacts.

Cookies

Cookies can remember a session, preserve a preference or help us understand a broken page. Your browser controls some cookie choices, while disabling necessary cookies may affect account access. The Privacy Policy explains the purpose of each cookie group in plain terms.

Account security

We use account checks before discussing private records or changing profile details. If access looks unusual, we may ask you to confirm an account step rather than disclose information immediately. Keep your login details private and contact support if a session does not look familiar.

Retention

We keep account, support and payment-reference records for the period needed to operate services, resolve disputes, protect accounts or meet a legal duty where local law permits. The period can differ by record type, so a deletion request may receive a specific explanation.

Your request

You can ask for access to your details, a correction, an explanation of processing or deletion where that option applies. Send the request through our support path with enough account context to locate it, and we may verify ownership before sharing or changing anything.

Answers About Your bimaspin Privacy Policy

These Privacy Policy answers address the questions you may have before opening an account or returning to the lobby from a phone. We keep the scope on personal data, cookies, wallet references, account security and requests for access or correction. If your situation is not covered, use the support path and describe the record or account step involved. Any access or eligibility decision depends on local law.

It covers account details, verification records, device and browser signals, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, virtual account or bank transfer activity. It also explains why we use those records, retention considerations and ways to request access or correction.

Phone verification helps connect an account request to the person seeking access and supports checks when profile details change. We use the result for account security, not as permission to request unrelated personal details. If a verification step fails, support can explain the next account path.

Yes. We may store a transaction reference, amount status or related support detail so we can match a DANA, OVO, GoPay, QRIS, virtual account or bank transfer enquiry. We do not need your wallet password to check a receipt, and the payment provider may apply its own privacy terms.

Cookies can keep a session active, remember a page preference or help diagnose access errors. Your browser provides controls for some cookie choices. Necessary cookies may still be required for account access, while optional records are handled according to the purposes described in our Privacy Policy.

You can contact support and name the detail that needs correction, such as a phone or contact record. Include a safe account identifier, not a wallet password. We may verify ownership before making the change, then explain whether the correction is completed or needs another account step.

Retention depends on the record and its purpose. Account, security, support and payment-reference data may remain while needed to provide access, resolve a dispute, protect the account or meet a legal duty where local law permits. We can explain the applicable reason when you submit a request.

Use our available support route and describe whether your question concerns account data, cookies, a device session or a wallet receipt. We may ask for the relevant account step before discussing private details. If your question concerns access or eligibility, the answer depends on local law.