Reference

How mikasa 189 Handles Your Personal Information

When you open an account with us, you share data — and we take that seriously. This page explains what we collect, why we collect it, how your payment details from DANA, OVO, and GoPay are handled, and what rights you have over your…

Account data protectionDANA, OVO, GoPay wallet privacyYour right to access and deleteSecure data storageContact us to update your info
mikasa 189 How mikasa 189 Handles Your Personal Information
REACH OUR PRIVACY TEAM

How to Contact Us About Your Data

For any question about what data we hold on your account, how your DANA, OVO, or GoPay wallet reference is stored, or how to request a correction or deletion, our support channels are open around the clock. Players in Bandung and anywhere else in Indonesia can reach us through live chat, email, or directly via the account settings page — whichever is fastest for you.

Live Chat Reach our support team directly through the live chat on site. Available around the clock — share your account details and your data request gets logged immediately.
Email Support Send your privacy request by email and we will respond with a reference number. This is the preferred path for data deletion or correction requests on your account.
Account Settings Some personal details — display name, contact number, linked wallet — can be reviewed and updated directly inside your account settings without contacting support.
DATA HANDLING STANDARDS

How We Protect and Manage Your Account Data

Every account on our platform sits behind SSL-encrypted connections, and wallet references from GoPay, OVO, or DANA are never exposed in plain text in our systems. Cookies we set are limited to what keeps your session working smoothly — we do not pass your browsing behaviour to outside advertising platforms. If you close your account, your data is retained only for the minimum period required and then cleared from active storage. At any point while your account is active, you have the right to ask what we hold and to request changes.

Encrypted Storage

Your account credentials and wallet references are stored with encryption. We apply SSL across all account pages so data in transit — including your DANA or OVO session — is protected.

Cookie Use

We use session cookies to keep you logged in and functional cookies to remember your lobby preferences. No cookies are shared with third-party ad networks without your awareness.

Data Retention

We keep your account data for as long as your account remains open and for a defined period after closure. After that window, personal data is removed from active systems.

Your Access Rights

You can request a copy of the personal data we hold, ask us to correct inaccurate details, or request deletion of your account data. These rights apply where local law permits.

Your Privacy Policy Questions

These are the questions we hear most often about how your data is handled on mikasa 189. If something is not covered here, live chat and email support are both available around the clock to help with specific account and data queries.

We collect your name, contact details, and login credentials at registration. Once you transact, we also log the wallet reference from DANA, OVO, or GoPay to match deposits and withdrawals to your account.

No. We only record the transaction reference and wallet identifier needed to verify a transfer. Your PIN and wallet password stay entirely within your own e-wallet provider's system.

Yes. Contact us through live chat or email with your account details and we will provide a summary of the personal data we hold. This right applies where local law in Indonesia permits.

Send a deletion request via email or live chat. We will verify your identity against your account, process the request, and confirm once your data has been removed from active storage.

We set session cookies to keep you logged in and preference cookies for lobby settings. You can manage cookies through your browser settings, though turning off session cookies may affect account access.

We retain account data for a defined period after closure as required by applicable rules, then clear it from active systems. The exact window depends on the type of data and local regulatory requirements.