Reference

Open disa4d Legal Details Before Account Access

disa4d Legal details put account rules, data handling and access conditions in one place before you open an account.

Account termsData handlingLocal-law accessPolicy requests
disa4d Open disa4d Legal Details Before Account Access
POLICY HELP PATHS

Ask disa4d About Legal Account Steps

A clear contact route matters when a Legal question concerns your account, wallet record or access status.

Account access request If phone verification or account access stops at a Legal condition, use the support path beside the login area. Tell us which step appeared and provide your registered phone detail, without sending a password or full wallet PIN.
Wallet record question For a DANA, OVO, GoPay or QRIS receipt question, attach the transaction reference and date through the cashier support path. We can compare the receipt status with the account record while keeping your payment credentials private.
Policy change request When you want a correction, copy request or clarification under Legal, name the specific account field or paragraph involved. We will use your registered contact route to confirm the request before changing or releasing account-related records.
DATA AND ACCOUNT CARE

Check How Legal Records Stay Managed

Legal handling is practical: we connect account actions to the records needed to operate access, verify phone details and resolve wallet status questions.

Account details

We use the account details you submit to identify the account connected to a Legal request. Before changing a phone detail or releasing a record, we may ask you to confirm the registered contact route so another person cannot redirect the request.

Phone verification

Phone verification is an account access step, not a request for your private wallet code. If the check does not complete, contact support with the displayed status and registered phone detail; keep one-time codes out of messages and screenshots.

Cookies on pages

Cookies can support page operation, session continuity and the route back to Legal pages. Your browser controls how cookies are stored. Clearing them may sign you out or require the phone verification step again when you return.

Payment records

DANA, OVO, GoPay and QRIS references help us match a wallet event to the correct account question. We review the reference, amount shown by the rail and account status, while avoiding requests for wallet passwords, PINs or one-time codes.

Retention requests

Some account and transaction records may need to remain available for account operations, dispute handling or local-law requirements. If you ask what is retained or request a correction, name the record and date so we can assess the specific entry.

Security contact

If you suspect that someone accessed your account, stop sharing codes, sign out on other devices and contact us through the account support route. Include the time, device path and visible account change so we can focus the security check.

Find Answers About disa4d Legal Rules

These Legal answers address the questions that usually come before account access: who may use the service, which records connect to a wallet action, how to request a correction, and where to ask for help. We keep the wording specific to disa4d and Indonesia, while local access remains dependent on local law.

Legal is our section for account conditions, data handling, cookies, policy requests and access wording. It explains what you need before account use, including phone verification and accurate account details. For Indonesia, access depends on local law, so you should check the relevant rule before continuing.

Access is available where local law permits. Your location alone does not replace the account conditions: you must provide accurate details and complete the required phone verification step. If an access question remains unclear, contact support with your registered phone detail before attempting another account action.

Legal handling connects a DANA or QRIS reference with the account and receipt status needed to answer a payment question. We may ask for the transaction reference and date, but you should never send a wallet PIN, password or one-time code through support.

Yes, you can send a correction request through the policy support path and name the exact field that needs attention. We may confirm your registered phone route before making a change. Include the relevant date or account screen, but leave passwords and wallet codes out.

Cookies can keep your session and help return you to the Legal page from the account menu. Browser settings control their storage. If you clear cookies, you may be signed out or asked to complete phone verification again when accessing your account.

The period depends on the type of record and the account or local-law reason for keeping it. Account and transaction entries may remain available for operation or dispute handling. Ask through support with the record type and date if you need a specific retention answer.

Use the account support route linked near login and include the policy page, device path, time and visible account change. Do not send passwords, PINs or one-time codes. If access depends on local law, state the location connected to your question so we can route it correctly.