Reference

Privacy Policy for Your dana123 Account

Our Privacy Policy explains what account, device, cookie and payment details we handle when you open or use dana123.

Account dataDevice signalsWallet recordsPolicy requests
dana123 Privacy Policy for Your dana123 Account
REQUEST A RESPONSE

Privacy Help Beside Your Account Path

A clear contact route helps you ask about the Privacy Policy without explaining your whole account history. Send a policy question through the support route shown inside your account, and include the phone number linked to your profile plus the subject of your request. We may ask for a matching account step before discussing personal data. If a DANA or QRIS receipt is attached, remove unrelated wallet details before sending it.

Team online

Policy questions

Use the account support route for questions about the Privacy Policy, stored details or a request to change personal data. We will use your account phone number to locate the right record before replying.

Wallet references

When your question concerns DANA, OVO, GoPay or QRIS, share only the transaction reference and status needed for the check. Do not send a wallet PIN, password or full authentication code.

Account access

If sign-in stalls during a privacy request, tell us the device path you used, such as mobile browser or desktop browser. This helps us separate an access issue from a request about stored data.

HOW WE HANDLE DATA

Account, Cookie and Device Safeguards

We keep this Privacy Policy practical by linking each data use to an account, security or support task.

Phone verification

Before account access or a detailed data response, we may check the phone number attached to your profile. This step reduces the chance that another person receives account details through a support request.

Login records

We record sign-in events and related device signals to protect account access. A mobile browser and a desktop browser may create different session records, which can help us investigate an unexpected login.

Cookies

Cookies or browser storage can remember a session path and support page functions. You can manage browser storage through your device settings, although removing it may require you to verify your account again.

Payment data

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we use transaction references and status details to match account records. We do not need your wallet PIN for a policy or receipt check.

Retention choices

We keep personal records for the period needed for account operation, security checks, support history or legal duties. A deletion request may be limited where a record is still needed for one of those purposes.

Change requests

Ask us to correct account details or explain how your data is used through the support route inside your account. Include the requested change, and we may verify your phone before making an update.

Privacy Policy Answers for Indonesia

These Privacy Policy answers cover the account steps people usually check before opening access. They explain data collection, device handling, wallet records, cookies and contact options in plain language. If your situation involves a particular account or transaction, use the support route inside your account and mention whether the record concerns DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

The Privacy Policy covers details such as your phone number, account activity, sign-in events, device signals, cookie records and payment references. For DANA, OVO, GoPay or QRIS, we may receive transaction status and reference details rather than your wallet PIN.

Phone verification connects an account request with the correct profile and helps protect personal details from an unauthorised request. We may use it before discussing stored data, changing account details or providing a response about a wallet transaction.

Yes. The Privacy Policy covers device and session signals from a mobile browser as well as a desktop browser. These records can help us keep access working, recognise unusual sign-ins and understand why a session ended during an account step.

We use DANA and QRIS references, selected rail details and transaction status to match a payment event with your account. If you contact support, send only the relevant reference and status; never include a wallet PIN or full authentication code.

You can ask for a correction through the account support route. State which detail is wrong and what should replace it. We may verify your linked phone number first, and a requested change remains subject to local law and account security checks.

We retain personal data only while it supports account operation, security, support records or a legal duty. A deletion request may not remove records that must remain for one of those purposes. Support can explain the reason connected to your request.

Open your account and use the support route shown there, then identify your request as a Privacy Policy question. Include your linked phone number and the relevant record type, but exclude passwords, wallet PINs and authentication codes from the message.