Reference

dhx4 Privacy Policy for Your Account

Our Privacy Policy explains how we collect, use, protect and retain information connected with your dhx4 account, wallet activity and support requests.

Clear data purposesWallet activity explainedAccount access controlsRequest path included
dhx4 dhx4 Privacy Policy for Your Account
POLICY HELP PATH

Where to Ask About dhx4 Privacy Policy

A clear contact route matters when you need to understand a record, correct an account detail or ask why a payment reference appears in your account history. Our support path starts from the account and cashier areas, so a question about DANA, QRIS, phone verification or a receipt can stay linked to the relevant case. Please include the account detail you want us to check, without sending a password or full payment credentials. We use the request to locate the right policy process.

Team online

Account questions

Use the account support path when your Privacy Policy question concerns phone verification, login records or the personal details attached to your dhx4 account. We can direct the request to the correct account process without asking you to share your password.

Cashier records

For a Privacy Policy question about DANA, OVO, GoPay, QRIS, bank transfer or virtual account references, start beside the cashier path. Include the receipt reference and date where available so we can check the relevant payment record.

Access requests

If you want to ask about a stored detail, correction or deletion route, identify the account email or phone number connected with your request. We may need an account check before discussing personal data, helping prevent disclosure to the wrong person.

DATA HANDLING

What Our Privacy Policy Does With Data

We keep the Privacy Policy practical by connecting each data category with an account task: phone details support verification, payment references support cashier matching, and device signals help identify unusual access.

Account details

We use the details entered during account creation and phone verification to create your account, support sign-in checks and respond to account requests. The Privacy Policy describes the purpose of each requested detail so you can understand why it is needed.

Payment references

DANA, OVO, GoPay and QRIS activity can create references used to match a cashier event with your account. Bank transfer and virtual account records may serve the same purpose. We use these references for status checks rather than treating them as full wallet credentials.

Cookies and devices

Cookies can keep a session open while you move between the account page and lobby, while device signals can help us identify repeated or unusual access. Your browser settings may control some storage, although changing them can affect sign-in or policy-page behaviour.

Account protection

Phone verification and sign-in checks help us decide whether an account request comes from the account holder. Never send your password in a support message. If a device change or login issue affects your request, tell us which account step stopped.

Record retention

We keep personal and transaction records only for the operational, dispute and legal purposes described in the Privacy Policy. Retention can differ by record type, including a cashier reference or support case. When a record is no longer needed, our process addresses removal or restriction where available.

Changes and contact

You can ask us to correct an inaccurate account detail or explain how a record is used through the policy contact path. We may verify your identity before making a change, and we will apply the request according to the policy, account status and local legal requirements.

Privacy Policy Answers for dhx4 Accounts

These Privacy Policy answers address the account, device and payment questions you may search before opening an account. We keep the wording tied to the actual steps shown in the Indonesian account and cashier paths, including phone verification and local wallet references. Where a request depends on location or legal requirements, we will apply the process where local law permits and explain the next account check.

The Privacy Policy covers account details, phone verification, sign-in activity, device signals, cookies, support messages and payment references. It explains how we use and retain those records for account access, cashier matching, security checks and requests connected with your personal data.

Yes. The Privacy Policy includes references created when you use DANA or QRIS through the cashier path, along with OVO, GoPay, bank transfer and virtual account records. These references help us check payment status and are not the same as storing your full wallet password.

We may use your phone number for account creation, phone verification, sign-in checks and support matching. The Privacy Policy explains the related purposes and retention approach. If the number is inaccurate, use the policy contact path and be ready for an account-holder check.

You can ask about access to or correction of personal data through the account support path. Tell us which detail or record you mean, such as a phone number or cashier reference. We may verify your identity before responding, and the result depends on local law.

The Privacy Policy does not treat every record alike. Account details, payment references and support cases may have different retention periods because they serve different operational, dispute or legal purposes. We remove or restrict records when the applicable process allows, subject to required checks.

Cookies and browser storage can remember a session or page setting while you move between the Privacy Policy, account and cashier areas. You can adjust browser controls, but blocking necessary storage may interrupt sign-in or page behaviour. The policy explains the types and purposes involved.

Start from the account or cashier support path and describe the specific Privacy Policy issue. For a payment record, include the date and receipt reference; for an account request, identify the connected phone or email. Do not send passwords or complete wallet credentials.