Reference

botatoto Privacy Policy For Your Account

Our Privacy Policy explains what botatoto collects when you open an account, sign in from your phone, browse Live Roulette or check wallet status through DANA, OVO, GoPay…

Clear data purposesWallet record detailsCookie choicesAccount request path
botatoto botatoto Privacy Policy For Your Account
HELP WITH PRIVACY

Get A Clear Privacy Contact Path

A direct support path matters when your Privacy Policy question concerns a phone number, wallet receipt or sign-in record. Start from your account support route and tell us whether the request concerns DANA, QRIS, bank transfer, a device change or a data correction. We use the details you provide to locate the right record without asking you to repeat unrelated account history. If you are in Jakarta or elsewhere in Indonesia, the same request path applies, subject to local law.

Team online

Account request

Use our account support path to ask about personal data held for your botatoto profile. Include your registered phone number and the requested action, such as correcting a name, checking a phone verification record or asking which account detail is linked to your access.

Wallet record

For a Privacy Policy question about DANA, OVO, GoPay, QRIS or a bank transfer reference, share the receipt time and visible reference only. We can then check the payment record connected to your account without requesting your wallet password or private security code.

Access concern

If a sign-in device or phone verification result looks unfamiliar, use the account help route and describe when you noticed it. We may ask for account confirmation before discussing records, helping us keep personal data away from an unverified request.

DATA CONTROL

Keep Your botatoto Records Under Control

Privacy is handled through practical account controls rather than broad promises. We separate login activity, wallet references and support correspondence so each request can be checked against the relevant record.

Account data

We use the details needed to create and maintain your account, including contact information and phone verification status. When you ask for a copy or correction under the Privacy Policy, we first confirm that the request comes from the account holder before discussing personal records.

Cookies

Cookies can remember a session on your mobile browser and help us understand whether a sign-in request matches the device pattern already connected to your account. You can review browser cookie controls, although changing them may require another sign-in or affect session continuity.

Security checks

Phone verification and device signals help us identify unusual account access before a request reaches wallet records. We may ask you to confirm account details when you contact us about DANA, QRIS, bank transfer or a sign-in event.

Retention

We keep account, payment and support records for the period needed to operate the service, resolve disputes, protect access and meet legal duties. The retention period can differ by record type, so your request should name the specific data you want us to assess.

Correction request

If your phone number, contact detail or account name is wrong, send a correction request through account support. Tell us the current value and the replacement value; we may request confirmation before changing a detail that controls account access.

Policy contact

Questions about this Privacy Policy can be sent through the same support path used for account help. State that your request concerns privacy, identify the record or purpose involved and include no wallet password, one-time code or full payment credential.

Privacy Policy Answers For Indonesia

These Privacy Policy answers focus on the account questions you are most likely to ask before opening or using botatoto. We explain the records connected with phone verification, mobile sessions, wallet activity and support requests in plain terms. If your situation concerns eligibility or access in Indonesia, it depends on local law. For a personal case, use the account support path and identify the exact record you want us to check.

It covers personal data connected with your account, including contact details, phone verification, sign-in device signals, wallet references, cookies and support messages. It also explains why we use those records, how retention is considered and how you can ask for access or correction.

Phone verification helps connect an account request to the person seeking access and helps us investigate unusual sign-in activity. It can also support a correction or privacy request. We use the verification result for account and security purposes, not as a reason to collect unrelated details.

Yes. The policy covers payment references and status details connected with DANA, QRIS, OVO, GoPay, bank transfer and virtual account routes. A receipt or reference can help us match a wallet event to your account, while private wallet passwords and one-time codes should not be sent.

Use the account support path and state that the request concerns the Privacy Policy. Include your registered phone number, the incorrect detail and the replacement value. We may confirm account ownership before changing information that affects sign-in, phone verification or wallet record matching.

Retention depends on the record and the reason it was created. Account, payment and support records may be kept while needed for access, security, dispute handling or legal duties. Ask us about a named record rather than a general deletion request so we can assess it accurately.

Yes. Ask through account support which cookie or session concern you want checked. Browser settings can remove or restrict cookies, but that may end a saved session and require phone verification again. We can explain the account effect without asking for your device password.

Yes. Account eligibility and access depend on local law, and our Privacy Policy applies where local law permits. If you are in Indonesia and need a specific rights answer, contact support with your account phone number and the data purpose or record involved.