Reference

mini53 Privacy Policy For Your Account Data

Auto Roulette, Cleocatra and QRIS access begin with a clear Privacy Policy, so you can see what we collect before opening an account.

Clear data purposesWallet record detailsPhone verification contextLocal law wording
mini53 mini53 Privacy Policy For Your Account Data
HELP WITH YOUR RECORDS

Where To Ask About Privacy Policy

A clear support route helps when a login record, wallet status or receipt needs checking.

Account help path Use the signed-in account help route for a Privacy Policy question linked to phone…
Wallet status request For DANA, OVO, GoPay or QRIS records, include the payment reference and date rather…
Privacy request Ask us to access, correct or remove eligible personal data through the account support…
SIX HANDLING CHECKS

What Our Privacy Process Covers

We keep this policy practical by connecting each data use to a real account step. Phone verification helps confirm account control, device logs help investigate unusual access, and…

Account details

We handle the contact and login details you provide to create an account, support phone verification and connect your account…

Device signals

Browser, device and session signals can help us recognise unusual access and troubleshoot a mobile path.

Cookie choices

Cookies and similar storage may keep a session active or remember a display setting.

Security checks

We may compare account activity with phone verification and payment references when access looks unusual.

Retention timing

We retain records only for the period needed for the stated account, security, payment reconciliation or legal purpose.

Change requests

Contact us through account help to request a copy, correction or eligible deletion of your personal data.

Privacy Policy Answers For mini53 Accounts

These Privacy Policy answers address the questions we expect before an Indonesian account is opened. They cover the records created during phone verification, mobile access, wallet activity and support requests. If your situation is not listed, use the account help path with a payment reference or account identifier, and we will explain the relevant handling step.

It covers account details, phone verification, device and session signals, cookies, payment references, support requests, retention and the ways you can ask for access or correction.

We use your phone number for account creation and verification before access. It helps connect the request to the correct account and helps prevent another person from changing your records.

Yes. The Privacy Policy covers payment references, amounts, timestamps and status details connected with DANA, OVO, GoPay and QRIS, so a receipt or stalled status can be checked.

We may record browser, device and session signals linked to access security or troubleshooting. These details can help us investigate an unusual login or a mobile display problem.

Use the account help path and ask for a personal data access request. Include your account identifier, then complete any phone verification we request before we release account-linked records.

You can request correction or eligible removal through account support. We will explain what can change, what must be retained for a stated purpose and whether local law affects the request.

Yes. Access and eligibility depend on local law. Our Privacy Policy explains the data process for supported regions, while account access may be limited where local law does not permit it.