Reference

mantra 88 Privacy Policy For Your Account

The mantra 88 Privacy Policy explains what account, device and wallet details we collect, why we use them and how you can ask about them.

Account clarityWallet recordsCookie choicesContact route
Explore Our Lobby Read FAQ
mantra 88 mantra 88 Privacy Policy For Your Account
CONTACT THE TEAM

Privacy Questions Have A Clear Route

A direct contact route helps when a Privacy Policy question is connected to a login or wallet status. Start from your account help path and include the email or phone detail linked to the account, plus the payment reference if your question concerns DANA, OVO, GoPay or QRIS. We use those details to locate the right record without asking you to send a full password. If you cannot access the account, tell us which device path failed and request a privacy contact response.

Team online

Account contact

Use the account help path for requests about the Privacy Policy, stored profile details or a correction. Include the account phone or email so we can separate your request from another record, while keeping passwords and one-time verification codes out of your message.

Wallet status

If a DANA, OVO, GoPay or QRIS receipt raises a privacy question, send the transaction reference and date through the cashier-related help path. We can check the payment record without needing your wallet PIN, full card details or a copy of your sign-in credentials.

Access trouble

When the mobile browser or desktop account path stalls, describe the device type, browser step and visible message. That gives our contact team enough context to handle an access request under the Privacy Policy while you keep sensitive login details private.

SIX DATA PROMISES

What We Do With Account Data

Privacy work is part of the account path, not a separate page you have to decode. We explain the main records involved in phone verification, mobile browsing, wallet reconciliation and security checks…

Account details

We use the phone or email details you provide to create the account path, complete phone verification and send account-related responses. Check that these details are yours before access begins, because an incorrect contact record can delay a request to view or change stored data.

Device signals

A mobile browser or desktop browser can provide technical signals such as device type, browser version and session events. We use them to diagnose an access issue and identify unusual sign-in patterns, rather than asking you to share your password or wallet PIN.

Cookie choices

Cookies may keep your sign-in session active, remember a selected setting or show where a page error occurs. You can manage cookie behaviour in your browser settings, although restricting some cookies may interrupt account access or require you to verify the device again.

Payment matching

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference helps us match a cashier event to your account. We keep the reference needed for reconciliation and support, while you should never send a wallet PIN, password or one-time code.

Security controls

Phone verification and sign-in checks help us confirm that an account request comes from the right person. If a sign-in looks unusual, we may ask for an account detail already on file. We will not ask you to disclose your password through a contact message.

Retention requests

We retain records only as needed for the account relationship, security checks, payment reconciliation and required operational handling. Ask us what remains connected to your account, request a correction or ask about closure; some records may need to stay for a stated service or legal reason.

Privacy Policy Answers For Indonesia

These Privacy Policy answers cover the questions we expect when you check the account path from Indonesia. They explain the data connected to sign-in, devices and local wallets without turning a privacy request into a payment request. If your situation is unusual, use the contact route above and describe the exact account step you need us to inspect. Access remains where local law permits.

The mantra 88 Privacy Policy covers account details, phone verification, device and browser signals, cookies, payment references, security checks, retention and privacy requests. It also explains how to contact us when you want to ask about a record connected to your account or wallet status.

We may handle the phone or email detail you submit, verification events, session information and technical device signals from the browser path. These records help us provide account access, investigate a failed login and respond to a request about your stored details.

Yes. The Privacy Policy covers payment references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We use a reference, date or status to reconcile an account event, and you should not send a wallet PIN or one-time code.

Use the account contact path and identify the phone or email linked to your account. State whether you want to view a record or correct it, then include only the relevant payment reference or device detail. We may verify account ownership before responding.

Cookies can retain a browser session, remember a setting or help us locate a technical error. You can change cookie controls in your browser, but blocking some cookies may sign you out or require another phone verification step before the account path works.

We keep account, security and payment-reconciliation records for the period needed to operate the account relationship and handle required obligations. The exact record can differ by purpose. Contact us to ask what remains connected to your account and why it is retained.

You can contact us with a Privacy Policy question from Indonesia, including a request about access, correction or closure. Whether an account service is available depends on local law. Tell us your account contact detail and location context so we can route the request correctly.

Related Pages

mantra 88 Indonesia FAQ Account information bolaonline bimabetslot