Reference

Privacy Policy for Your toto30 Account

toto30 Privacy Policy explains what we collect when you open an account, sign in from a mobile device, or use DANA and QRIS for wallet activity.

Account dataWallet recordsCookie choicesDevice safety
toto30 Privacy Policy for Your toto30 Account
CONTACT PATHS

Ask About Your Privacy Policy Rights

A clear contact path helps you question a record, ask why a detail was requested, or request a correction.

Account support Use the support link after signing in and describe the Privacy Policy question in…
Wallet record check For a DANA, OVO, GoPay, QRIS, bank transfer, or virtual account query, share the…
Access request If you need a copy, correction, or deletion request considered, send it through the…
HANDLING DETAILS

What Happens To Your Data

We handle Privacy Policy requests around the same account flow you already use: phone verification, sign-in, wallet selection, and support contact.

Collection

When you open an account, we collect the details needed for access, such as your phone number and verification result.

Cookie choices

Cookies can remember a session, language choice, or page preference on the device you use.

Account security

We use phone verification and access checks to reduce mistaken or unauthorised account changes.

Payment references

Our records may contain a chosen rail such as QRIS or DANA, a reference number, amount status, and time.

Retention

We retain account and support records only while they serve the stated purpose, help resolve a dispute, protect access, or…

Your request

You can ask what account data we hold, request a correction, or ask us to consider deletion through support.

Privacy Policy Answers For toto30

These answers address the Privacy Policy searches we hear most often before account access. They cover phone verification, cookies, wallet references, device records, retention, and requests sent through support. If your situation is different, use the account support path and describe the exact record or access event you want us to check.

It covers data connected with your account, including phone verification, sign-in events, device signals, cookies, support messages, and payment references. It also explains how we use, retain, protect, and respond to requests about those records. Access depends on local law.

No. We may keep a selected payment rail, reference number, status, and time for a DANA or QRIS request, but we do not need your wallet password or PIN for that record. Do not include those secrets in a support message.

Phone verification helps connect an account request with the person who opened the account and helps reduce mistaken changes. We may use the result with sign-in and device records when checking access. Keep your verification code private and do not send it to support.

Use the support path inside your account and state whether you want a copy, correction, or deletion considered. Add your account phone number or reference, but leave out wallet PINs and passwords. We may verify your identity before releasing or changing a record.

Cookies may remember a session or page choice when you use a mobile browser, including a device opening the lobby after sign-in. Browser controls let you remove or restrict them. Turning cookies off can require another sign-in and may affect saved preferences.

We keep a record while it supports the stated purpose, account security, dispute handling, or a legal duty. The retention period can differ by record type. When the reason ends, we consider deletion or secure restriction under our handling process.

Yes. Send the transaction reference, selected rail, and date through account support, without sharing a wallet PIN or password. We can check whether the record relates to DANA, OVO, GoPay, QRIS, bank transfer, or a virtual account request.