Reference

Legal terms for your net 4d account

net 4d Legal terms show how we handle account access, wallet records and policy requests before you open the lobby.

Account termsPayment recordsLocal access
net 4d Legal terms for your net 4d account
CONTACT ROUTES

Legal help beside your account path

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

Account access Use the account help route when a Legal rule affects verification or sign-in. Share your registered phone details and the message shown on screen; we can explain the next account step without asking for your password or wallet PIN.
Wallet records For a DANA, OVO, GoPay or QRIS record, send the payment reference through the cashier support path. We can compare the receipt, account status and displayed transaction state before asking for any further evidence.
Policy requests Ask for a policy clarification or correction through support with the exact page point you mean. We will identify the relevant Legal contact, explain the request path and tell you what account detail is required to proceed.
RECORD PRACTICE

How our Legal handling works

Legal handling is practical: we separate account access, payment evidence and policy requests so each record reaches the right check.

Data handling

We use submitted account details for access checks, support replies and payment matching. A receipt from DANA, OVO, GoPay or QRIS should contain only the reference needed for the request, not your private wallet PIN or password.

Cookie choices

Cookies can keep a Legal page preference or active session available on your device. You can manage browser cookie settings, but removing session cookies may require you to sign in again before viewing account pages.

Account security

We treat phone verification and account credentials as separate security steps. Do not share a password or one-time code in a support message; if access changes, use the account path so the request can be matched safely.

Record retention

We retain account and transaction records only for the operational, security or policy purpose connected to the service. A retention question should include the record type and account contact so we can identify the applicable handling rule.

Policy updates

When Legal wording changes, we publish the revised terms in the policy area and may ask you to acknowledge an affected account step. Check the date shown with the text before relying on an older saved copy.

Change requests

To request a correction, identify the inaccurate field, explain the requested change and provide a safe contact route. We may ask for account verification before editing records, and we will not use a public message for private account data.

Answers before you open an account

These Legal answers focus on the questions we expect you to ask before account access, payment connection or a policy request. Read the terms shown at sign-up as well, because a local rule can affect whether access is available. If your situation is not covered, send the relevant account or payment reference through the support route without sharing secret credentials.

Legal on net 4d explains the conditions for account access, policy use, data handling and payment records. It does not replace local rules: access depends on local law. Read the current terms before opening an account and contact support if a specific condition is unclear.

Access from Indonesia is available only where local law permits. Your location, account details and the applicable policy can affect eligibility. We may ask you to complete phone verification before account access, and you should confirm that using the service is lawful for you.

Legal terms explain why we may use a DANA or QRIS reference to match a cashier record and resolve a status question. Send the transaction reference through support, but do not send your wallet PIN, password or one-time code with the request.

We use the account details needed for verification, sign-in support and payment matching. Phone verification can be required before access. If you ask about a stored field, identify the record safely; we may verify ownership before discussing or changing private account data.

Send the exact field, the correction you want and a secure account contact through the policy support route. We may request verification before editing the record. Include a payment reference only when it is relevant, and remove wallet PINs and passwords.

Cookies may keep a session active or remember a policy preference on your device. You can change browser settings to remove them, although sign-in may be required again. The Legal policy explains the purpose connected with each cookie setting shown to you.

Use the account or cashier support path that matches your question, then state that the request concerns Legal. Include your registered contact and the relevant page or transaction reference. We will direct it to the appropriate policy contact without requesting secret credentials.