Reference

Privacy Policy For Your mikasa Account

Our Privacy Policy explains what mikasa collects when you open an account, verify your phone, browse from a mobile device, or use DANA, OVO, GoPay and QRIS.

Clear data purposesWallet records explainedCookie choicesAccount request path
Explore Our Lobby Read FAQ
mikasa Privacy Policy For Your mikasa Account
REQUEST HELP

Get A Clear Privacy Support Route

A direct account path helps you raise a Privacy Policy question without sending sensitive wallet credentials through an unverified route. Sign in, open the support area beside your account controls, and describe whether your request concerns a phone record, cookie choice, payment reference or device entry. If login access is blocked, include the account identifier you can safely provide; we will ask for appropriate checks before discussing private details. Payment receipt and status questions can follow the same support path.

Team online

Account support path

Use the signed-in support area to ask about account data, phone verification or a correction request. We check the account context before discussing private records, so your request stays connected to the right profile.

Wallet record check

For DANA, OVO, GoPay or QRIS references, share the receipt detail shown in your account rather than a wallet password. We can trace the relevant payment record while limiting the data sent in your message.

Blocked access route

If a mobile login or device change prevents access, use the account help route and state the last successful sign-in. We may request phone verification before changing account details or releasing private records.

DATA HANDLING

How We Manage Privacy Requests

Privacy work is tied to practical account events rather than broad promises. We record the steps needed to verify a phone, protect a sign-in, reconcile a wallet reference and answer a data…

Account details

We use the details you enter during account creation to establish your profile and connect later requests to the right account. Review each field before submitting it, especially your phone number used for verification.

Cookies and browser

Cookies may retain session preferences and help the site recognise a returning browser. You can adjust cookie controls in your browser, though limiting them may require another login when moving between the lobby and account pages.

Device signals

A mobile browser or desktop session can create security signals such as device type, session time and approximate connection details. We use these signals to investigate unusual access, not to read private content stored on your device.

Wallet references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account entries may create reference data for reconciliation. We use the reference needed to match a record and do not ask you to disclose a wallet PIN.

Retention period

We retain account, support and payment references only while they serve account operations, legal duties or a genuine dispute. When the applicable need ends, records are deleted or changed so they no longer identify you where feasible.

Changes and contact

You can request a correction, copy or eligible deletion through the account support area. Include the request type and account identifier, and we may complete phone verification before changing or disclosing personal records.

Privacy Policy Answers For Indonesian Accounts

These Privacy Policy answers focus on the account actions you are most likely to take before using mikasa from Indonesia. They cover what we collect, why a wallet reference appears, how browser settings work and how to request a change. If your question concerns a specific DANA receipt, phone check or device entry, use the signed-in support path so we can examine the relevant record without asking for unnecessary credentials.

The mikasa Privacy Policy covers account details, phone verification, login and device signals, cookies, support messages and payment references. It explains how we use those records for access, security, reconciliation and requests, with access depending on local law.

We may collect the details you submit during account creation, your verified phone record, session activity, device signals and support messages. Payment references from DANA, OVO, GoPay, QRIS, bank transfer or a virtual account may also appear when tied to your account.

A QRIS or DANA entry gives us a reference for matching an account transaction or checking a receipt status. It is not your wallet PIN. The same approach applies to OVO, GoPay, bank transfer and virtual account references.

Sign in, open the account support area and request a correction with the relevant field and account identifier. We may complete phone verification before making a change, helping ensure that a private record is not altered by another person.

Where local law permits, you can request deletion of eligible records through the support route. Some account, payment or dispute records may need temporary retention for legal or operational reasons, after which we delete or anonymise them.

Cookies can keep a browser session and selected settings available as you move between account pages and the lobby. You can change browser cookie controls, but restricting them may sign you out or require another phone check on a later visit.

Yes. The Privacy Policy applies to mobile browser access as well as desktop sessions. We may record device type, session time and related security signals, while account data and wallet references remain subject to the same request and retention rules.

Related Pages

mikasa Indonesia mikasa Casino FAQ Access guide Esports PUBG Mobile