Reference

ten40aw toto Privacy Policy For Your Account

DANA, OVO, GoPay and QRIS records are handled alongside your login details under the ten40aw toto Privacy Policy, so you can see what we collect before opening an…

Clear data choicesWallet activity contextMobile accessPolicy contact path
ten40aw toto ten40aw toto Privacy Policy For Your Account
POLICY HELP ROUTES

Ask About Privacy Policy And Account Data

A direct support route helps when you want to understand a Privacy Policy clause, correct an account detail or ask how a wallet record is used.

Account help Use the account help path beside the cashier section for a Privacy Policy question.
Payment records If a DANA, OVO, GoPay, bank transfer or virtual account entry looks unfamiliar, share…
Access questions When a policy page or account request does not load on your phone, tell…
DATA HANDLING PRACTICE

What We Do With Your Personal Details

We keep the Privacy Policy practical by linking each data use to an account action you can recognise.

Account information

We may hold the name, phone number and verification information you provide when creating or accessing an account.

Cookies and devices

Cookies and device signals can remember a session, preserve the account path on mobile and help identify repeated access attempts.

Wallet references

For DANA, OVO, GoPay and QRIS activity, we use transaction references and status information rather than your wallet PIN.

Account protection

Phone verification and login checks help protect the account from access that does not match your usual activity.

Retention period

We retain account, support and transaction records only for as long as needed for the stated account, safety, dispute and…

Changes and requests

You can ask about access, correction, deletion or a restriction concerning your personal details where local law permits.

Privacy Policy Answers For Indonesian Accounts

These Privacy Policy answers cover the questions we expect you to ask before opening an account or sending a data request. They explain the practical link between account access, mobile use, payment references and support. If your situation is not listed, use the account help route and describe the exact record or policy point you want us to address.

It covers personal details, phone verification, login and device activity, support messages, cookies and payment references connected with your account. It also explains how we use, protect, retain and respond to requests about those records when you access the site from Indonesia.

Your phone number supports the account access step and helps us complete phone verification. It can also help us identify your account when you ask about a DANA, OVO, GoPay, QRIS or login record, but you should never send your verification code to support.

No. Our handling of DANA, OVO, GoPay and QRIS activity uses payment references and status details needed for account reconciliation. We do not need your wallet PIN for a policy request, and you should not place it in chat, email or any support form.

Use the account help path near the cashier area and state whether you want access to, or correction of, a particular record. Include your linked phone number for account matching, then complete any ownership check we request. The available action depends on local law.

Cookies can keep your session and account path working when you move from login to the mobile lobby. Browser settings let you remove or block them, but necessary cookies may be required to authenticate again. Device signals may also help us spot unusual access.

Retention depends on the record and the purpose for keeping it, such as account access, payment reconciliation, support history, safety checks or legal duties. If you ask about deletion, we will identify the relevant record and explain where limited retention still applies.

Yes. Start with account support and describe the policy concern without including a password, one-time code or wallet PIN. For a payment question, add the transaction reference and approximate time. We will explain the applicable request path, with access depending on local law.