Reference

mimpi88 Privacy Policy: Your Data Path

mimpi88 Privacy Policy explains what we collect when you open an account, sign in from a mobile browser, or use DANA, OVO, GoPay and QRIS.

Account clarityWallet contextCookie choicesAccess requests
mimpi88 mimpi88 Privacy Policy: Your Data Path
CONTACT ROUTE

Get Privacy Help Near Your Account

A direct support path helps when you cannot identify a data item or need a correction. Include your account phone number, the page involved and a short description; do not send a wallet PIN or full payment credentials. We use the contact route shown in your account area to check identity before discussing personal data.

Team online

ACCOUNT CONTACT

Use the support contact displayed after sign-in for privacy questions. We may ask for the phone verification step before confirming account data or discussing a correction.

WALLET STATUS

If a DANA, OVO, GoPay or QRIS record looks unfamiliar, share the date and status label rather than secret credentials. We can trace the account event safely.

REQUEST TRACKING

For access or deletion questions, state the exact request in one message. We reply through the available support route and explain any identity or legal restriction.

SECURITY PRACTICE

What Happens To Your Account Data

We keep this Privacy Policy practical: data is grouped by account, payment status, device security and service records. The same approach applies whether you open Baccarat, Aviator or another listed lobby area.

ACCOUNT DETAILS

We use your phone number and account records to create access, verify ownership and respond to account requests. We do not need unrelated profile details for these steps.

WALLET RECORDS

DANA, OVO, GoPay, QRIS and bank-transfer references help us match a payment status with the correct account. We retain only the records needed for reconciliation and support.

DEVICE SIGNALS

A mobile browser may send device, browser and session details that help detect unusual sign-in activity. Cookie controls can change some optional tracking, but essential security records remain active.

COOKIES

Cookies can keep your session available and remember selected settings. You can adjust browser cookie controls, though turning off essential cookies may interrupt sign-in or policy-request handling.

RETENTION

We keep personal data for the period connected to its purpose, account safety, dispute handling or applicable requirements. When that need ends, records are removed or de-identified where suitable.

YOUR REQUEST

Ask us to access, correct or delete personal data through the account support contact. We verify the request first and explain what can be changed under local rules.

Privacy Policy Questions For Indonesia

These Privacy Policy answers address the account steps you are most likely to ask about before opening access. They cover wallet records, mobile browsing, cookies, retention and the support route used by our Indonesian audience.

It covers account details, phone verification, wallet status records, device and browser signals, cookies, security events, retention and requests to access or change your personal data.

We use your phone number to create the account path, confirm ownership before access and locate the correct record when you ask about a wallet status or personal-data request.

Yes. The policy explains that DANA, OVO, GoPay, QRIS, bank transfer and virtual account references may be used to match payment status with your account.

When you use a mobile browser, we may receive browser, device and session signals linked to sign-in security. These signals help identify unusual access without requiring unrelated profile details.

You can adjust cookie settings in your browser. Essential cookies may still be needed for sign-in, account verification and handling a Privacy Policy request through the account area.

Use the support contact shown in your account area and describe the records you want to access, correct or delete. We verify ownership before sharing or changing personal data.

Retention follows the purpose of each record, account safety needs, dispute handling and applicable requirements. When a record is no longer needed, we remove or de-identify it where suitable.