Reference

Open the mikasa189 Privacy Policy

The mikasa189 Privacy Policy explains what we collect when you open an account, sign in on mobile, and use DANA, OVO, GoPay or QRIS.

Account dataWallet recordsDevice accessPolicy requests
Explore Our Lobby Read FAQ
mikasa189 Open the mikasa189 Privacy Policy
REQUEST A HAND

Ask us about a privacy request

A clear support route helps when you want to ask about the Privacy Policy or a record linked to your account. Use the support contact shown inside your signed-in account and include the phone number or account identifier connected to the request. If your question concerns a DANA, OVO, GoPay or QRIS reference, attach the receipt or status code but hide passwords and one-time codes. We use the account step to confirm that the request comes from you before discussing personal data.

Team online

Account privacy request

Send a request from the signed-in account path so we can match your identity with the correct record. We may ask you to complete phone verification before sharing account details, changing contact data, or processing a correction request.

Wallet record question

For a payment record, provide the relevant date, rail and reference number. DANA, OVO, GoPay, QRIS, bank transfer and virtual account checks may require the original receipt, while sensitive wallet credentials should never be sent to us.

Access or deletion query

Use our account support path to ask what personal data we hold or whether deletion is available. We first verify the request, then explain any data that must remain for account security, payment reconciliation or a legal obligation.

DATA IN PRACTICE

Explore how we handle privacy

We handle privacy through ordinary account steps rather than vague promises. Sign-in records help us detect unusual access, while device signals help connect a session to the correct account without giving us…

What we collect

We may receive your account name, phone number, verification result, sign-in time, browser type, device signals and messages sent to support. When you open a game such as Live Blackjack Gold or Aviator Fast Round, technical event data may help load the requested page and protect the session.

How cookies work

Our cookies and similar tools can keep your session active, remember a basic preference and help identify abnormal sign-in behaviour. They do not let us read unrelated files, contacts or private messages on your phone. Browser settings can restrict or clear cookies, although account access may then require another sign-in.

Account security

Phone verification is an account security step before access to personal records. We may review sign-in patterns, device changes and failed access attempts to protect your account. Never share a password or one-time code through a support message, even when a wallet receipt needs checking.

Payment matching

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we use reference details to match a payment event with your account. We do not need your wallet password. A receipt can help us investigate a pending status while the payment provider remains responsible for its own processing records.

Retention choices

We remove or anonymise data when it is no longer needed for the purpose that brought it into our systems, unless a longer period is required for security, reconciliation or law. Closing an account does not always erase records immediately because some transaction and support records may still need to be retained.

Changes and contact

You can ask us to correct inaccurate account details, explain a data use, provide eligible access to your records, or assess a deletion request. Send the request through signed-in account support, identify the record clearly, and complete any identity check needed to prevent disclosure to another person.

Find answers about your Privacy Policy

These Privacy Policy answers address the questions we expect Indonesian account holders to ask before opening an account or checking a wallet record. They cover collection, access, cookies, retention and contact steps without replacing the full policy text. If your situation involves a particular payment reference or an account security concern, use the signed-in support path so we can review the correct record.

The Privacy Policy covers data collected during account creation, phone verification, sign-in, lobby access, payment reconciliation and support contact. It can include account identifiers, device signals, cookies, payment references and messages. It also explains how to request access, correction or deletion where that request is available.

We use your phone number to create and secure the account, complete phone verification and help identify the correct account during support. It can also help us investigate an unusual sign-in. We do not need your DANA, OVO or GoPay password to check a payment reference.

Yes. The Privacy Policy covers payment references connected with QRIS, DANA, OVO, GoPay, bank transfer and virtual account activity. We use a reference, amount status and related account details to reconcile the event. Your payment provider may separately retain its own records under its policy.

You can ask us to correct inaccurate account details through signed-in account support. State which field is wrong and provide the account identifier connected to it. We may request phone verification or another reasonable identity check before changing data, so another person cannot alter your account.

On a mobile browser, cookies and similar signals can support sign-in continuity, page preferences and security checks. They do not provide access to unrelated files or contacts. You can clear or restrict them through your browser settings, but doing so may require a fresh account sign-in.

We keep information for the period needed for its stated purpose, account protection, payment reconciliation or a legal requirement. Closing an account may not remove every record immediately because transaction references and support messages can be needed for these purposes. We remove or anonymise data when retention is no longer needed.

Open the support contact inside your signed-in account and describe the Privacy Policy request clearly. Include the relevant account identifier, date or payment reference, but do not send passwords or one-time codes. We may verify your identity before discussing personal data or fulfilling an eligible request.

Related Pages

mikasa189 Indonesia About Us FAQ mikasa189 Casino Access guide