Reference

bobatoto Privacy Policy for Account and Wallet Data

Our bobatoto Privacy Policy explains what we collect when you open an account, sign in from a mobile browser, browse the Live Dealer Lobby or use DANA, OVO…

Account collectionWallet recordsCookie choicesAccess requests

Explore Our Lobby Read FAQ

How Privacy Policy Applies in Indonesia

bobatoto Service availability depends on jurisdiction. Users are responsible for checking local law before access.

This Privacy Policy covers the details you provide during account creation, including contact data used for phone verification before account access. It also covers sign-in records, device and browser signals, lobby activity, support messages, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or

1
a virtual account. We use this material to process account requests, match a receipt to the correct wallet status, protect the account from unusual access and answer a privacy request. We do not ask you to send a wallet password through support. If you use a
2
shared device, sign out and clear saved browser data after visiting the account area. Our services and any eligibility decision are available where local law permits; this wording does not change rights or duties that apply to you in Indonesia.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

PRIVACY HELP ROUTE

Where to Ask About Your Privacy Policy

A clear contact route matters when you want to understand a record or change an account detail.

Account request Use the signed-in account support path to ask what personal details are linked to your profile or to request a correction. We may ask for an account step before discussing protected records.

Wallet record For DANA, OVO, GoPay or QRIS records, share the transaction reference and date shown on your receipt. Do not send a wallet PIN; the reference lets us check the account-side status.

Access question If a mobile browser shows a different privacy choice from desktop, tell us the device path and browser state. We can explain cookie controls and account access where local law permits.

DATA HANDLING

What We Do With Your Account Details

We keep this Privacy Policy practical: each data use connects to account access, payment checking, security or a request from you.

Account details

We collect the contact and verification details needed to create and maintain your account. These details help us distinguish your sign-in from another session and route an account request to the correct record.

Payment references

A DANA, OVO, GoPay or QRIS reference can be used to match a cashier event with your account. Bank transfer and virtual account references serve the same checking purpose without requiring a wallet password.

Cookies

Cookies and similar browser storage can remember a session choice or help us understand whether a page loads correctly. You can manage browser permissions, though removing them may require another sign-in.

Device security

We use sign-in, phone verification and device signals to identify unusual account access. If your phone is shared or lost, sign out on the device and contact support through the account path.

Retention

We retain account, security and payment references only for the period needed for the stated service, dispute handling and applicable legal duties. When a record is no longer needed, our process removes or anonymises it.

Change requests

You can ask us to correct account data, explain its use or address a privacy concern. Send the request through signed-in support with enough detail to identify you, while withholding wallet credentials.

Privacy Policy Answers for bobatoto

These Privacy Policy answers focus on the account actions you are most likely to take in Indonesia: opening access, checking a wallet reference, using a mobile device and asking for a data change. If your question is not listed, use the signed-in support route and describe the record without sending secret credentials.

It covers account and phone-verification details, sign-in and device records, cookies, support messages, lobby activity and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or a virtual account.

Phone verification helps connect the sign-in to the correct account and helps us investigate unusual access. We use the verification detail for account security and related support, where local law permits.

Yes. A DANA or QRIS receipt reference can be handled as an account-linked payment record so we can check status. Send the reference and date, never a wallet PIN or password.

Cookies may keep a session choice or help a mobile browser load the account path correctly. Clearing them can remove saved preferences and may require you to sign in again on that device.

You can ask for access, clarification or correction through signed-in support. Include the account identifier and the specific record, such as a phone detail or wallet reference, without attaching unnecessary private data.

We keep records for the period needed to operate account access, address disputes, protect security and meet applicable legal duties. Records no longer needed are removed or anonymised through our retention process.

Use the support path inside your signed-in account and label the request as a Privacy Policy question. For payment records, add the DANA, OVO, GoPay or QRIS reference, but do not send credentials.

bobatoto Privacy Policy for Account and Wallet Data

Where to Ask About Your Privacy Policy

What We Do With Your Account Details

Account details

Payment references

Cookies

Device security

Retention

Change requests

Privacy Policy Answers for bobatoto

01 What does the bobatoto Privacy Policy cover?

02 Why does bobatoto need phone verification before account access?

03 Does the Privacy Policy include my DANA or QRIS receipt?

04 How do cookies affect my bobatoto account on mobile?

05 Can I request a copy or correction of my personal data?

06 How long does bobatoto keep account and payment records?

07 Who can I contact about a Privacy Policy concern?

Related Pages