Reference

Open asio4all with clear Legal terms

asio4all Legal sets out how your account, wallet records and lobby access are handled in Indonesia.

Account termsPayment recordsLocal-law accessSupport route
asio4all Open asio4all with clear Legal terms
POLICY HELP ROUTES

Check Legal questions through account support

A clear support path helps when a Legal rule affects your account or payment record. Start from the account help route and include the phone detail connected to your profile, along with…

Account access If your phone verification does not complete, contact us through the account help path and describe the exact step that stopped. We can check the account record and explain which Legal condition applies before you attempt another access request.
Payment records For a DANA, OVO, GoPay or QRIS question, include the payment reference and account phone detail. We can use the receipt and status information to identify the relevant transaction record without asking you to repeat unrelated account details.
Policy requests When you want clarification, correction or removal of account data, state the request plainly through support. We will explain the available route, any identity check required and whether local law affects the way we can act.
DATA HANDLING PRACTICE

Understand how Legal protects your account

Our policy practice connects Legal wording with the account actions you actually take. We record the details needed to verify access, match a payment receipt and answer a policy request, rather than…

Data purpose

We use account details for identifiable operational purposes such as phone verification, access checks and payment-status matching. If you ask why a particular detail is needed, our support route can explain its connection to the Legal process.

Cookie use

Cookies can help keep your account session and policy page behaviour consistent on a mobile browser or desktop. You can ask support about cookie-related handling when a setting affects access, and we will describe the relevant request path.

Account security

Phone verification is part of the account access path before wallet activity is connected to your profile. Keep your phone details current and do not share account credentials; a change request may require checks against the existing record.

Payment retention

Payment references such as QRIS, DANA or bank transfer records may be retained so we can match receipts, investigate status questions and respond to account enquiries. Ask us what applies to your specific record instead of sending duplicate payment details.

Correction requests

You can ask us to correct an account detail that is inaccurate. Include the affected field and the phone detail linked to your profile; we may need to confirm your identity before changing information used for access.

Contact ownership

Send Legal requests through the account support route so the right record is reviewed. We can address policy wording, data handling, access conditions and payment evidence there, while any eligibility decision depends on local law.

Find answers about asio4all Legal

These Legal answers cover the questions you may have before opening an account or asking us to change account information. We focus on the practical steps: where the policy applies, what details connect to your account, how payment records are handled and how to send a request. If your situation is not covered, use the account support route and include only the details needed to identify the issue.

asio4all Legal covers account access, phone verification, payment-record handling, cookies, data requests and policy contact routes. It also explains that eligibility or access depends on local law. Read the notice before opening an account, especially if your access location or account details have changed.

Yes. Access and eligibility depend on local law. Where local law permits, we show the available account route and apply the policy wording connected with that route. If you are unsure, contact support before creating or changing an account.

We may use DANA and QRIS references to match a receipt or payment status with the account phone detail you provide. Include the relevant reference when asking for help. We do not need unrelated account information to begin checking that record.

You can send a correction request through account support. Name the detail that is inaccurate and provide the phone detail linked to your profile. We may ask for an identity check before changing information used for phone verification or account access.

Retention can depend on the record and the purpose for which it is needed, including receipt matching, status checks or account enquiries. Ask support about your specific payment reference and we will explain the applicable Legal route rather than giving a general estimate.

Yes. Cookies may help maintain a consistent session when you open the Legal page or account route on a mobile browser. Contact support if a cookie setting changes your access behaviour, and include your device path so we can explain the relevant handling.

Use the account support route and identify your request as Legal. Add the account phone detail, the policy clause or payment reference involved, and the action you want. We can then explain the next check, available correction path or local-law condition.