Reference

dana4d Privacy Policy for Your Account

The dana4d Privacy Policy explains how we handle your account details, device signals and payment references when you use our Indonesia site.

Account dataWallet referencesCookie choicesContact requests
dana4d dana4d Privacy Policy for Your Account
CONTACT ROUTES

Privacy Questions Follow Your Account Path

A clear contact route helps you ask about the Privacy Policy without sending payment details into an unrelated message. When you contact our support team from the account or cashier path, include the account identifier, the subject of your request and the relevant date. You can ask us to explain a data field, check a wallet reference or direct a correction request. For a payment concern, keep the DANA, OVO, GoPay or QRIS receipt reference available, but do not send a password or one-time access code.

Team online

Account contact

Use the support route connected with your dana4d account when you want to ask about personal data, a stored phone detail or a Privacy Policy request. We can match the conversation to your account path more accurately when you provide the registered contact detail without sharing your password.

Payment status

If your question concerns a DANA, OVO, GoPay or QRIS reference, mention the transaction date and receipt code through the cashier support path. We use those details to locate the relevant record while avoiding a request for your full wallet password or private authentication code.

Access concern

When a sign-in or verification problem affects your privacy request, tell us the device type and the step that stopped, such as phone verification before account access. We can separate an account-access issue from a data request and explain the next contact step clearly.

DATA PRACTICES

Six Practical Privacy Checks We Apply

Privacy work is part of the account flow, not a page we expect you to read once and forget.

Account records

We use your contact details, verification result and sign-in history to establish the account path and protect it from unusual access. If a detail changes, contact us through the account route so we can confirm the request before updating the record tied to your profile.

Payment references

A payment record may show a method such as DANA, OVO, GoPay, QRIS, bank transfer or virtual account, together with amount and status references needed for reconciliation. We do not need your wallet password to investigate a receipt or compare a cashier status.

Cookies

Cookies and similar browser storage can keep a session available, remember a selected setting and help us see whether a page loads correctly. You can manage browser storage through your device settings, although removing it may sign you out or require phone verification again.

Device security

We may use device, browser and network signals to identify a changed sign-in pattern and protect your account. This does not replace your responsibility to keep access details private. On mobile, close the dana4d browser session after use, especially when the device is shared.

Retention period

We retain account, support and payment-related records only for the period needed for the stated service purpose, dispute handling, security checks or applicable legal duties. The exact period can depend on the record type, so ask support which category applies to your request.

Changes and requests

You can ask us to explain, correct or assess deletion of personal data through the account contact path. Include the registered contact detail and a clear request. We may need to verify ownership first, so another person cannot change your account records without confirmation.

Privacy Policy Questions About dana4d

These answers address the privacy questions most often connected with account creation, wallet records and mobile access. If your circumstances are different, send the specific request through the account contact path and we will assess the relevant record category. Eligibility and access remain dependent on local law.

The dana4d Privacy Policy covers account details, phone verification, sign-in activity, device signals, cookies, support conversations and payment references. It explains why we use each category, how retention can work and how you can contact us about correction, access or another privacy request.

Yes. The Privacy Policy includes references linked to DANA and QRIS, as well as OVO, GoPay, bank transfer and virtual account activity. These records can contain a method, receipt reference, status and date used to match a cashier event without requesting your wallet password.

Use the support route connected with your dana4d account and state whether you want an explanation, correction or assessment of deletion. Provide the registered contact detail and the affected field. We may verify account ownership before changing anything, which protects your profile from an unauthorised request.

Device and browser details help us protect account sessions, identify unusual sign-in patterns and diagnose a page that fails on mobile or desktop. They can also show whether cookies are available. We use these signals for the stated operational purpose and do not treat them as your wallet password.

The Privacy Policy allows retention for the period needed for account operation, payment reconciliation, support handling, security checks, disputes or applicable legal duties. The period can differ by record category. Ask support about a particular account or receipt record rather than assuming one period covers every field.

You can contact us through the account path and ask which personal data category relates to your request. We may confirm ownership using the registered contact detail before responding. Do not include your password or one-time code. Any response remains subject to applicable law and access conditions.

This Privacy Policy is written for the Indonesia account flow and covers local references such as DANA, OVO, GoPay and QRIS. Site access and eligibility depend on local law, and the service is available where local law permits. Contact support if your location affects a privacy request.