Reference

Privacy Policy for Your mimo slot Account

mimo slot Privacy Policy explains what we collect when you open an account, use the mobile lobby, or check DANA and QRIS status.

Account dataWallet recordsDevice accessPolicy requests
mimo slot Privacy Policy for Your mimo slot Account
HELP WITH REQUESTS

Get Privacy Help Beside Account Support

A clear contact route matters when you want to ask about the Privacy Policy, correct an account detail or question a wallet record. Use the support path connected to your account area and include the phone number linked to your profile, the relevant request and any receipt reference you can safely share. We use those details to locate the right record without asking you to send a password or full payment credentials.

Team online

Policy questions

Ask how we collect, use or retain your account details. Include the policy point you mean and the phone number linked to your account so our support team can identify the relevant record without requesting your password.

Wallet record checks

If DANA, OVO, GoPay or QRIS activity appears unfamiliar, send the date, wallet name and visible reference number through account support. Please hide passwords, PINs and complete bank details; we only need enough context to locate the event.

Correction requests

When your phone verification detail or account record needs correction, tell us what appears wrong and what should change. We may ask for an account step that confirms ownership before changing personal data or closing access to an old record.

DATA HANDLING

What We Do With Your Account Data

The Privacy Policy is designed around the records our Indonesia account flow actually creates. We separate account identity, wallet status and device-session signals so a support request can be checked without exposing…

Account collection

We collect details you enter for account creation and phone verification, along with records needed to maintain account access. The Privacy Policy explains why each category is used, so you can distinguish required account data from session or preference data.

Payment matching

DANA, OVO, GoPay and QRIS references help us connect a wallet action with the correct account status. Bank transfer and virtual account records serve the same checking purpose. We use transaction context, not your wallet PIN, for account support checks.

Cookie choices

Cookies can keep a session or remember a device setting while you move from login to the lobby. Our Privacy Policy explains their role and limits. Clearing browser data may remove convenience settings, but it does not erase records already required for account handling.

Device security

A phone or desktop session can create technical signals such as browser or device details. We use these signals to spot unusual access and protect your account. They are not a substitute for phone verification, and support will not ask for your login password.

Retention timing

We retain account, wallet and support records only for the purposes described in the Privacy Policy and for periods shaped by operational or legal needs. When a record is no longer needed, our handling follows the applicable retention process rather than an informal deletion promise.

Your requests

You can ask what personal data we hold, request a correction or raise a concern about use. Send the request through account support with enough detail to verify ownership. Some requests may depend on local law and the status of the related account record.

Privacy Policy Answers for Indonesia Accounts

These Privacy Policy answers focus on the questions that arise during account access, phone verification and local wallet activity. We keep the wording practical so you can decide what to share, how to contact us and what to expect when a record needs checking. For a case-specific request, use the support route connected to your mimo slot account.

It covers account details, phone verification, device-session data, cookies, support messages and wallet references connected with DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. It also explains our purposes, retention approach, security handling and the requests you can send.

Phone verification helps us connect account access and privacy requests to the correct person. It can also reduce mistaken changes when two records look similar. We use the verification step for account protection and will not ask you to disclose your password or wallet PIN.

Our Privacy Policy distinguishes payment references from secret credentials. We may handle a DANA or QRIS reference, status and support context, but you should not send a PIN, password or complete security code through support. Contact us with the visible transaction details only.

Cookies may keep a login session, remember a device preference or help the account path open consistently on mobile. The Privacy Policy describes their purpose and limits. Clearing cookies can remove saved settings, while account and transaction records remain subject to the stated retention process.

Yes. Send a correction request through account support and identify the account detail that appears wrong, such as a phone verification record. We may confirm ownership before making a change. The available action depends on local law and the nature of the record.

Retention varies by record type and purpose. Account, wallet and support entries may need to remain available for security, service checks or legal needs. Our Privacy Policy sets the governing approach; support can explain the relevant category without promising deletion outside applicable requirements.

Use the support path linked to your account and state that your request concerns the Privacy Policy. Add your account phone number, request type and safe reference details. Do not include passwords or PINs. We can then route the question to the team handling data requests.