Reference

Privacy Policy for Your monata189 Account

monata189 explains what we collect, why we use it, and how you can ask about your account data before opening access.

Clear collection detailsWallet record contextAccount contact routePhone verification notes
monata189 Privacy Policy for Your monata189 Account
CONTACT YOUR WAY

Get Privacy Help Near Account Support

A clear contact route helps when you need a copy, correction, or explanation under our Privacy Policy.

Account support chat Use the support chat inside your account for a Privacy Policy question about login records, phone verification, device access, or a wallet status entry. We can identify the relevant account path more accurately when your request includes the registered contact detail.
Privacy contact form Choose the privacy contact form when you want to ask about stored data, correction, deletion, or retention. Describe the request in plain English and attach only the details needed to locate your account; payment passwords and one-time codes are never needed.
Receipt status check For a question about a DANA, OVO, GoPay, QRIS, bank transfer, or virtual account record, send the transaction reference and date through support. We use those details to compare the account ledger with the payment status without requesting your wallet password.
SECURITY DETAILS

Know What Your Privacy Policy Covers

We keep the Privacy Policy practical by describing the data flows you meet during account access, wallet activity and support.

Data we receive

We may receive your name, phone number, email address, login events, phone verification result, device signals, support messages and account activity. Payment records can include a DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference, but not your wallet password.

Why we use it

We use account and transaction data to provide access, match a receipt, answer support questions, detect unusual login behaviour and maintain accurate records. A request linked to Two Factor Setup may require security event details so we can explain the account action.

Cookies and devices

Cookies can keep a session active and help us understand whether you return from a phone, tablet or desktop. Device signals may be compared with login activity when access changes. You can manage browser cookie settings, although some account functions may then need another sign-in.

Account protection

Phone verification and sign-in checks help us confirm that an account request comes from the account holder. We do not ask for your wallet password or one-time code in support messages. If a new device appears, we may request another account check before changing contact details.

Retention approach

We retain account, support and payment records for as long as needed for the purpose described in the Privacy Policy, including security, reconciliation and legal duties. Retention can differ by record type and depends on local law; we remove or anonymise data when it is no longer needed.

Your requests

You can contact us to ask for access, correction, clarification or deletion where local law permits. We may verify your identity before responding, especially when a request affects phone, email, DANA, OVO, GoPay or QRIS records connected with your account.

Privacy Policy Answers for Indonesian Accounts

These Privacy Policy answers address the account and wallet questions you may search before opening access. We keep the wording direct so you know what to prepare, which records may appear, and how to reach us when a request needs account verification. Where local law permits, the available request rights can depend on your location.

The monata189 Privacy Policy covers account details, phone verification, login and device records, cookies, support messages, payment references, security activity and retention. It also explains how to ask for access, correction or deletion where local law permits, without asking you to share a password.

No. Our Privacy Policy describes payment references such as a DANA or QRIS transaction number, status, amount and time, rather than your wallet password. The same approach applies to OVO, GoPay, bank transfer and virtual account records used to match an account entry.

Device details help us recognise login patterns, keep a session working and investigate an unusual access attempt. The Privacy Policy treats these signals as security and service records. A new phone may lead to another phone verification step before contact details are changed.

Use the privacy contact form or account support chat and state that your request concerns the Privacy Policy. Include your registered email or phone number and a clear description of the records you want. We may verify account ownership before providing or changing data.

Yes, you can ask us to correct inaccurate account details where local law permits. Send the affected field and the correct value through support, along with your registered contact detail. For a payment record, include the DANA, OVO, GoPay or QRIS reference and date.

Retention depends on the record and the purpose described in our Privacy Policy. Login, support and payment records may be kept for security, reconciliation and legal duties. The applicable period depends on local law, and data may be removed or anonymised when no longer needed.

Start with the account support chat if you can sign in, or use the privacy contact form if you need a dedicated data request route. Tell us whether the question concerns access, correction, deletion, cookies, device records or a wallet transaction reference.