Reference

mikato Privacy Policy for Indonesia

mikato Privacy Policy explains how we collect, use and protect the details connected with your account, device and wallet activity.

Account clarityWallet contextPolicy accessDevice choices
Explore Our Lobby Read FAQ
mikato mikato Privacy Policy for Indonesia
CONTACT ROUTES

Where To Ask About Your Privacy Policy

A clear contact route matters when a wallet receipt, login record or phone detail needs attention. We keep privacy questions connected to the same account help path used for access and payment status checks, so you do not need to explain your account from the beginning each time. When you write, use the email or support contact shown inside your account area and describe the request in plain English. We may ask for account details needed to locate the record, but never ask you to send a password or wallet PIN.

Team online

Account help

Use the account support route when your request concerns phone verification, a sign-in record, stored contact details or a correction to your profile. We check the account safely before discussing personal data, and we keep the response tied to the specific request rather than exposing unrelated account activity.

Wallet status

For a DANA, OVO, GoPay or QRIS question, include the payment method and the relevant receipt or reference details without sharing a PIN. Our team can trace the account-side status and explain which payment record is connected to your request under the Privacy Policy.

Policy request

Ask through the support contact displayed in your account area when you want a copy of stored details, a correction or clarification about retention. We may verify ownership by phone or account step before releasing or changing any personal record.

HANDLING YOUR DATA

How mikato Applies This Policy

Privacy work is part of the account flow, not a separate page we leave unused.

Account details

We may collect the details needed to create and maintain your account, such as contact information, phone verification results and sign-in records. These details help us connect your request to the correct account when you ask about access, correction or removal.

Device signals

When you open the lobby on a phone, tablet or desktop browser, technical signals can help us recognise a session, keep pages working and identify unusual access. We use these signals for account protection and service operation, not as a substitute for your account credentials.

Cookies

Cookies and similar browser storage can remember session choices, support sign-in continuity and help us understand whether a page is functioning. You can manage browser storage through your device settings, although removing it may require you to verify your account again.

Wallet records

A payment selection can create a record showing the chosen route, such as QRIS, DANA, OVO, GoPay, bank transfer or virtual account. We use payment references and status results to reconcile the account, respond to receipt questions and investigate mismatches.

Security checks

Phone verification and sign-in controls help us check that an account request belongs to you. Never send us your password, wallet PIN or one-time code. If access looks unusual, we may pause a request while we confirm the account details through the support path.

Retention requests

We keep records only for the period needed for account operation, security, payment reconciliation or a valid legal requirement. You can ask what we hold, request a correction or ask whether removal is possible; we will explain any record that must remain and why.

Privacy Policy Questions About mikato

The questions below address the account and payment situations most likely to bring you to this Privacy Policy. We have kept the answers practical: what may be collected, how to ask for access, why a device record can appear, and what happens when your request involves a wallet or a law-based retention need. For a personal account question, use the support contact shown after sign-in.

It covers account creation, phone verification, sign-in activity, device signals, cookies, support messages and payment status records. It also explains how we use those details for account access, security, wallet reconciliation and requests to view, correct or remove personal data.

Depending on your account activity, we may receive contact details, verification results, login events, device signals, support correspondence and payment references. We collect the details needed for the stated account purpose, and you can ask support which categories are linked to your record.

Those payment routes can create account-side records such as a selected method, reference number and status result. We use them to match a wallet or QRIS action with the correct account and to respond when a receipt or payment status needs checking.

Send a request through the support contact shown in your account area and describe the records you want to access. We may verify your phone or account details first, then explain the available record and any details that cannot be disclosed for security or legal reasons.

Yes. Contact account support with the detail that appears wrong and the correction you are requesting. We may ask for a phone verification step before changing the record, particularly when the change could affect sign-in, wallet matching or account ownership.

We may use device and browser signals to maintain a session, keep the lobby working and identify unusual sign-in behaviour. Browser cookie controls can remove some stored choices, but you may then need to sign in or complete phone verification again.

The policy explains the same core handling for Indonesian account activity, including wallet and device records. Access or eligibility depends on local law, so some account routes may not apply in every location. Contact support if you need the policy applied to your specific case.

Related Pages

mikato Indonesia Access guide Account information LinkAja Min Deposit Live Baccarat Salon