Reference

Open the mio toto Privacy Policy

The mio toto Privacy Policy shows what account, wallet and device data we use, why we use it, and how you can ask about it before opening an…

Account dataWallet recordsDevice accessYour choices
mio toto Open the mio toto Privacy Policy
HELP WITH ACCESS

Check Privacy Policy help before contacting us

A clear contact path helps when you need to ask how your data was used or why an account record does not match your wallet activity. Start with the account help route for sign-in and phone verification questions, then include the relevant transaction reference when your request concerns DANA, GoPay or QRIS. We use the details you provide to locate the correct record without asking you to send a password.

Team online

Account access

Ask us about phone verification, sign-in records or a device that no longer reaches your account. Include your registered contact detail and the time of the issue, but never send your password or a full security code.

Wallet status

For a DANA, OVO, GoPay or QRIS question, share the visible reference, amount and date shown in your account. We use those details to trace the wallet record while keeping unrelated account activity outside the request.

Data requests

Use our account help path to ask for a copy, correction or deletion assessment under this Privacy Policy. We may first confirm account ownership so a request cannot expose another person’s records.

HOW DATA MOVES

Explore how we protect account data

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

Account details

We handle details such as your registered contact information and verification status to create, maintain and secure your account. The same records help us respond when you ask why access changed or a profile detail needs correction.

Cookie choices

Cookies and related device storage can keep a sign-in session active or show whether a page loads correctly. You can manage browser settings, although removing these tools may require you to complete phone verification again.

Device signals

A phone or desktop session can create technical signals such as browser type, operating system and connection details. We use them to identify unusual access patterns, not to request your private wallet password or read unrelated files.

Account security

Phone verification is part of the account access path, and we may ask for additional account details before discussing a sensitive record. This step helps prevent a third party from receiving your wallet history or changing your profile.

Retention period

We keep different records for different periods, based on their operational, security or legal purpose. When a record is no longer needed for that purpose, we remove it, restrict it or separate it from direct account details where suitable.

Change requests

To request access, correction or a deletion assessment, contact us through the account help route and describe the record involved. We confirm ownership first, then explain what can be changed and any reason a record must remain.

Browse Privacy Policy answers for mio toto

These Privacy Policy answers focus on the questions you may have before opening an account or connecting a local wallet. They explain the practical link between your account, device, payment reference and contact request without asking you to share sensitive credentials.

It covers data connected with account creation, phone verification, sign-in sessions, device access, cookies, wallet references and contact requests. It also explains why we use those records, how retention works and how you can ask for access or correction.

Phone verification helps us connect account access to the person who created the account and helps protect profile and wallet records. If you cannot complete that step, use the account help path and do not send a password or security code.

Yes. The Privacy Policy covers references connected with DANA, OVO, GoPay and QRIS, including visible dates, amounts and confirmation details needed to match a request. We do not need your wallet password to investigate a payment record.

A session may provide technical details such as browser type, operating system, connection data and basic activity signals. We use these details for access continuity, page function and unusual-session checks; we do not use them to read unrelated files on your device.

Retention depends on the reason for holding a record, such as account operation, security checks or a legal requirement. When that reason ends, we remove, restrict or separate the record where suitable, subject to applicable requirements and account requests.

Contact us through the account help route and describe the profile or transaction record that needs attention. Provide the registered contact detail and a visible reference where relevant. We confirm account ownership before changing data or discussing a sensitive record.

You can ask for a deletion assessment through the same contact path. We first confirm ownership and identify the records involved. Some data may need to remain for security, account history or legal reasons, and we will explain that outcome.