Reference

Open sutra toto Privacy Policy

sutra toto Privacy Policy shows how we handle the details connected to your account, from phone verification to DANA and QRIS status.

Clear data purposesWallet record contextPhone access controlsPolicy request path
sutra toto Open sutra toto Privacy Policy
REQUEST HELP DIRECTLY

Switch to the right privacy contact

A clear contact route matters when a phone detail, wallet reference, or sign-in record needs attention.

Account-linked request Use the contact route connected to your sutra toto account when asking about a…
Wallet record check For a DANA, OVO, GoPay, QRIS, bank transfer, or virtual account question, share the…
Policy clarification Ask us to explain a Privacy Policy section in plain English, including why a…
DATA HANDLING BASICS

Explore the controls behind this policy

Privacy work is part of the account flow, not a separate promise hidden away from the cashier. We separate identity details, payment references, device signals, and support messages according to their operational…

Account details

When you open an account, we handle the details needed to create and maintain your profile. Phone verification can be required before account access, helping us avoid mixing one person’s records with another account.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer, or virtual account reference can appear in payment records. We use that reference to reconcile account activity and status without requesting your wallet password or unrelated wallet content.

Device signals

Your browser, device type, sign-in time, and related technical signals may be recorded for access checks. These details help us investigate an unusual login or a stalled account path without treating every device change as a problem.

Cookies

Cookies may keep a session active, remember a language or access preference, and help us understand whether a page loads correctly. The Privacy Policy describes their role so you can distinguish session support from account data handling.

Retention period

We retain records for the period needed for account administration, payment matching, support history, security checks, or a legal requirement that applies where local law permits. A deletion request can be assessed against those operational duties.

Changes and questions

You can ask us to correct an inaccurate phone detail, clarify a data purpose, or explain a retention reason. Send the request through the account-linked support path, and include only the details needed to locate your record.

Browse Privacy Policy answers before access

These Privacy Policy answers focus on the account questions you may have before opening access from Indonesia. We keep each response tied to a practical step, such as phone verification, a DANA reference, a device change, or a request to correct your record. If a question involves eligibility or access, the answer is read together with local law.

The Privacy Policy covers account details, phone verification, device signals, cookies, support messages, and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer, or virtual account activity. It also explains purposes, retention, correction requests, and the contact route for privacy questions.

Phone verification helps connect you to the correct account before access and reduces the chance of a mistaken account match. We may use the verified phone detail for account administration and support checks, subject to the Privacy Policy and where local law permits.

Yes. The Privacy Policy includes payment references associated with DANA, OVO, GoPay, QRIS, bank transfer, and virtual account activity. We use those references to match a deposit or withdrawal status to your account, not to request your wallet password or private wallet content.

You can request a correction when a phone detail, profile field, or other account record is inaccurate. Send the request through the account-linked support path and provide the smallest useful set of details. We may need to verify account ownership before changing the record.

Retention depends on why the record exists. Account administration, payment matching, security checks, support history, and legal duties may require different periods. Our Privacy Policy explains these purposes, and a deletion request is assessed against any duty that still applies where local law permits.

The policy can cover browser type, device type, sign-in time, session details, and related technical signals. We use them to support account access, identify unusual sign-ins, and investigate loading or login issues. They are handled for the stated operational purpose rather than collected without context.

Use the contact route linked to your account and state whether you need access, correction, deletion, retention clarification, or a policy explanation. For a wallet question, add the relevant payment reference only. Access and eligibility remain subject to local law and where local law permits.