Reference

sakau toto Privacy Policy, Clearly Explained

sakau toto Privacy Policy shows what we collect when you open an account, sign in from a mobile device, or use DANA and QRIS at the cashier.

Account clarityWallet contextCookie choicesContact route
sakau toto sakau toto Privacy Policy, Clearly Explained
CONTACT WHEN NEEDED

Get Policy Help Beside Account Support

A clear contact route matters when your account data or wallet status needs attention. We keep privacy questions close to the same account-help path used for login checks, payment receipts and status…

Account access If you cannot sign in or need to confirm which phone number is attached to your account, use the account-help route beside the login path. We may ask for an account detail to confirm that the privacy request comes from you.
Wallet records For a DANA, OVO, GoPay or QRIS receipt question, include the transaction reference and date, not your wallet password or security code. We can then connect the payment status with the relevant account record without requesting unrelated wallet content.
Privacy requests Ask us to access, correct or remove eligible personal data through the account support path. State the request plainly and use your registered contact detail, because we check account ownership before discussing stored records or applying a change.
CONTROL YOUR RECORDS

What We Do With Your Personal Data

We separate account operation from the content of your personal wallet. Sign-in, phone verification and cashier checks create records needed to connect your request to the right account, while device and browser…

Data collection

We collect details you provide during account creation and phone verification, along with sign-in time, browser type and device signals needed for account security. We do not need your DANA, OVO or GoPay wallet PIN to connect a payment reference with your account.

Cookie controls

Cookies can keep a signed-in session working and help us understand whether a page loads correctly on mobile or desktop. You can adjust cookie permissions in your browser, although blocking some cookies may affect account access or require you to sign in again.

Account security

Before we discuss personal records or change registered details, we use account and phone checks to confirm ownership. Never send a password, wallet PIN or one-time code in a support message; those credentials remain yours and are not required for a privacy request.

Record retention

We keep account, support and payment-reference records only as long as needed for the stated service, security checks, dispute handling or legal duties. A deletion request does not automatically remove records that must remain to reconcile a QRIS, bank transfer or virtual account event.

Device access

Your mobile browser can reach the account path without a separate app, and the same account records may be used when you return on desktop. If a new device triggers a security check, completing phone verification helps us protect the account before showing stored details.

Change requests

To correct a phone number, ask for a copy of stored data or request removal of eligible records, contact us through account support with your registered detail. We assess the request under applicable law, explain any restriction, and confirm the action through the account contact path.

Answers About Privacy Policy Access

These Privacy Policy answers cover the questions you may have before opening an account or returning to the lobby from Indonesia. We focus on the records connected to sign-in, phone verification, cookies, payment references and support requests, so you know what to send and what to expect. If your situation is not covered, use the account support path and mention the specific record or request you want us to check.

The sakau toto Privacy Policy covers account details, phone verification, sign-in and device data, cookies, support messages and payment references. It explains why we use those records for access, security, status checks and legal duties, and how you can request access, correction or removal where local law permits.

We may store a reference showing that you used DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, together with status and timing needed for reconciliation. We do not need your wallet PIN or one-time code to check whether a cashier request matches your account.

Send an access request through the account support path using your registered contact detail. Tell us whether you want account, device, cookie, support or payment-reference records. We verify account ownership before sharing data, and we explain any lawful limit on what can be provided.

Yes, you can ask us to correct eligible details such as a phone number or other account data through account support. Include the current record and the requested correction, but do not send a password or wallet security code. We confirm ownership before applying the change.

Our Privacy Policy covers cookies used to maintain a session and check page behaviour on mobile or desktop. You can manage permissions in your browser settings where available. If you block required cookies, you may need to sign in again or some account steps may not work.

Retention depends on the purpose of each record. We keep data for account operation, security, support, dispute handling or legal duties only as long as needed for that purpose. Some payment references may remain after closure when they are required to reconcile DANA, QRIS or bank activity.

Yes. Requests and account eligibility are handled according to applicable requirements and depend on local law. Where local law permits, you can ask for access, correction or deletion of eligible data. Contact account support if you need us to explain a restriction affecting your request.