Reference

dewi111 Legal terms for your account

Clear Legal terms help you understand account access, wallet records and requests before you enter the lobby.

Account access wordingWallet record clarityLocal law conditions
dewi111 dewi111 Legal terms for your account
CONTACT ROUTES

Where Legal questions reach us

A clear contact route matters when you need a policy answer rather than a lobby explanation.

Account access For Legal questions about phone verification, account ownership or access where local law permits, use the account support route and describe the exact step that stopped you.
Wallet records If DANA, OVO, GoPay or QRIS status does not match your receipt, contact us beside the cashier with the reference and requested account action.
Policy requests For a copy, correction or removal request involving your account records, use the support contact shown after login and state the Legal request in plain English.
RECORDS AND CONTROL

How we handle account records

We keep this Legal area practical by connecting each policy point to an account action. Your phone verification supports account security, payment references help us trace wallet questions, and cookie controls affect…

Data handling

We use account and payment details to provide account access, match DANA, OVO, GoPay or QRIS records, answer requests and address issues connected with Legal obligations.

Cookie choices

Cookies can help keep a session active and remember selected settings. You can manage browser cookie controls, though changing them may affect the login path or cashier display.

Account security

Phone verification is part of the account access step. Keep your password and verification code private, and contact us through the account route if a detail looks unfamiliar.

Record retention

We keep records for the period needed to operate the account, trace payment references, resolve disputes or meet a legal requirement. Retention can differ by record type.

Correction requests

If your account details are outdated or incorrect, request a change through the support path after login. Include the affected field so we can assess the correction.

Who handles requests

Our account support route receives Legal, privacy and access questions, then directs them to the team responsible for the relevant record or policy action.

Legal answers before you open

These Legal answers cover the questions we expect you to ask before creating an account in Indonesia. They explain eligibility, records, wallet references, account changes and the practical route for contacting us. If your situation is not covered, sign in only where local law permits and send the specific question through the account support path.

The Legal page explains account access, phone verification, payment records, cookies, data handling, retention and request routes. It also states that eligibility depends on local law and may vary by location.

Access depends on local law. You should continue only where local law permits, and you remain responsible for checking whether account access is lawful in your Indonesian location.

Phone verification helps connect the account to the correct account holder and supports security checks before access. Do not share the verification code with another person or through support messages.

DANA and QRIS references may be used to match a cashier action, investigate a status question or resolve a dispute. Keep your receipt and send only the reference requested through our support route.

Yes. Use the support path shown after login, identify the field that needs correction and explain the requested change. We may need account checks before updating or removing a record.

Retention depends on the record and the reason it is needed, such as account operation, payment tracing, dispute handling or a legal requirement. The relevant handling route can explain a specific record.

Use the account support contact shown after login, or the route beside the cashier for a payment-related matter. Include the topic and reference, but exclude passwords and verification codes.