Reference

Open with Legal clarity for your account

amoy333 sets out the Legal terms behind your account, wallet activity and use of the lobby in Indonesia.

Account termsWallet recordsPolicy accessLocal-law wording
amoy333 Open with Legal clarity for your account
CONTACT ROUTES

Find Legal help beside your account

A clear contact route matters when a policy question affects your account or wallet status. We keep Legal support close to the account and cashier path, so you can send the relevant account step instead of describing the whole issue from memory. Include your registered phone detail and transaction reference when appropriate, but never send a password or wallet PIN. We use the same route for policy wording, data requests and questions about account checks.

Team online

Account policy

Open the support route from your signed-in account when you need a clause explained. We can point you to the relevant Legal wording and tell you which account step is needed before access can continue.

Wallet records

For a DANA, OVO, GoPay or QRIS receipt question, include the transaction reference and rail name. We can match the request with the wallet record without asking you to share a PIN or full security credential.

Data requests

Use the account support path to ask about stored data, correction or deletion. We may ask for phone verification before discussing account records, which helps keep a request connected to the right account.

DATA PRACTICE

Explore how Legal care works

Legal care is practical: we separate account identity, wallet records and site activity so a request can be checked against the right record.

Account data

We use the account details you submit to create and maintain the account path, including phone verification. Keep your registered details current, because an outdated number can prevent us from confirming that a Legal request belongs to you.

Wallet matching

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference may be linked to the related account record. This matching supports receipt checks while keeping the request focused on the transaction rather than unrelated account activity.

Cookies

Cookies can retain a session setting and help us understand which policy page was opened. Browser controls let you remove or block them, although changing those settings may require you to repeat the account sign-in step.

Account security

We use phone verification before protected account details are discussed. If your sign-in or wallet status looks unusual, we may pause the relevant step and ask for confirmation through the account support route.

Record retention

We retain account, support and transaction records for the period needed to operate the service, resolve disputes and meet applicable Legal duties. When a record is no longer needed for those purposes, our handling process moves it toward removal.

Change requests

Ask us to correct, access or remove eligible account data through the support path. State the request clearly, identify the registered phone detail and include a reference number when the matter concerns a wallet record.

Browse answers about Legal access

These Legal answers cover the questions we expect you to ask before opening an account or sending a data request. They explain the practical steps around local eligibility, phone checks, wallet records, cookies and policy changes. If your situation is not covered, contact us through the account support route and include only the details needed to identify the request.

It covers account terms, local eligibility wording, phone verification, wallet records, cookies, security steps, retention and requests to change account data. Read it before opening your account so you understand how the account path operates where local law permits.

Eligibility depends on local law, and access is provided where local law permits. Our Legal wording applies across Indonesia, including Makassar and Denpasar. You should check the rules that apply to your own location before completing the account and phone verification steps.

Phone verification helps us connect a policy, security or data request with the correct account. We may require it before discussing protected records, and you should never send your password, wallet PIN or a full secret credential through support.

DANA and QRIS references may be matched with the related account and transaction record so we can check receipt or status questions. The same approach can apply to OVO, GoPay, bank transfer and virtual account activity when the request needs payment confirmation.

Send a clear request through the account support path and identify the registered phone detail. Tell us whether you want access, correction or removal of eligible data. We may ask for phone verification before discussing or changing protected account records.

We review account, support and transaction records against operational, dispute and applicable Legal needs. Data that is no longer needed for those purposes moves toward removal under our handling process, while records that must be retained remain protected for the required period.

We publish revised wording on the Legal page and identify the policy area affected. Check this page before using the account after a material change. If a clause is unclear, use the support route near your account and ask for the relevant explanation.