Reference

Legal terms for your letnan189 account

letnan189 sets out the Legal rules behind account access, wallet records and policy requests in one clear place.

Account termsData handlingLocal accessPolicy requests
letnan189 Legal terms for your letnan189 account
CONTACT ROUTES

Get Legal help beside account support

A clear contact path matters when a Legal question affects account access or a wallet record. We ask you to include the account phone number, the subject of your request and any relevant payment reference, without sending a password or full wallet credentials. Our team can then identify whether the issue concerns policy wording, phone verification, a DANA or QRIS status, or a request to update account details. Where local law permits, start with the support route shown beside your account and cashier area.

Team online

Account policy request

Use the account support route when you need clarification about Legal wording, phone verification or access depends on local law. Include your account phone number and the exact clause or screen that prompted your question, so we can route the request without asking for your password.

Payment record question

For a Legal question involving DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, send the payment reference and date shown in your account. We use those details to compare the wallet status with the account record while keeping your secret credentials private.

Access concern

If access is unavailable in your area, contact us through the account help path rather than trying repeated sign-ins. Tell us your country or region and device path; we will explain whether access depends on local law and what policy wording applies to your request.

DATA PRACTICE

How we handle Legal requests

Legal handling is tied to practical account work, not abstract wording. We use account details to process phone verification, connect payment references to the right wallet record and investigate access questions.

Account details

We use the details attached to your account to complete the phone verification step, answer Legal requests and distinguish one account record from another. Send only the details needed for your request, and tell us if a name or phone detail needs correction.

Payment matching

A DANA, OVO, GoPay or QRIS reference helps us match a payment event to the correct account. Bank transfer and virtual account records follow the same matching purpose. We do not need your wallet password, card secret or one-time security code.

Cookies

Cookies can keep the sign-in path and policy notice connected during a session on your phone or desktop browser. If you clear them, you may need to repeat account access steps. Cookie behaviour can vary by browser settings and local device controls.

Account security

Phone verification is required before account access, and repeated or unusual sign-in activity may lead to an additional check. Keep your phone details current and never share a password or security code with anyone contacting you about a Legal request.

Record retention

We keep account, payment and contact records only for the period needed to operate the account, check a transaction or meet an applicable policy duty. Retention can depend on local law, so a deletion request may need a clear reason and account reference.

Changes and contact

To request a correction, access clarification or policy change, contact support through the account help path with your phone number, request type and supporting reference. We review the request against the relevant record and explain the next step where local law permits.

Answers about Legal and account access

These Legal answers address the questions we expect before an Indonesian customer opens an account or asks for a record change. They cover local access, phone verification, payment references, cookies, retention and contact steps. If your situation is specific, use the support route with the smallest relevant set of account details, and remember that access depends on local law.

Legal covers the rules for account access, policy requests, data handling, cookies, payment records and contact steps. We apply those rules to your account and explain limits where local law requires them. Read the page before opening an account so the verification and record process is clear.

Access depends on local law and your location. Where local law permits, you can follow the account path and complete phone verification before access. If the service is unavailable in your area, contact support with your region and device path for a policy-based explanation.

Phone verification connects the account to the contact detail you provide before account access. It helps us distinguish your account from another record when handling a correction, payment question or policy request. Keep the phone detail current and do not share its security code.

DANA and QRIS references help us match a payment event to the correct account and investigate a status question. Send the reference and date shown in your account, but never send a wallet password or one-time code. We handle the request according to applicable local rules.

Yes, where local law permits. Contact support through the account help path with your phone number, the field you believe is wrong and a short reason for the correction. We compare the request with the account record and tell you what further proof, if any, is needed.

Cookies can keep sign-in and policy screens connected in your browser, while account and payment records support access checks and payment matching. We retain records for the period needed for those duties, subject to local law. Clearing cookies may require you to repeat the sign-in path.

Use the support route shown beside your account and describe the policy issue plainly. Add your account phone number, request type and any DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference that matters. Never include your password, wallet secret or security code.