Reference

dian4d Legal Rules For Your Account

dian4d Legal sets out how we handle account access, wallet records, privacy requests and local eligibility before you enter the lobby.

Account termsPrivacy requestsLocal-law accessPolicy contact
dian4d dian4d Legal Rules For Your Account
POLICY CONTACT ROUTES

Get Help With Legal Account Questions

A clear contact route matters when a Legal question affects your account or wallet record.

Account policy desk Ask about Legal wording, phone verification or account access through our support route. We can explain the relevant step and tell you which account detail is needed without asking for your password.
Wallet record help For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, send the payment reference and account phone number. We use those details to locate the matching record.
Privacy request route Request a copy, correction or change concerning your account data through support. State the action clearly, and we will ask for account verification before discussing private records.
DATA HANDLING DETAILS

How dian4d Applies Its Legal Policy

We apply this policy through practical account controls rather than unclear statements. Registration details support account matching, phone verification confirms access before account use, and payment references help us trace wallet status…

Registration records

We use the details submitted during account creation to identify the account connected with your Legal request. Keep your phone number current so policy notices and verification checks reach the right account.

Phone verification

Phone verification is an account step before access. If the number no longer belongs to you, contact support first; do not send a password or one-time code in a message.

Cookie controls

Cookies can keep a session active and help display the correct Legal content on mobile or desktop. Clearing them may require you to sign in again and repeat the account check.

Account security

We treat passwords, one-time codes and wallet references as private account details. Support can discuss a record after verification, but we will not ask you to publish secret credentials.

Retention questions

If you want to know why a record is retained or ask for a change, identify the account and the specific record. We can then assess the request under the applicable Legal terms.

Requesting changes

You may ask us to correct account details or review a privacy request through support. Include the requested change, account phone number and receipt reference when payment history is involved.

Questions About dian4d Legal Access

These Legal answers address the account questions we expect before registration: who may access the service, how verification works, what happens to wallet records and where to send a privacy request. Read the relevant answer before opening an account, particularly if your location or payment record needs clarification.

dian4d Legal covers account creation, phone verification, lawful access, privacy requests, cookies, account security and payment-record handling. It explains the conditions that apply before and during account use.

Yes. Access depends on local law. If you are unsure whether account access is permitted in your Indonesian location, check the Legal notice first and contact support before creating an account.

Phone verification helps connect access to the person who created the account and reduces account-matching errors. Keep your number available during registration, and contact support if it has changed.

DANA and QRIS references are connected to the account that submitted the payment. For a status or privacy request, send the account phone number and receipt reference so we can locate the correct record.

Yes. Send a clear correction request through support from the relevant account. We may ask for verification before changing registration details, especially when the request affects wallet or payment history.

Contact our policy desk and quote the clause or describe the exact step you do not understand. Do not send passwords or one-time codes; we will explain the wording after account verification.

Use the privacy request route through support and name the cookie or record concerned. We can explain its account purpose and assess a change or retention request under the applicable Legal terms.