Reference

botoltoto Privacy Policy for Your Account

botoltoto Privacy Policy explains how we collect, use and protect the details connected with your account, including phone verification and wallet status.

Phone verificationCookie choicesWallet data contextAccount access
botoltoto botoltoto Privacy Policy for Your Account
CONTACT ROUTES

Privacy Questions Near Your Wallet Path

A clear contact route matters when a privacy question appears beside a wallet status or login step. We direct you to the support path shown in your account area, where you can identify the account, describe the request, and attach a payment receipt when it helps us locate the correct record. Please avoid sending passwords or full wallet credentials in any privacy message.

Team online

Account request

Use the support path connected to your account when asking for a copy, correction, or explanation of personal data. Include your registered phone number so we can locate the right record.

Wallet reference

For DANA, OVO, GoPay, QRIS, bank transfer, or virtual account questions, share the transaction reference and date only. We use those details to check records without requesting your wallet password.

Access concern

If phone verification or account access exposes a privacy concern, tell us which step appeared on your mobile browser. We can review the event and explain what data that step required.

DATA PRACTICES

Privacy Controls Across Mobile and Account

We handle policy requests through the same account path used for phone verification, because confirming the requester helps prevent another person from changing your record.

Collected details

We may collect your phone number, account identifiers, login events, device signals, payment references, and messages sent to support. We collect these details when you take a stated account or wallet action.

Use of data

Account and transaction records help us complete phone checks, match wallet activity, detect unusual access, answer privacy requests, and meet applicable legal duties. We do not use a privacy request as a reason to ask for unrelated credentials.

Cookies

Cookies and similar browser storage can keep a session connected, remember selected settings, and help us detect repeated sign-in problems. You can manage browser storage through your mobile browser settings, though some account steps may then need repeating.

Account security

Phone verification is used before account access, while login events and device signals can help us identify unusual activity. Keep your verification codes private and contact support if a sign-in event does not match your action.

Retention period

We keep records only for as long as needed for the stated purpose, account reconciliation, dispute handling, security checks, or legal duties. Retention can differ between a phone event, a payment reference, and a support message.

Changes and contact

You can ask us to correct inaccurate details, explain a data use, or clarify a retention decision through the account support path. We may request phone verification before discussing or changing information linked to your account.

Privacy Policy Answers for Indonesia

These Privacy Policy answers address the searches we expect before you open an account from Indonesia. They explain what we collect, how wallet references are handled, what cookies do, and how to ask for a change. If your situation depends on a local requirement, we will assess the request under the law that applies to your access.

It covers account details, phone verification, login and device events, payment references, cookies, support messages, retention, and requests to correct or explain personal data connected with your account.

Phone verification helps connect account access with the correct person and reduces mistaken or unauthorised changes. We may use the verification event as part of an access or privacy request check.

Yes. The policy explains how we handle DANA, QRIS, OVO, GoPay, bank transfer, and virtual account references used to match an account action. We do not request your wallet password.

You can request a correction through the account support path. Tell us which detail is inaccurate, identify the account with your registered phone number, and complete any verification we reasonably require.

Cookies can maintain your session, remember selected settings, and help identify repeated login issues. Clearing browser storage may remove those settings and require you to repeat phone verification or another account step.

Retention depends on the record and its purpose. We may keep payment references for reconciliation, security checks, disputes, or legal duties, then remove or restrict them when they are no longer needed.

Use the support route shown in your account area and describe the request clearly. For a wallet matter, include the reference and date, but never send a password, verification code, or full wallet credentials.