Reference

miko toto Privacy Policy explained

miko toto Privacy Policy sets out what we collect, why we use it and how you can ask about your account data before opening access.

Account dataWallet recordsCookie choicesAccess requests
miko toto miko toto Privacy Policy explained
CONTACT ROUTES

Get policy help beside account access

A clear contact path matters when a Privacy Policy question affects your login or wallet record. Start from the support route attached to your account area and tell us the email or phone detail connected to the request. We will use the smallest amount of extra data needed to confirm ownership, including a payment reference when your question concerns DANA, OVO, GoPay or QRIS.

Team online

Account data request

Ask us to locate the account records linked to your verified phone detail. Include the account identifier shown after login so we can reduce back-and-forth during the Privacy Policy request.

Wallet record question

For a DANA, OVO, GoPay or QRIS query, share the transaction reference rather than sending a full wallet screenshot. We use that reference to check the related account event.

Login privacy concern

If a device sign-in looks unfamiliar, use the account support route and describe the date and device path. We can review the access event without asking you to post your password.

HANDLING PRACTICES

What our Privacy Policy does with data

We keep this policy practical: your account records support sign-in, phone verification, wallet matching and requests made through support.

Account security

Phone verification connects account access to the contact detail you provide. We record sign-in events and device signals to help identify an access attempt that does not match your usual path.

Cookie settings

Cookies can remember a selected setting and help us understand page use. You can clear or restrict them through your browser, although some account functions may then need another sign-in.

Payment matching

DANA, OVO, GoPay and QRIS references help us match a wallet event to the correct account. We do not need your wallet password for that matching step.

Data retention

We retain account, support and payment records for the period needed for the stated service, security checks or applicable legal duties. When a record is no longer needed, our process removes it.

Correction request

If your contact detail or account record is inaccurate, contact us through the account support route. Tell us what needs changing and provide enough detail for ownership checks.

Policy contact

Questions about collection, cookies, retention or access requests can be sent through support from your account area. We will explain the relevant policy section and the next step.

Privacy Policy answers for your account

These Privacy Policy answers address the questions you may have before creating an account or checking a wallet record. We keep the route tied to your account so a request can be matched safely, while access remains subject to local law and the wording shown on the current policy page.

It covers account and phone verification data, login and device signals, cookies, support messages, game-category selections and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

We use your phone detail for account verification and access checks. It helps us connect a request or sign-in event to the correct account without asking you to share a password.

Yes. The policy covers payment references and wallet status linked to DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity. We use those references to match account events.

Use the support route inside your account area and request access to your data. Include the account identifier or verified phone detail so we can confirm ownership before responding.

Yes. Send a correction request through account support, describe the inaccurate field and provide the relevant account detail. We may ask for an ownership check before changing the record.

Cookies can retain settings and help measure page use. You can clear or restrict them in your browser, but doing so may remove saved preferences or require another login.

We keep records for the period needed for account operation, support handling, security checks or applicable legal duties. The relevant retention period can vary by record type and purpose.