Reference

dian4d Legal access for your account

dian4d Legal explains how account access, wallet records and policy requests work before you open an account.

Account termsData choicesWallet recordsLocal-law access
dian4d dian4d Legal access for your account
CONTACT ROUTES

Where to ask about Legal access

A clear contact path helps when a policy question affects your account, wallet record or access status.

Account access Tell us if phone verification, a sign-in step or a policy notice prevents access.
Wallet record For DANA, OVO, GoPay or QRIS questions, send the payment reference and approximate time…
Policy request Ask us to clarify a Legal clause, data choice or account-status decision.
DATA PRACTICE

How Legal data choices work

We handle policy records around the account rather than treating every request as a general lobby question.

Data handling

We use account details to operate access, check phone verification and respond to a Legal request.

Cookie choices

Cookies can support sign-in continuity and page settings on your device.

Account security

Keep your password and phone verification details private, and contact us through the account route if a sign-in event looks…

Record retention

Some account, verification and payment records may remain while they are needed for account administration, dispute handling or legal duties.

Correction request

If your account detail is inaccurate, send the affected field through the policy contact route.

Access decision

When local law affects eligibility or account access, we explain the policy basis available to us.

Legal answers before account access

These Legal answers cover the questions we expect you to ask before opening an account or sending a wallet payment. They explain how dian4d handles access, data, cookies and account requests without replacing the policy wording itself. If your situation is specific, use the account contact path and quote the relevant clause.

It covers account access, phone verification, data handling, cookies, payment references, retention and policy requests. It also explains that access and eligibility depend on local law, so the available account path may differ by your location.

Yes. A policy or jurisdiction rule can affect whether an account step is available. Where local law permits, we explain the relevant status through the account contact route and identify whether phone verification or another account detail is required.

We use the payment reference, account connection and timing to identify a DANA or QRIS event. Do not send a password. If a receipt needs checking, provide the reference through the account support path so the Legal request stays tied to your account.

Yes. Send the incorrect field and your account contact detail through the policy request route. We may ask for phone verification or another matching account step before making a correction, so the change is applied to the right record.

Cookies may support sign-in continuity, page settings and policy-page preferences. If you want clarification, tell us your device and browser path. We can explain the relevant cookie choice and how it connects with the Legal wording.

Retention depends on why a record is needed, such as account administration, payment tracing, dispute handling or legal duties. Ask us about the category involved, and we will explain the applicable reason and any local-law limitation.

Use the account support route shown on the site and quote the clause, notice date or event reference. Include only necessary details, such as a QRIS receipt reference, and we will direct the question to the appropriate policy path.