Reference

xiu toto Privacy Policy For Your Account

xiu toto Privacy Policy explains what we collect when you open an account, use DANA or QRIS, and move between the lobby and your wallet.

Clear data purposesWallet record detailsPhone verification contextCookie choices
xiu toto xiu toto Privacy Policy For Your Account
CONTACT ROUTES

Privacy Help Beside Your Wallet

A clear contact path matters when you want to ask about the Privacy Policy rather than a game screen.

Account data request Ask us to explain the personal data connected with your xiu toto account.
Wallet record question For a DANA, OVO, GoPay or QRIS question, send the payment reference, date and…
Policy change request Use the support route beside the cashier path to request a correction, restriction or…
DATA HANDLING

Mobile Login And Data Controls

We handle policy matters around the real account steps you take, from mobile login through phone verification and payment status checks.

Account details

We may collect your phone number, login identifiers, verification result and account activity needed to provide access. These details help us connect a session with the correct account when you switch from a mobile browser to a desktop browser.

Payment records

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference can remain linked to your account history. We use the reference and status to reconcile a receipt, investigate a mismatch and answer a wallet-related request.

Cookies and devices

Cookies can remember a sign-in state, language choice and security event on the device you use. Your browser settings can remove or restrict cookies, although doing so may require another login or phone verification step.

Account security

We may record device signals, login time and failed access attempts to identify unusual account activity. Never send us a password, wallet PIN or one-time code; support can work from a verified phone number and transaction reference instead.

Retention timing

We retain records for as long as they support account operation, payment reconciliation, security checks or a legal requirement. When a record is no longer needed for those purposes, our handling follows the retention process applicable to the account and region.

Your requests

You can ask for access, correction, clarification or deletion of eligible personal data through the support route. We first confirm account ownership, then explain which records can be changed and which must remain for payment or legal reasons.

Privacy Policy Questions For Indonesia

These Privacy Policy answers cover the questions we expect before you open an account or connect an Indonesian wallet. If your situation involves a specific receipt, phone number or device, use the support path beside the account and include only the details needed to locate the record. Eligibility depends on local law.

It covers account details, phone verification, login events, device signals, cookies, payment references, support requests and records used for security or legal duties. It explains why we use each category and how you can ask about eligible data connected with your account.

We use your phone number to create and confirm account access, connect you with the correct wallet record and check ownership before a data request. Phone verification also helps us avoid sending account details to someone using an unverified device.

No. We may retain a DANA or QRIS transaction reference, amount status supplied by the payment route and timing needed for reconciliation, but your wallet password, PIN and one-time code should stay with you and must not be sent to support.

Use the support link beside the account or cashier path and identify the verified phone number on your account. We may ask an ownership question before responding, then explain which records can be provided and whether any legal retention rule applies.

You can request correction or deletion of eligible data through the stated support route. We confirm ownership first and explain the result. Payment references, security records or information required by law may need to remain for a defined purpose.

Cookies can support sign-in continuity, language settings and security checks on your browser. You can restrict them through browser controls, but that may clear your session or trigger phone verification again when you return to the account.

The policy is written for supported Indonesia access, including account activity from Surabaya and other cities, where local law permits. Availability and handling can depend on local law, so the account screen and current policy should be read together.