Reference

Privacy Policy For Your dax69 Account

The dax69 Privacy Policy explains what account, device and payment details we collect, why we use them and how you can ask about them.

Account dataWallet detailsDevice choicesYour requests
dax69 Privacy Policy For Your dax69 Account
CONTACT ROUTES

Ask About Privacy Through Support

A clear support path helps you question a record without sending unnecessary details. Use the support route available inside your account and identify the email or phone detail connected to the request; we use that step to avoid discussing account data with the wrong person. You can ask about a wallet reference, device sign-in or a message linked to your Privacy Policy rights.

Team online

Account request

Tell us whether you want to access, correct or clarify account data. Include the account phone detail and a short description, but never send your wallet password or full payment credentials through a support message.

Wallet question

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, share the transaction reference and date shown in your account. We use those details to locate the relevant entry without requesting unrelated wallet activity.

Device concern

If a login appears on an unfamiliar phone or browser, contact us through the account support route and mention the device path. We can review the sign-in record and explain the next account-security step.

DATA PRACTICE

How We Handle Account Privacy

We keep our Privacy Policy practical by connecting each data use to an account action: access, wallet matching, security checks, support or a request from you.

Account records

We use the details needed to create and maintain your account, including contact data and verification status. This lets us connect a support request to the correct account without treating every message as an anonymous request.

Payment references

A DANA, OVO, GoPay or QRIS reference can help us match a cashier event. Bank transfer and virtual account records serve the same checking purpose; we do not need your wallet password to trace that reference.

Cookies and sessions

Cookies or similar storage may keep a session active, remember a device choice or protect the path between login and the lobby. Clearing them can sign you out or remove saved preferences without deleting your account data.

Device security

We may retain device type, browser signals and sign-in events to identify unusual account access. On a shared phone, sign out after use and avoid saving your login details in the browser.

Retention choices

We keep records only for the operational, security or legal purpose connected to them. Ask support which category applies to your record, why it remains and whether deletion or restriction can be considered.

Policy requests

You can ask for a copy, correction or explanation of personal data linked to your account. Use the account support route, describe the request plainly and complete any identity check needed before we respond.

Privacy Policy Questions About dax69

These answers focus on the questions we expect you to ask before opening or using an account. They explain the Privacy Policy in terms of phone verification, device access, local wallets and support requests. If your case involves a specific record, use the account support route so we can check the relevant details.

It covers account details, phone verification, sign-in and device records, support messages, cookies and payment references connected to requested account activity. It explains why we use those details, how we retain them and how you can ask for access, correction or clarification.

Yes. The Privacy Policy covers transaction references from DANA, OVO, GoPay and QRIS when they are linked to an account event. We use those references to match or check a record, not to request your wallet password or unrelated wallet activity.

Phone verification helps us connect an account to the person completing the access step and reduces confusion between accounts. The verification status may be retained as an account-security record. We use it for access and support checks described in the Privacy Policy.

Yes. You can ask about device type, browser signals and sign-in events linked to your account. Send the request through the account support route, identify the related phone or email detail and complete any check needed before we discuss the record.

Use the support route inside your account and state which detail is incorrect, such as a contact entry or verification record. Include only the necessary account identifier. We may ask for an identity check before changing data covered by the Privacy Policy.

Retention depends on the purpose connected to the record, such as account access, payment matching, security or a legal requirement. The Privacy Policy does not assign one period to every item. Ask support which category applies and whether a request can be made.

The policy applies to account activity handled for Indonesian access where local law permits. Eligibility depends on local law. If you are unsure about a specific request, contact support through your account and ask which data or access rule applies to your case.