Reference

Inside mini303 Privacy Policy

mini303 Privacy Policy explains how we use the details needed for your account, wallet checks and lobby access, including when you connect DANA or QRIS.

Account dataWallet recordsCookie choicesSecurity checks
mini303 Inside mini303 Privacy Policy
HELP WITH DATA

Contact Us About Your Privacy Policy

A clear contact route helps you act on the Privacy Policy instead of searching through account screens.

Account data request Ask us to locate the account details connected with your phone verification step.
Wallet record question For DANA, OVO, GoPay or QRIS references, tell us which wallet rail and date…
Policy change request If a name, phone detail or privacy preference needs attention, contact us through the…
HOW DATA WORKS

Explore How We Handle Your Account Data

We handle Privacy Policy requests through practical account controls rather than vague promises.

Account details

We use the details you submit to create and maintain your account, confirm phone access and respond to account requests. We do not need your password in a privacy enquiry, and we ask you to avoid placing secret credentials in any message.

Payment references

A DANA, OVO, GoPay or QRIS entry can include a reference, amount status and time needed to match a wallet event. We use those records to trace account activity, not to request your wallet PIN or private login code.

Cookies on devices

Cookies may remember sign-in state, security choices and page preferences on the phone or computer you use. You can manage browser cookie controls, although switching them off may require another account check before the lobby opens.

Account security

Phone verification and sign-in checks help protect the account from an unapproved access attempt. If you change devices, we may ask for another confirmation before showing account or wallet details, particularly after a security signal.

Retention periods

We keep account, payment and security records for the periods stated in the Privacy Policy, based on service operation, dispute handling and legal needs. When a period ends, records are removed or handled according to the stated retention process.

Your request path

You can ask what data we hold, request a correction, question a cookie choice or ask about removal through the policy contact route. We verify the request, explain any lawful exception, and reply with the practical action available.

Browse Privacy Policy Answers for mini303

These Privacy Policy questions address the account and wallet situations you are most likely to face before or after opening an account. Each answer points back to the practical data path: what we collect, why we retain it, how cookies work, and how you can ask for access or a correction. If your case involves a local restriction, the outcome depends on local law.

The mini303 Privacy Policy covers account details, phone verification, sign-in activity, cookies, support messages, security logs and wallet references from DANA, OVO, GoPay or QRIS. It also explains retention, data requests and the circumstances in which local law limits access.

We use your phone number for account creation, verification and account recovery checks. It helps us distinguish your request from another account when you ask about Privacy Policy records. We do not ask you to place a password, PIN or private code in a request.

Yes. The Privacy Policy covers payment references connected with DANA, OVO, GoPay and QRIS, such as a status, timestamp or matching reference. These details help us trace an account event; they do not require us to receive your wallet PIN.

Use the privacy contact route linked from your account area and state which account detail or date you need. We verify ownership before sharing records, then explain the available response. The exact scope of access depends on local law and required security protections.

You can request a correction when an account detail is inaccurate or outdated. Include the relevant field and a safe way to confirm ownership, without sending a password. We assess the request against the Privacy Policy, account security checks and local law.

Cookies can retain sign-in state, security settings and page preferences on your device. Your browser controls can remove or block them, but the next account visit may require another verification step. The Privacy Policy explains which cookie purpose applies to each setting.

Retention depends on the record type and the operational, security or legal reason for keeping it. The Privacy Policy sets out the applicable periods and handling process. You can ask us about a specific account or wallet reference, subject to identity checks.