Reference

Legal rules for your dede4d account

dede4d Legal sets out how we handle account access, personal data, cookies and payment records before you enter the lobby.

Account termsData handlingCookie choicesPolicy contact
dede4d Legal rules for your dede4d account
POLICY HELP ROUTES

Where to ask about Legal matters

Legal questions are easier to resolve when you send the account detail connected to the issue rather than a general message. We keep policy help close to the account and cashier paths, so you can ask about access, a data correction or a wallet record without describing your full history repeatedly. If you are in Surabaya, the same online contact route applies as for other supported Indonesia regions, subject to local law.

Team online

Account access

Use the account support path when phone verification, an identity detail or a policy acknowledgement prevents access. Include your registered phone number and the exact screen message, but never send your password or wallet PIN.

Wallet records

For a DANA, OVO, GoPay or QRIS record, provide the transaction reference and date through the cashier help path. We can compare the receipt with the account ledger without asking you to share a private wallet credential.

Policy requests

Ask us to correct, explain or remove eligible account data through the Legal contact route. State the request clearly, identify the account holder and tell us which policy section or record needs attention.

DATA AND ACCOUNT CARE

How we apply our Legal policy

We apply the Legal policy to the practical events around your account: sign-in, phone verification, wallet status, support requests and policy changes.

Personal data

We use account details, phone verification results and support messages for account administration, policy handling and payment reconciliation. We do not ask for a wallet PIN or password in a Legal request, and you should redact those details from any receipt.

Cookie settings

Cookies can help keep a sign-in session active and remember choices made on the site. Your browser controls whether they remain available; changing them may affect the account path, policy display or return from a wallet page.

Account security

Phone verification is part of the account access step, and we may ask for matching details when a request concerns personal data. Keep your phone available, use a private device session and contact us if a sign-in event was not yours.

Payment retention

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references may remain connected to account records so we can reconcile status questions. A receipt helps us locate the event, but it does not replace the required account checks.

Policy changes

When a Legal rule changes, we place the revised wording on this page and may ask you to acknowledge it during account access. Check the page before using the account if you have not signed in for some time.

Change requests

You can request a correction or ask what eligible data is held by using the policy contact route. We may verify ownership through the registered phone and account details before changing or disclosing anything.

Common dede4d Legal questions

These Legal answers cover the questions we expect before an account is opened or a policy request is sent. They focus on access, data, cookies, wallet records and contact steps rather than on lobby content. If a situation is specific to your account, use the policy contact route with the relevant reference and registered phone details.

dede4d Legal covers account conditions, access checks, personal data, cookies, wallet records, policy changes and requests for correction or clarification. It also explains that access or eligibility depends on local law and that accurate account details are required.

Access is available where local law permits. Your location and account details may affect eligibility, and phone verification is required before account access. If the access screen does not proceed, contact us with the exact message rather than opening duplicate accounts.

These payment names identify wallet records that may be connected to an account when a status or receipt question is checked. We use the transaction reference and date for reconciliation, while your wallet PIN and password should never be included in a Legal request.

Use the policy contact route and state which account detail or record needs correction. Include your registered phone number and a clear explanation. We may verify account ownership before changing information, and you should remove passwords, PINs and unrelated receipt data.

Yes. Legal explains that cookies can support an active sign-in session and remember site choices. You can change cookie settings in your browser, though doing so may affect the account path, policy display or return from a wallet page.

Wallet and transfer references may remain linked to account records for reconciliation and policy handling. The page does not treat a receipt as permission to bypass checks. For a specific record, send its date and reference through the policy contact route.

Use the account support path for access problems, the cashier help path for DANA, OVO, GoPay or QRIS records, and the policy contact route for data or wording requests. Include the registered phone and exact issue, but never share a password or PIN.