Reference

dana100vip Privacy Policy for Your Account

The dana100vip Privacy Policy explains what we collect when you open an account, use a mobile device, or connect DANA, OVO, GoPay and QRIS.

Account dataWallet recordsDevice detailsCookie choices
dana100vip dana100vip Privacy Policy for Your Account
CONTACT DATA HELP

Where to Ask About Privacy Policy

A clear support path helps you ask about the Privacy Policy without explaining your concern repeatedly. Start from the account help route shown beside the cashier area and include your account phone number, the affected wallet rail and the payment reference if your request concerns DANA, OVO, GoPay or QRIS. We use those details to locate the relevant record, while you should avoid sending a wallet PIN or full password. If you cannot sign in, state that first so we can use the account-access path available to you.

Team online

Account data request

Use the account help path to ask what personal details are connected to your dana100vip account. Include the phone number used during verification so we can distinguish your request from another account and ask for an identity check before releasing account-linked data.

Wallet record check

For a privacy question about DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity, provide the transaction reference and date. We can then check the payment-status record without asking you to disclose a wallet password or private wallet security code.

Access problem

If login stalls before you can reach the account help route, describe the device path you used, such as mobile browser or desktop browser. We use that context to handle an access request while keeping the privacy conversation tied to your verified account.

HANDLING YOUR RECORDS

What We Do With Account And Device Data

The Privacy Policy is practical: it connects each data category with a reason for using it. Account details support phone verification and sign-in; device and browser signals help us recognise unusual access…

Account security

We use your verified phone number and sign-in events to protect account access. A new device or unusual login may require an additional check. This lets us discuss a data request with the account holder rather than disclose personal details to an unknown contact.

Device behaviour

When you move between a mobile browser and desktop browser, we may record device type, browser signals and access time. These details help diagnose a stuck login or repeated verification prompt; they are handled as account security data, not as a request for your device contents.

Cookies

Cookies can keep a session setting or help us understand whether a page loads correctly. You can manage cookies through your browser controls, although removing them may require you to repeat the phone-verification or sign-in step.

Payment matching

For DANA, OVO, GoPay and QRIS, we keep the reference and status needed to match a cashier action to your account. Bank transfer and virtual account checks may also show BCA, BRI, Mandiri or BNI context without storing your bank password.

Retention periods

We keep account, access and payment records for as long as needed for the purpose described in this Privacy Policy, including dispute handling and legal duties. When a record is no longer needed, our process is to delete it or remove its direct account link.

Changes and requests

You can ask for access, correction or deletion through the account help route. Tell us which record concerns you, such as a phone number, cookie choice or QRIS receipt. Where local law permits, we may request identity confirmation before changing or sharing the data.

Privacy Policy Answers For Indonesia Accounts

These Privacy Policy answers cover the questions we expect you to ask before opening an account or checking a wallet record. They explain the practical route for data access, corrections, cookies, device details and account deletion. If your situation is specific, use the support path linked to your account and include only the details needed to locate the request.

The dana100vip Privacy Policy covers account and phone-verification data, login and device signals, cookie settings, support messages, and payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains retention, account requests and the limits created by local law.

No. Our Privacy Policy describes recording the payment reference and status needed to match an account transaction. We do not ask for your DANA or OVO wallet password. If support needs a receipt check, send the reference and date through the account help route instead.

Where local law permits, you can request access to personal data connected with your account. Use the account help path and identify the phone number used for verification. We may ask for an identity check before responding, so account details are not disclosed to an unauthorised contact.

Send a correction request through account help and name the field that needs changing, such as a phone number or contact detail. We may confirm your identity and ask for supporting context. Payment references cannot be altered simply to change a transaction history or dispute record.

Device type, browser signals and access time help us recognise unusual sign-ins and investigate a repeated verification prompt. The Privacy Policy does not mean we inspect your device contents. If a mobile browser behaves differently from desktop access, mention that path in your support request.

You can manage or remove cookies through your browser settings. Some session preferences may then disappear, and you may need to repeat sign-in or phone verification. The Privacy Policy explains that cookies support page operation and diagnostic checks rather than giving us access to wallet passwords.

Where local law permits, you can request deletion through the account help route. We assess which records can be removed and which must remain for payment reconciliation, fraud checks, disputes or legal duties. Include the account phone number and the specific data category you want us to assess.