Reference

bimabet Privacy Policy for Your Account

Our Privacy Policy explains how bimabet handles the details you provide when opening an account, signing in from a mobile browser, and checking wallet records for DANA, OVO…

Account clarityWallet recordsCookie choicesRequest access
bimabet bimabet Privacy Policy for Your Account
HELP WITH REQUESTS

Get Privacy Help Near Your Account

A clear support path helps when you want to ask what we hold, correct an account detail or question a wallet record. Start from the support link shown after sign-in and include the email or phone detail attached to your account, without sending a password or wallet PIN. We use the same route for requests from mobile and desktop browsers.

Team online

Access request

Ask us which account details, device events or support messages are linked to your profile. We may ask for an account step that confirms the request comes from you before sending a response.

Correction request

If your contact detail or account record is inaccurate, describe the specific field through the account support route. We check the request against your sign-in details before making a change.

Wallet question

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account references, attach the transaction date and status shown in your account. Never include a wallet PIN or full password.

CONTROL YOUR DETAILS

How We Handle Account Privacy

We keep this policy practical: you should know why a detail is collected, how it supports an account action and what route to use when something needs changing.

Account data

We may hold the contact details you submit during account opening, along with sign-in events needed to connect your access…

Device signals

A mobile browser or desktop browser can send device and connection signals during sign-in.

Cookie choices

Cookies can remember session status and your policy choices between pages.

Payment references

For DANA, OVO, GoPay, QRIS and bank rails, we retain references such as amount status, channel and time when needed…

Retention checks

We keep records only for the period needed for the stated account, security, support or legal purpose.

Change requests

Send a request through the signed-in support route and name the exact detail you want to access, correct or remove.

Privacy Policy Answers for Indonesia

These answers address the questions we expect you to ask before creating an account: what we collect, why wallet references appear, how cookies work and how to request a change. If your situation is different, use the signed-in support path and quote the relevant account detail.

It explains how we handle account details, sign-in and device records, cookies, support messages, payment references and requests to access or correct your data. It also explains local-law limits on available access.

When you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, we may retain a reference showing the channel and status. This helps us match an account action without requesting your wallet PIN.

We may collect the contact details you submit, account sign-in events, device and connection signals, support correspondence and transaction references. We use each category for the account, security or support purpose described here.

Yes, send an access request through the support link visible after sign-in. State the account detail or record you want us to locate, and we may verify your identity before responding.

Use the signed-in support route, identify the field that is wrong and provide the corrected value. We compare the request with your account details before confirming whether the change can be made.

Session cookies can keep your sign-in active while you move between pages on a mobile browser. If you remove them, you may need to sign in again before opening account or support areas.

We retain payment references for the period needed for account matching, security, support or applicable legal requirements. The exact period can depend on the record type and local law.