Reference

Privacy Policy for Your mikato Account

mikato keeps this Privacy Policy close to the account steps you use for DANA, OVO, GoPay and QRIS.

Account dataWallet recordsDevice accessPolicy requests
mikato Privacy Policy for Your mikato Account
HELP WITH PRIVACY

Get Help With Your Privacy Request

A clear contact path helps when your account record, wallet status or device access needs attention.

Account access If you cannot reach your account, tell us which sign-in step stopped and whether phone verification was completed. We use those details to locate the correct record without asking you to send a full payment credential or wallet password.
Wallet records For a DANA, OVO, GoPay or QRIS question, share the transaction reference and approximate date rather than private wallet credentials. We compare the reference with the account record and explain what data we hold about that payment event.
Policy changes To ask for correction, access or removal of personal data, state the request clearly and use the support path beside your account area. We may verify ownership before action, then respond according to applicable law and record requirements.
DATA HANDLING

What This Privacy Policy Covers

We separate the practical parts of privacy handling so you can see what happens after an account action.

Account details

When you open an account, we collect the details needed to create and maintain it. Phone verification may be required before access. We use these details for sign-in, account messages, support identification and requested changes to your personal record.

Device signals

A phone or desktop session may send technical signals such as browser type, operating system, language and session timing. These signals help us keep access consistent between login and the lobby, including when you switch from mobile to desktop.

Cookies

Cookies or similar storage can remember an active session and selected settings. If you clear them, you may need to sign in again or repeat an account step. Browser controls can limit storage, although some access functions may then work differently.

Payment references

A payment record can include a method name, amount reference, status and time. For DANA, OVO, GoPay, QRIS, BCA, BRI, Mandiri or BNI transactions, we use those references to match wallet or bank status with your account.

Security checks

We may examine sign-in events, device changes and unusual payment patterns to protect account access. If a check pauses an action, support may ask for limited verification. Do not send a wallet PIN, password or complete card credential in a request.

Retention requests

We keep records only for the operational, security or legal purpose connected to them, subject to applicable retention duties. You can ask what we hold, request a correction or ask whether removal is possible through the account support path.

Privacy Policy Answers For Indonesia

These Privacy Policy answers focus on the questions you may have before opening an account or connecting an Indonesian wallet. They explain the account path, device behaviour, payment references and ways to contact us. If a request concerns eligibility or access, the outcome depends on local law and the records we must retain.

The mikato Privacy Policy covers account details, phone verification, device and session signals, cookies, support messages and payment references. It explains why we use those records for access, security, wallet status and requests, and how you can ask about your personal data.

Phone verification helps connect account access to the person who created the account and supports security checks when a device or sign-in pattern changes. We may use the verification status when responding to a data request, but you should not send your password or wallet PIN.

Yes. The Privacy Policy explains how we handle payment references linked to DANA, OVO, GoPay and QRIS. We may record a method, status, time and transaction reference so support can match a wallet event to your account without requesting private wallet credentials.

We may receive technical details such as browser type, operating system, language, session timing and device changes. These signals help maintain sign-in security and identify unusual access. They can also explain why a mobile session behaves differently after cookies are cleared.

Use the support path connected to your account and clearly state whether you want access, correction or another privacy action. Include the account phone or email and enough detail to locate the record. We may verify ownership before responding where local law permits.

Retention depends on why a record exists, such as account access, security, payment matching or a legal duty. We remove or anonymise data when the relevant purpose and required period end, subject to applicable rules. You can ask support about a specific record.

You can contact us to ask whether deletion is available for particular account data. We first verify the request and then assess security, payment and legal retention needs. Access or eligibility depends on local law, so some records may need to remain for a defined purpose.