Reference

Privacy Policy for logam189 Account Access

Our Privacy Policy explains what we collect when you open a logam189 account, use DANA or QRIS, and move between the lobby and cashier.

Account recordsWallet activityCookie choicesSecurity requests
logam189 Privacy Policy for logam189 Account Access
REQUEST SUPPORT

Contact Us About Your Privacy Policy

A clear support route helps when your account record or wallet reference needs attention. Use the contact path connected to your account and include the email or phone detail used during access, plus the payment reference if your request concerns DANA, OVO, GoPay, or QRIS. We ask for enough detail to locate the correct record, but never ask you to send a password or wallet PIN. If you browse from a phone, you can reach the same privacy request path without installing an app.

Team online

Account request

Send a privacy request from the contact path linked to your account. Include the account email or phone detail so we can match your request without asking for your password or a wallet PIN.

Payment record

For a DANA, OVO, GoPay, QRIS, bank transfer, or virtual account question, add the transaction reference and date. We use those details to locate the relevant status without requesting private wallet credentials.

Access concern

If a browser session or phone account shows unfamiliar activity, tell us which device you used and when you noticed it. We can direct the account-security check while keeping the privacy request separate.

DATA PRACTICES

Explore How We Handle Account Details

Privacy controls work best when they match the real account journey. We separate identity details from payment references where practical, limit staff access to records needed for a…

Account data

We collect the details needed to create and protect your account, including contact information and phone verification status.

Payment references

A DANA, OVO, GoPay, or QRIS transaction gives us a reference, amount status, and timing for reconciliation.

Cookies

Browser cookies can retain session, language, and security settings so you do not repeat the same account step on every…

Account security

Phone verification and session checks help protect access before you reach the lobby.

Retention period

We keep each record for as long as its stated purpose requires, or longer when a legal duty applies.

Change request

Ask us to access, correct, delete, or clarify personal data through the account contact path.

Browse Privacy Policy Answers for logam189

These Privacy Policy answers focus on the questions you may have before opening an account or connecting an Indonesian wallet. We explain the account step, browser behaviour, payment references, retention, and contact route in plain terms. If your situation is not covered, use the support path with the smallest amount of personal detail needed to identify your record.

It covers account details, phone verification, browser and device records, cookies, payment references, security checks, retention, and requests about your data. It applies when you use the account journey, lobby, or cashier from Indonesia where local law permits.

No. For DANA and QRIS, we use transaction references and status details to match a payment with your account. Wallet credentials remain with the payment provider. Do not send us a PIN, password, or full wallet login in a support request.

Phone verification helps connect the account to the correct contact detail and supports session protection before account access. We record the verification result and related security event, not more personal data than the account and security purpose requires.

Use the contact path linked to your account and ask for a data access request. Include the account email or phone detail used at sign-in. We may ask for an identity check before sharing records, and the response depends on local law.

Yes, you can request a correction or deletion through account support. We first identify the relevant record, explain whether it can be changed, and tell you if a payment, security, or legal retention duty means part of it must remain.

Cookies can remember your session, language, and security settings in a mobile browser. You can clear or restrict them through browser controls, but removing essential cookies may require you to repeat login or phone verification before access.

Retention depends on why the record exists. Account security and payment reconciliation records remain while needed for those purposes, or longer when required by applicable rules. You can ask support which category applies to a specific record and request clarification.