Reference

dana69 Privacy Policy For Your Account

The dana69 Privacy Policy explains what we collect when you open an account, verify your phone, use the lobby and connect DANA, OVO, GoPay or QRIS.

Account clarityWallet data controlCookie choicesRequest access
dana69 dana69 Privacy Policy For Your Account
CONTACT ROUTES

Privacy Help When Account Details Need Care

A clear contact route helps you ask about personal data without explaining your whole account history.

Account support Send a privacy request through the account contact path when you need to ask what details are linked to your dana69 profile. We may ask you to confirm the phone verification step before discussing account-specific records.
Payment status If a DANA, OVO, GoPay or QRIS reference appears in your account history, include the date and reference shown to you. Our support route can use that detail to separate a wallet question from a broader data request.
Security concern Tell us promptly if a sign-in record or device signal does not look familiar. We may pause the conversation until account ownership is checked, helping prevent private account details from being sent to the wrong person.
HANDLING YOUR DATA

How We Apply This Privacy Policy

Our handling process separates account access, payment matching and security signals so a single support request does not expose more than it needs to.

Account records

We use the details supplied during account creation and phone verification to connect you with the correct profile. Sign-in events and account changes may be recorded so we can check ownership when you ask about access or request a correction.

Payment references

Wallet and bank records are handled as transaction references rather than as a reason to collect unrelated material. DANA, OVO, GoPay, QRIS, bank transfer and virtual account details help us match status checks to the account step that created them.

Device signals

When you move between a mobile browser and desktop, technical signals may help us recognise unusual access or protect a phone verification step. These signals support account security and are not a substitute for confirming your identity when a request concerns private records.

Cookies

Cookies and similar browser storage can remember session choices, support sign-in flow and help us understand whether a page request worked. You can manage browser storage through your device settings, although removing it may require you to complete account access steps again.

Retention steps

We retain account, security and transaction records for as long as needed for the purpose described in this policy, account administration and applicable legal duties. When a record is no longer needed, our handling process is designed to remove or separate it from active account use.

Change requests

You can ask us to correct account details, explain a data use, or provide a copy where applicable. Send the request through account support and include the phone or account detail needed for verification; we will explain any lawful reason a request cannot be completed.

Privacy Policy Answers For dana69 Accounts

These questions address the practical points Indonesian account holders usually check before sending a privacy request. Each answer stays within the scope of our Privacy Policy, from phone verification and cookies to payment references and account deletion questions. If your situation is not listed, use the account support path and describe the specific record or action you want us to examine.

It covers account details, phone verification, sign-in and device records, cookies, payment references and support requests. It also explains why we use those details for access control, security and payment matching, with availability and eligibility handled where local law permits.

Phone verification helps us connect an account request to the person controlling the contact number. It can also protect a privacy request, because we should not disclose account records or change details until the account path has been checked.

Yes. The Privacy Policy covers transaction references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account steps. We use those references to match payment status to your account, not to request unrelated wallet details.

You can send a correction request through account support. Include the account or phone detail needed to locate your profile and describe the exact field that looks wrong. We may verify ownership first, then explain the correction step or any legal restriction.

Cookies can keep a session active, remember selected settings and help us see whether a page request completed. You can clear or restrict them in your browser or device settings, but you may need to repeat sign-in or phone verification afterward.

We keep each category only for the period needed for its stated purpose, account administration, security checks and applicable legal duties. Retention can differ for account, payment and security records. Support can explain the category involved in a specific request.

Use the account support contact path and write the Privacy Policy topic clearly, such as access, correction, cookies or payment references. Add the account detail needed for verification, but do not send a password or unnecessary wallet credentials.