Reference

letnan189 Privacy Policy for Indonesia

Our Privacy Policy explains what we collect when you open a letnan189 account, enter the lobby, or use DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesAccess requests
letnan189 letnan189 Privacy Policy for Indonesia
HELP WITH PRIVACY

Where To Ask About Your Privacy Policy

A clear contact route helps you act on this Privacy Policy instead of searching through account screens. Send a request through the support path linked to your letnan189 account and include the phone number on the account, the subject of your request and any relevant payment reference. Do not send a wallet password or full bank credentials. We may ask for an account step or verification detail before discussing personal data, because the request must come from the person connected to that account.

Team online

Account data request

Ask us to explain the personal data connected with your account, the purpose for holding it and the source of a detail you do not recognise. Include your account phone number so we can route the request without asking you to repeat unrelated payment details.

Wallet record question

If a DANA, OVO, GoPay or QRIS reference appears unfamiliar, send the date, rail name and visible transaction reference through account support. We use that narrow payment context to check status while avoiding requests for your wallet password or complete banking credentials.

Access support

When login or a privacy request stalls on mobile, return to the account support path from the same browser where possible. Tell us whether you used a phone or desktop device and which account step stopped, so we can separate an access issue from a data request.

DATA HANDLING DETAILS

What We Do With Account And Device Data

Privacy Policy choices are easier to understand when each data use has a practical reason. We keep account, device and payment records connected to the action that created them: access, verification, cashier…

Account security

Phone verification helps us connect an account request to the correct account before we discuss personal details. Keep your sign-in information private, and contact support if a device you do not recognise appears in your access history or if an account step changes unexpectedly.

Payment matching

A payment reference, rail name and status can be used to match a cashier event with your account. For DANA, OVO, GoPay, QRIS, bank transfer and virtual account records, we focus on reconciliation details rather than collecting unnecessary wallet credentials.

Cookies and sessions

Cookies and similar browser records help keep a signed-in session working, remember relevant page choices and support security checks. Clearing them can sign you out or remove a saved preference, but it does not automatically erase account records held for access or payment reconciliation.

Device signals

When you move from a mobile browser to desktop, technical signals can change, including browser type, session identifiers and security events. We use these details to protect account access and investigate a support request, not as a substitute for the phone verification step.

Retention choices

We retain personal data only while it serves account access, payment matching, security, support or a legal need that depends on local law. When a record no longer has a valid purpose, our process is to delete it, anonymise it or restrict its use where appropriate.

Changes and questions

You can ask what data we hold, request a correction, question a payment record or ask how cookies affect your session. Include the account phone number and a precise request. We may verify account ownership before making a change, then explain any limit that applies.

Privacy Policy Answers For letnan189

These Privacy Policy answers focus on the account and payment questions you are most likely to have before opening access. They also explain the practical route for correcting data, asking about cookies or checking a wallet record. If your situation is unusual, use the account support path with the smallest amount of detail needed to identify the request.

It covers account details, phone verification, device and session records, cookies, payment references and support messages connected with your use of letnan189. It explains why we use each category, how retention works and how you can ask a question or request a correction.

Those rails can create payment references and status records that need matching with your account. We may use the rail name, reference and outcome to check a cashier event. We do not need your wallet password to investigate whether a DANA, OVO, GoPay or QRIS payment reached the account.

Yes. Send an account data request through the support path and identify the account with its phone number. We may verify ownership before responding. Your request can ask for the categories held, the purpose for use and the payment or device records connected with your account.

Describe the incorrect field and the correction you want through account support. Include your account phone number and, for a payment issue, the relevant rail and reference. We may request a verification step, then correct the record or explain why a specific field must remain unchanged.

Clearing browser cookies can end your session and remove saved page choices on that device. It does not by itself erase account, payment or support records held for operational purposes. After clearing cookies, sign in again and complete phone verification if the account path asks for it.

We keep data while it supports account access, payment matching, security, support or a legal requirement where local law permits. Retention depends on the record and its purpose, not simply the date you last opened the lobby. Ask support about a specific category for a clearer response.

You can ask us to remove or restrict personal data through account support. We first verify the request and check whether a record is still needed for security, payment reconciliation, support or a legal requirement that depends on local law. We will explain any data that cannot yet be removed.