Reference

minislot Privacy Policy for Your Account

minislot Privacy Policy explains how we handle the account, wallet and device details connected with your access.

Account dataWallet recordsDevice detailsCookie choices

How Wallet Data Is Used

minislot Service availability depends on jurisdiction. Users are responsible for checking local law before access.

This Privacy Policy describes the data we collect when you create an account, verify your phone, sign in, contact support or use a payment route. That can include your account details, verification records, transaction references, device identifiers, cookie settings and messages sent through our contact path.

1
DANA, OVO, GoPay and QRIS may return payment status or reference data needed to match an account action; bank transfer and virtual account records can serve the same purpose. We use these records to provide requested access, identify unusual sign-in activity, resolve a wallet-status question and
2
meet applicable obligations. Access depends on local law, and some features or account actions may not be available in every Indonesian region. We will explain a relevant change through the account or policy path where practical.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT ROUTES

Where To Ask About Your Data

A clear contact path helps you ask what we hold, why we use it or how to correct an account detail.

Policy questions Use our support contact path for questions about the Privacy Policy, collection purposes or a notice shown during phone verification. We will first match the request to your account.

Wallet records For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, include the payment reference and date. This helps us locate the relevant account event without requesting your wallet password.

Access requests Ask us to access, correct or remove eligible personal data through the same support route. We may confirm ownership using your verified phone before making a change.

DATA CONTROLS

Six Controls Behind Our Privacy Policy

We handle this policy area through practical account steps rather than broad promises. Phone verification connects a request to the right account, session controls help us identify unfamiliar device activity, and payment…

Collection purpose

We collect only the details needed for account access, phone verification, requested wallet processing, security checks, support replies and records required by applicable rules.

Cookie settings

Cookies and similar device storage can remember session choices and help us understand whether a sign-in flow is working. Your browser settings can limit or remove them.

Account security

We use phone verification, sign-in checks and device signals to reduce unauthorised account access. Never send us a wallet password or one-time code in a support message.

Record retention

We keep account, payment and support records for the period needed to provide the requested service, resolve disputes, protect access and meet applicable legal duties.

Policy changes

If our handling practices change, we will revise this Privacy Policy and show the updated date or notice through the policy path before the change affects a relevant request.

Your request path

You can ask about access, correction or eligible removal by contacting support with your account identifier. We may need identity checks before releasing or changing private data.

Privacy Policy Questions Before Account Access

These Privacy Policy answers cover the practical questions we expect before an Indonesian account is opened or a wallet action is requested. If your situation is not listed, use the support route and include the account step or payment reference involved.

It covers account details, phone verification, device and session data, cookies, payment references, support messages, retention and requests to access or correct eligible personal data.

We use phone verification to connect an account request to the right person, protect sign-in activity and reduce mistaken changes. We do not need your DANA, OVO or GoPay password.

Yes. The Privacy Policy explains how payment references and status details from DANA, QRIS, OVO, GoPay, bank transfer or virtual account routes can be matched to an account event.

Contact us through the support path linked near your account area, state that you want an access request and provide your account identifier. We may verify your phone first.

Yes. Send the incorrect field and the requested correction through support. We will assess the request, check account ownership and update eligible records where the change is supported.

We retain payment and account records for as long as needed for the requested service, security checks, dispute handling and applicable legal duties. The period can differ by record type.

Yes. Access depends on local law. Some requests, account actions or data disclosures may have limits where local law permits, and support will explain the relevant next step.

minislot Privacy Policy for Your Account

Where To Ask About Your Data

Six Controls Behind Our Privacy Policy

Collection purpose

Cookie settings

Account security

Record retention

Policy changes

Your request path

Privacy Policy Questions Before Account Access

01 What does the minislot Privacy Policy cover?

02 Why does minislot need phone verification data?

03 Does the policy cover DANA and QRIS activity?

04 How can I request a copy of my account data?

05 Can I ask minislot to correct my personal data?

06 How long does minislot retain payment records?

07 Does local law affect privacy requests or account access?

Related Pages