Reference

Legal Terms Before You Join

Our legal page sets out how access, account records, wallet activity, cookies, and support contact are handled on dadu4d.

Indonesia access rulesDANA wallet recordsOVO account checksGoPay and QRIS context
dadu4d Legal Terms Before You Join
LEGAL HELP

Contact Paths for Legal Questions

A legal question should reach the right queue, not a general inbox.

Live chat legal queue Use live chat from your logged-in account between 09:00 and 23:00 WIB.
Account message route Open your account menu, choose Help, then send a message linked to your registered…
Wallet record check For GoPay, QRIS, DANA, or OVO questions, include the transaction time and visible reference…
ACCOUNT RECORDS

How We Handle Legal Data

Legal handling depends on clear account records. We store only what we need to operate your account, respond to support questions, check wallet activity, and keep access decisions aligned with local law.

Account identity

We connect legal requests to your registered phone number, account name, and login history. This prevents a third party from changing profile details or asking about wallet activity that belongs to you.

Cookie use

Cookies help us remember sessions, language display, and basic device signals. You can clear them from your browser settings, but a fresh login may be required before support can verify your account path.

Wallet references

DANA, OVO, GoPay, and QRIS records may appear in wallet checks, support replies, and account history. We use the reference, time, and amount shown on your account rather than private wallet access.

Security checks

If a login pattern changes, we may ask for account confirmation before answering a legal request. The check can include your registered phone, last wallet rail used, and recent device session.

Retention period

We keep legal and wallet records for as long as needed for account operation, dispute handling, and applicable obligations. When a record is no longer needed, we aim to remove or separate it from active account use.

Change requests

To ask for a correction, send the request from your account message route and state the field that needs updating. We may ask for one account step before changing legal or wallet-related details.

Questions About Legal Use

These answers cover the legal points you are most likely to check before opening or using an account. They focus on access, account data, cookies, wallet records, contact routes, and how we respond when a correction or account question is raised. If your case involves local law, availability depends on that law and applies only where it permits.

Availability is not the same in every place. Access and eligibility depend on local law and are available only where local law permits, so we may restrict account use if a location or account check requires it.

We may use your registered phone number, account name, login time, device session, wallet reference, and support history. These details help us answer access, correction, and wallet-record questions with a clear account trail.

Yes, send the request from your logged-in account through Help or live chat. Tell us which field needs correction, and we may ask for a phone or wallet confirmation before any legal account detail is changed.

We use those rails as wallet references inside your account history and support cases. We do not need your private wallet password; the visible reference, time, and account match are usually enough for checking.

Cookies can support session recognition, device checks, and language display. If you clear cookies, you may need to log in again, and support may ask one extra account step before handling a legal request.

Use live chat from 09:00 to 23:00 WIB or send an account message through Help. Include your registered phone, device type, and the legal access question so the case reaches the correct queue.

Ask through your logged-in account and specify the date range, wallet rail, and transaction reference if available. We will check what can be shared with you based on account ownership and applicable rules.