Reference

capsatoto2 Privacy Policy Explained Clearly

Our Privacy Policy explains what account, device, cookie and payment details we handle when you use capsatoto2, from phone verification before account access to a mobile browser opening…

Account dataCookie choicesWallet detailsYour privacy requests
capsatoto2 capsatoto2 Privacy Policy Explained Clearly
CONTACT ROUTES

Privacy Help Beside Your Account

A clear contact path matters when a record looks unfamiliar or a privacy request needs checking. We keep policy help close to the account and cashier paths, so you can describe the issue without sending sensitive wallet credentials. Your request can concern phone verification, a cookie setting, a DANA reference, or activity linked to a mobile browser. We use the details you provide to locate the relevant record, confirm account ownership and respond through the available support route.

Team online

Account request

Use the support route connected to your account when you want a copy, correction or explanation of personal details. We may ask for the phone number linked to your account so we can confirm ownership before discussing records.

Wallet query

If a DANA, OVO, GoPay or QRIS reference appears in a privacy question, include the date and reference shown in your account. We use that limited payment detail to locate the record without asking for your wallet PIN.

Device concern

Tell us if a mobile browser, shared handset or unfamiliar login appears in your account history. We can review the related security record, explain the data purpose and guide you through the account step needed to protect access.

CONTROL CENTRE

How We Handle Your Privacy Choices

We treat privacy requests as account actions that require careful identity checks, not as a general message about the lobby.

Account security

Phone verification comes before account access, helping us distinguish your request from an attempt made on another device.

Cookies on mobile

Cookies can keep a session active and remember selected settings when you move from login to the lobby on a…

Payment references

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we handle the reference, status and amount needed to…

Game activity records

Our records may connect account activity with areas such as Live Casino, jamuslott, bolajasa, Aviator, Bingo or Fish Hunter.

Retention periods

We retain records only for the period needed for account operation, security checks, payment matching, dispute handling or a legal…

Changes and requests

You can ask us to correct inaccurate details, explain a data purpose, request a copy or ask about removal through…

Privacy Policy Questions Answered

These Privacy Policy answers focus on the account steps Indonesian customers ask about most often. They cover phone verification, cookies, wallet references, device records, retention and requests for access or correction. If your question concerns a detail not listed here, use the support route beside your account and describe the specific record you want us to check.

The capsatoto2 Privacy Policy covers details such as your phone number, verification status, login events, device signals, support messages and account activity. We use them for account operation, security, payment matching and a stated legal need where local law permits.

Phone verification helps us confirm that the person requesting account access or a privacy change controls the linked account. It also helps us investigate an unfamiliar login. We do not use verification as a reason to request your DANA, OVO or GoPay PIN.

Yes. The Privacy Policy covers payment references, status and matching details connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We use those details to identify an account transaction, while wallet passwords and PINs remain with the payment provider.

Open the support route linked to your account and state whether you want a copy, correction or explanation. Include the relevant account detail, such as your phone number or a payment reference, but do not send a wallet password. We confirm ownership before responding.

Cookies can preserve a login session and remember settings when you use a mobile browser from account access to the lobby. Your browser controls can limit them. If cookies are disabled, some account and privacy request steps may not work as intended.

We keep each record for the period needed for its purpose, such as account security, payment matching, dispute handling or a legal requirement. After that period, we remove, aggregate or restrict it. A support request can ask why a particular record remains.

You can submit a removal request through the account support route. We verify the request and explain which records can be removed, restricted or changed. Some details may need to remain for security, payment matching or a legal requirement where local law permits.