Reference

densus toto Privacy Policy For Your Account

Our Privacy Policy explains what account details we collect, why we use them and how you can ask us to change or remove eligible records.

Account dataWallet recordsDevice accessPolicy requests
densus toto densus toto Privacy Policy For Your Account
CONTACT PATHS

Privacy Help Beside Your Account

A clear contact route matters when you want to ask about your Privacy Policy rights or an account record.

Policy questions Ask through support chat when you need to understand a Privacy Policy section, the purpose of a phone check or the reason a particular account record is retained. We will explain the relevant step in plain English and may ask you to confirm the account phone number.
Access requests For a copy, correction or eligible removal request, contact our support email route with your account phone number and the record you are asking about. We check account ownership before responding, so your request does not expose DANA, OVO, GoPay or QRIS details to another person.
Wallet record checks If a payment receipt or wallet status is part of your question, attach only the reference details needed to locate it and hide unrelated balances. Our support path can compare the account record with the selected DANA, QRIS, bank transfer or virtual account route.
DATA PRACTICES

What We Do With Your Privacy

We keep this policy practical by linking each data use to an account action you can recognise. Phone verification supports account access, device records help us investigate sign-in issues, and payment references…

Account details

We use the phone number and contact details you provide to create your account, confirm that you are requesting access and respond to account questions. Please keep those details current; an outdated number can make an ownership check slower when you request a Privacy Policy change.

Cookies and sessions

Cookies and similar session records help keep your signed-in path working as you move from the account page to the lobby on mobile or desktop. You can manage browser cookie settings, but limiting them may require you to sign in again or repeat an account step.

Device signals

When you access the account from a phone, tablet or desktop browser, we may record basic device and session signals for sign-in checks and support diagnosis. We do not need your wallet password to review why a login or account page behaved differently on one device.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference can be retained to match a payment status with your account. We use the reference for reconciliation and support checks, rather than asking you to share a wallet PIN or one-time code.

Security controls

Phone verification before account access is one of our account-security checks. We also ask you to keep sign-in details private and to contact support if a device you no longer control appears in your session history. These steps reduce mistaken access during a policy request.

Retention and changes

We retain records only while they support account access, payment reconciliation, security checks or a required operational purpose. To request a copy, correction or eligible deletion, send support your account phone number and a precise description; we confirm ownership before making a change.

Privacy Policy Answers For Indonesia

These Privacy Policy answers cover the searches we hear most often before account opening. They explain the records connected to your account, how device and payment references are used, and the practical route for requesting access or correction. If your situation is not listed, our support chat can point you to the relevant policy wording.

The densus toto Privacy Policy covers account details, phone verification, sign-in and device records, cookies, support messages and payment references. It explains why we use each category, how we protect account access and how you can contact us about a copy, correction or eligible removal.

Phone verification helps us confirm that the person requesting account access or a data change controls the linked account. We may ask you to repeat this check before discussing records. Never send your password, wallet PIN or one-time code through support chat or email.

We may retain payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity so we can match a receipt with the correct account. These references support status checks; they do not require us to request your wallet password or PIN.

Contact our support chat or email route and state that you want a Privacy Policy data copy. Include the phone number linked to your account and describe the records you need. We first confirm account ownership, then explain what can be provided and the next step.

Yes, you can ask us to correct eligible account details by contacting support with your linked phone number and the exact field that needs changing. We verify ownership before editing the record. If a record cannot be changed, we explain the operational reason in our response.

Our Privacy Policy allows retention while a record supports account access, payment reconciliation, security checks, support handling or another required operational purpose. When you ask about deletion, we assess the specific record and explain whether it can be removed or must remain for that purpose.

Access or eligibility depends on local law. The Privacy Policy applies to the account and records created through supported access, but it does not replace local requirements. If your location or account status creates a restriction, contact support for the applicable wording before requesting a policy change.