Reference

toto hk Privacy Policy Explained Clearly

toto hk Privacy Policy sets out what we collect when you open an account, sign in from a mobile browser, or use DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesAccess requests
toto hk toto hk Privacy Policy Explained Clearly
REQUEST HELP

Get Policy Help Beside Your Account

A clear contact route matters when a privacy request sits beside a login or wallet question. Use the support area linked with this policy and include your account contact, request type and relevant payment reference, without sending a password or full security code. We use the details you provide to locate the right record and reply with the next account step.

Team online

Privacy request path

Open the contact route shown with our Privacy Policy to ask for access, correction or deletion. Add your account contact and describe the request so we can locate the correct record.

Account access help

If a sign-in check stalls on your mobile browser, contact support through the account help path. We may ask for a verification detail, but never ask you to disclose your password.

Wallet record query

For a DANA, OVO, GoPay or QRIS record question, include the payment reference and date. That lets us separate a wallet status query from a request about stored personal data.

DATA HANDLING

See How Your Records Are Managed

We keep this policy practical by tying each data use to an account action you can recognise.

Account opening

When you create an account, we use the submitted contact details to establish your account record and send access-related messages. We do not need your password in a privacy request.

Phone verification

A phone verification step helps connect the person requesting account access with the relevant record. We retain the verification result for account security and handle correction requests through support.

Device signals

Our systems may receive browser, device and sign-in signals when you move from mobile login to the lobby. These signals help identify unusual access without reading private content on your device.

Cookies and storage

Cookies can keep your session active and preserve selected settings. You can manage browser cookie controls, although changing them may affect sign-in continuity and the way privacy choices are remembered.

Retention steps

We retain records only for the account, security, dispute or legal purpose that requires them. When that purpose ends, deletion or anonymisation follows our internal retention process where local law permits.

Policy changes

If this Privacy Policy changes, we place the revised wording on this page and show the effective date. Check it before opening an account or changing wallet details, especially after a policy update.

Privacy Policy Answers For Your Account

These Privacy Policy answers focus on the searches we hear before account opening: what data is collected, how wallet references are used, whether mobile access changes the record, and how to request a change. If your question is specific to your account, use the policy contact path with the smallest useful set of details.

It covers account details, phone verification, device and browser signals, cookies, sign-in events, wallet references and requests to access or correct records. It also explains retention and policy changes.

Those wallet rails can appear in account records when you select or reference them. We use the related status or payment reference to connect an account action, not to request your wallet password.

We may receive browser, device and sign-in signals when you use the mobile path. These signals support session security and unusual-access checks; they do not give us access to private files on your device.

Use the contact route shown beside this policy and state that you want an access request. Include your account contact and enough detail to identify the record, while leaving out passwords and full security codes.

Yes, send a correction request through the policy support path. Tell us which account detail is wrong and what should replace it; we may complete an account check before changing the record.

Retention depends on why the record exists, such as account access, security, a payment dispute or a legal requirement. When the purpose ends, deletion or anonymisation follows where local law permits.

Your browser can restrict cookies through its own controls. Some session features may then work differently, so sign-in continuity or saved privacy choices may not remain available on your next visit.