Reference

mantra 62 Privacy Policy for Your Account

The mantra 62 Privacy Policy explains what we collect when you open an account, sign in from a mobile browser, use DANA or QRIS, and contact account support.

Clear data purposesWallet record detailsAccount security stepsContact and change requests
mantra 62 mantra 62 Privacy Policy for Your Account
CONTACT ROUTES

Three Ways to Ask About Privacy

A clear account route helps when you want to ask about the Privacy Policy, check a wallet record, or request a correction.

Account support link Use the support route inside your signed-in account for a Privacy Policy question, data request, or concern about an unfamiliar login. We can connect your message to the correct account record when you provide the contact detail used during phone verification.
Wallet record check For a DANA, OVO, GoPay, QRIS, bank transfer, or virtual account question, send the transaction reference rather than a wallet password or full security code. This gives us a focused way to locate the payment record and explain its privacy handling.
Security concern If you notice an unfamiliar sign-in or account detail, contact us through the account support route and change your password before sharing anything else. We use the account identifier and sign-in context to assess the request while limiting unnecessary disclosure.
DATA PRACTICES

Inside mantra 62 Data Handling

We handle Privacy Policy matters around the actual account steps you take: phone verification, mobile-browser login, wallet selection, and support contact.

Account details

We use the contact details and phone verification information you provide to create, secure, and maintain your account. If a requested correction concerns your name, phone number, or email, contact support from the account route so we can match the request safely.

Cookies and sessions

Cookies and similar browser storage can keep your session active and remember practical settings between pages. On a mobile browser, clearing site data may sign you out and remove those settings; you can then sign in again through the normal account path.

Wallet records

A DANA, OVO, GoPay, or QRIS reference helps us connect a payment event to the correct account. Bank transfer and virtual account records may also be retained so we can reconcile status questions without requesting your wallet password.

Account security

We use sign-in context, device signals, and phone verification to help identify unusual account access. Never send us a password or one-time security code. If your mobile browser shows an unfamiliar session, sign out, change your password, and contact support.

Retention periods

We retain account, payment, and support records only for the period needed for the stated service, security work, dispute handling, or applicable obligations. When a record is no longer needed, our handling follows the deletion or anonymisation process available for that record.

Your requests

You may ask for a copy of relevant data, a correction, or clarification about its use through the signed-in support route. Include the account contact detail and request type; we may ask for reasonable verification before changing or disclosing account data.

Privacy Policy Questions From Indonesia

These Privacy Policy answers address the account and payment questions you are most likely to have before opening an account. We keep the wording tied to real steps, including phone verification, mobile-browser sessions, wallet references, and the support path used for data requests. If your situation is not covered, contact us from the signed-in account route and describe the specific record or access concern.

The mantra 62 Privacy Policy covers account details, phone verification, sign-in and device data, cookies, wallet and bank transfer references, support messages, retention, and requests to correct or obtain data. It also explains that access depends on local law and is available where local law permits.

Phone verification helps us connect the account to the contact detail you supplied and helps identify unusual access. It can also support a data request or account correction. We do not ask you to include your password or one-time security code in a support message.

Yes. The Privacy Policy covers references connected with DANA, OVO, GoPay, and QRIS, along with bank transfer and virtual account records. We use those references to match a payment event, answer a status question, protect the account, and handle required record retention.

You can request a copy of relevant account data or ask us to correct an inaccurate detail through the signed-in account support route. Include your account contact detail and explain the request. We may complete a reasonable identity check before disclosing or changing data.

Cookies and similar browser storage can preserve your sign-in session and practical page settings. If you clear site data on your phone, the session may end and settings may disappear. You can sign in again through the account path, subject to local access rules.

Retention depends on the type of record and why it is needed. Account, payment, and support data may remain for service operation, security checks, dispute handling, or applicable obligations. When a record no longer has a valid purpose, deletion or anonymisation may apply.

Use the support link inside your signed-in account and identify the request as a Privacy Policy matter. For a wallet question, provide the DANA, QRIS, OVO, GoPay, bank transfer, or virtual account reference, but never include a password or one-time security code.