Reference

asu66 Legal for Indonesia Account Access

asu66 Legal sets out how we handle account access, payment records and policy questions for you in Indonesia.

Policy termsPhone verificationIndonesia accessWallet records
asu66 asu66 Legal for Indonesia Account Access
POLICY HELP ROUTES

Policy Questions Around Wallet Status

When a Legal question affects your account, we keep the support path close to the wallet and login steps. Tell us whether the matter concerns phone verification, a DANA or QRIS receipt, a withdrawal check, or access that depends on local law. Include your account contact detail and transaction reference where available, but do not send a password or full payment credentials. We can then direct the request to the right policy or account-handling step.

Team online

Account access

If phone verification has not opened your account path, contact our support desk with the registered contact detail and the screen message you received. We use that context to check the access record without asking you to share your password.

Wallet status

For DANA, OVO, GoPay or QRIS questions, send the payment reference and amount shown in your receipt. We compare that record with the wallet status attached to your account and explain the next policy step.

Policy request

For a correction, access concern or account-closure request, identify the policy point and your registered contact detail. We route the request for a written response and may ask for a further ownership check.

DATA HANDLING PRACTICE

How We Handle Legal Account Duties

Legal handling is practical: we limit account checks to the details needed for access, payment matching and policy requests.

Account data

We use your registered contact detail and verification result to connect you with the correct account. Keep that contact detail current, because a mismatch can delay access checks or make a policy request harder to confirm.

Payment records

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference may be retained to reconcile your transaction. We do not need your wallet password for that check, and you should never send it to us.

Cookies

Our account pages may use cookies or similar session tools to keep your login path connected to the correct account area. They help preserve navigation and security signals; clearing them can require you to verify access again.

Account security

Phone verification is an account-security step before access is enabled. If a device changes or an account detail looks unusual, we may pause the access path while we check ownership rather than expose account data.

Record retention

We retain account, payment and policy records for the period needed to handle transactions, disputes, security checks and legal duties. A retention question should include your registered contact detail so we can locate the right record.

Change requests

To request a correction, deletion assessment or explanation, contact the policy support route with the specific record involved. We may verify account ownership first, then confirm what can be changed under applicable local law.

asu66 Legal Questions About Your Account

These Legal answers cover the account, data and access questions we hear before an Indonesian account is opened. They also clarify what happens when a wallet receipt needs checking, when a phone verification step is incomplete, or when you want a policy record corrected. If your situation is different, use the policy support route with the relevant account reference.

asu66 Legal covers account access, phone verification, payment records, cookies, security checks, retention and policy requests. Eligibility depends on local law, so we assess access in the relevant location before connecting your account to the lobby or wallet path.

Yes, phone verification is part of our account-access process. We use the result to connect you with the correct account and reduce mistaken access. If the check does not complete, contact support with the registered contact detail and screen message.

We may retain the DANA or QRIS reference, amount and account link needed to match a transaction. Those details help us check wallet status or a receipt question. Never send a wallet password; provide only the reference requested through the support route.

You can request a correction by identifying the account record and the change needed. We may first verify ownership through your registered contact detail. After checking the request, we explain whether the record can be amended under applicable local law.

We retain records for the period needed for transaction matching, security checks, disputes and legal duties. The exact period can depend on the record and applicable local law. Ask through the policy route with your account reference for a record-specific response.

It can, because access depends on local law and completed account checks. We may pause lobby access when phone ownership, location or account details need confirmation. Once the required check is complete, we explain the available account path.

Use our support route and state whether your request concerns access, data correction, cookies, a wallet record or account closure. Include your registered contact detail and any relevant transaction reference, while keeping passwords and full payment credentials private.