Reference

mislot Privacy Policy For Your Indonesia Account

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

Account dataWallet recordsCookie choicesSupport requests
mislot mislot Privacy Policy For Your Indonesia Account
HELP WHEN NEEDED

Privacy Policy Help Beside Your Cashier

A clear contact path matters when you want to ask about the Privacy Policy or correct an account record. From the account and cashier areas, keep your registered contact detail ready and tell us which policy point needs attention. We can then match your request with the relevant sign-in, wallet or support record without asking you to repeat unrelated account history.

Team online

Policy questions

Use the support desk when you need clarification about the Privacy Policy, cookie choices or the reason a particular account detail is collected. Include your registered contact detail and a short description, so we can identify the correct account record before replying.

Wallet records

If a DANA, OVO, GoPay or QRIS receipt appears incorrectly, send the payment reference through the account support path. We use that reference to locate the related status event, explain what we retain and direct any correction request to the right team.

Account access

For a sign-in or verification concern involving personal data, contact support from the account help route rather than sharing a password. We may ask for account details needed to confirm ownership before discussing, changing or removing information.

DATA IN PRACTICE

How mislot Handles Account Data

We keep the Privacy Policy practical by linking each data use to an account event you can recognise.

Data collected

We may collect your registration details, verification outcome, sign-in history, device signals and activity needed to operate the account. Payment records from DANA, OVO, GoPay, QRIS, bank transfer or virtual account are used to identify and reconcile account transactions.

Cookie controls

Cookies and similar device storage can remember a session and help us understand whether a page loads correctly. The Privacy Policy describes their purpose and your available choices, including what may change when you restrict non-essential storage.

Account security

Your phone verification step helps connect account access to the contact detail you provided. We also examine sign-in and device signals when an event looks unusual, while support will not ask you to disclose your password during a privacy request.

Retention periods

We keep records only for the period needed for the purpose described in the Privacy Policy, account protection, payment reconciliation or a legal requirement. When a record no longer has a valid purpose, our retention process addresses its deletion or restriction.

Change requests

You can ask us to correct account details that are inaccurate or request a copy of personal data linked to you. Start through the support desk with your registered contact detail; we may verify ownership before making a change.

Privacy contact

Questions about collection, cookies, retention or disclosure belong with the privacy support route. Tell us the exact section or account event involved, such as a QRIS receipt or phone check, and we will assess the request under the rules for your location.

Privacy Policy Questions About mislot

These Privacy Policy answers focus on the account actions you are most likely to question before opening access. They cover verification, wallet references, cookies, device records, retention and requests for changes. If your situation is not listed, use the support route with the relevant account or payment reference.

The mislot Privacy Policy covers registration details, phone verification, sign-in and device records, cookies, account activity, payment references and support requests. It also explains retention, correction, access requests and the way eligibility is handled where local law permits.

We use the phone verification step to confirm that the person opening or accessing an account controls the submitted contact detail. The Privacy Policy explains this use, related security checks and how to contact support if the verification record is inaccurate.

Yes. When you use DANA or QRIS, we may retain a payment reference, status response and account link so a cashier event can be reconciled. OVO, GoPay, bank transfer and virtual account records are handled for the same stated purpose.

Send a request through the account support route using your registered contact detail and describe the field or record that needs correction. We may check account ownership first, then assess the request under the Privacy Policy and applicable local rules.

Cookies or similar storage may keep your session active and help us diagnose page behaviour on a phone or desktop. The Privacy Policy describes their purposes and available choices, including possible effects when you restrict storage in your browser.

Retention depends on the purpose of the record, account security needs, payment reconciliation and applicable legal requirements. Our Privacy Policy explains the retention approach; you can ask support about a specific account or payment record through the privacy contact route.

You can request details about personal data linked to your account, including registration, verification, device or wallet references. Contact support with enough account detail for ownership checks, and we will assess the request where local law permits.