Reference

mikitoto Privacy Policy for Your Indonesia Account

mikitoto Privacy Policy explains what we collect when you create an account, verify your phone, browse Super Sic Bo or use DANA and QRIS.

Clear data purposesPhone verification detailsWallet record controlsCookie choices
mikitoto mikitoto Privacy Policy for Your Indonesia Account
DATA HELP DESK

Ask About Data Beside Wallet Status

A clear account route helps you raise a Privacy Policy question without sending sensitive details through an unverified channel.

Account data request Ask us what account details we hold by using the signed-in support route.
Wallet record question If a DANA, OVO, GoPay or QRIS reference appears incorrectly, send the transaction reference…
Cookie or device query Tell us whether you used an Android phone, iPhone or desktop browser when reporting…
SECURITY PRACTICE

Explore How mikitoto Handles Account Data

Our Privacy Policy is designed around the actual account steps you take, from phone verification to wallet status checks.

Purpose-based collection

We collect contact, login, device and payment-reference details for stated account purposes.

Cookie controls

Cookies can keep your session active and help us see whether pages work on mobile or desktop.

Account protection

Phone verification supports account protection before access is completed.

Retention approach

We retain account, security and payment-reference records only while they serve the stated purpose or a valid legal requirement.

Correction requests

You can ask us to correct inaccurate contact or account details through the signed-in support path.

Policy contact

Questions about the Privacy Policy can be raised through account support, including concerns about cookies, device records, phone checks or…

Browse Privacy Policy Answers for Account Access

These Privacy Policy answers address the searches we hear before account creation and during wallet checks. They cover the records connected with your login, phone verification, device, cookies and local payment references. If your question concerns a specific account event, use the signed-in support route and mention the relevant step without sharing private credentials.

It covers account details, phone verification, login and device records, cookies, support requests and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Phone verification helps connect account access to the right contact detail and supports security checks. We record the verification result and related account event, not your private phone passcode.

Yes. The Privacy Policy covers cookies used for session continuity and page performance on an Android phone, iPhone or desktop browser. Your browser settings can limit cookies, with possible access effects.

We may store payment status, reference number, amount and timing needed to match an account event. We do not need your DANA or QRIS wallet PIN to check a receipt.

Use the signed-in account support route and describe the incorrect field or account step. We may complete a phone verification check before changing contact or account details.

We keep records for the stated account, security or payment-reference purpose, or for a valid legal requirement. After that need ends, we remove or securely handle the records.

Yes. Account access and eligibility depends on local law. Where local law permits, you can read the policy and raise a data question through the account support path.