Reference

Open the miko69 Privacy Policy

miko69 explains how we collect, use and protect the account details behind your lobby access, including wallet activity through DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesPolicy requests
miko69 Open the miko69 Privacy Policy
REQUEST A HAND

Contact us about your privacy choices

A clear account path helps you raise a Privacy Policy question without sending sensitive details through an unknown route. Sign in first where possible, open the account help or cashier-related support path, and include the email or phone number linked to your account rather than a wallet password. We can then locate the relevant record, explain its status and direct a correction or access request. If a wallet receipt is involved, keep the DANA, OVO, GoPay or QRIS reference ready. Support availability and contact instructions are shown in the account area.

Team online

Account contact

Use the support contact shown after account access when you want to ask about the Privacy Policy, stored profile details or a phone verification record. We use the account identifier you provide to match the request and avoid discussing private data with an unrelated person.

Wallet query

For a privacy question tied to DANA, OVO, GoPay or QRIS, include the transaction reference and approximate date, while hiding passwords and one-time codes. Our team can explain which wallet record is being checked without asking you to disclose a secret credential.

Access request

To request a copy, correction or removal review under applicable rules, state the action clearly and use the contact route displayed in your account. We may ask for account verification before releasing or changing personal data, protecting your details from an unauthorised request.

HANDLING YOUR DATA

Explore how we apply the policy

Privacy work is tied to practical account steps rather than broad promises. We separate sign-in details from ordinary browsing signals where our systems allow, record the events needed to investigate wallet status…

Account creation

When you open an account, we collect the details needed for account access and clear phone verification. We use those details to connect your sign-in to the correct profile, show the relevant account area and investigate a failed login without exposing another person’s records.

Device signals

A phone or desktop browser may send device type, browser data, language and access time. These signals help us recognise an interrupted session or unusual sign-in around pages such as Aviator Mobile Play, but they are not a substitute for your account credentials.

Cookie controls

Cookies may keep a session active, remember a setting or help us understand which policy page was opened. You can adjust browser cookie controls, although disabling some cookies may interrupt sign-in or prevent the Privacy Policy from displaying in the expected account path.

Wallet records

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference can appear beside an account event. We use that reference to match a receipt or status query, while your wallet password, PIN and one-time code should remain private and never be sent to support.

Retention periods

We keep information only for the period linked to its purpose, such as maintaining account history, answering a dispute or meeting a legal duty. The period can differ by record type, so a deletion request may remove active profile details while some required transaction records remain.

Change requests

If your phone number, email or other account detail is wrong, contact us through the account support route and identify the requested change. We may confirm ownership before editing it, and we will explain any reason a record cannot be changed or removed.

Find answers about your Privacy Policy

These Privacy Policy answers address the searches we expect from an Indonesian account holder before sharing details with us. They cover the records connected to login, mobile browsing, wallet references and account requests, rather than describing unrelated lobby functions. If your question depends on a particular record or local rule, contact us through the account support path with the smallest amount of detail needed to locate it.

The miko69 Privacy Policy explains how we collect, use, retain and protect details connected with your account, device, cookies and wallet references. It also tells you how to request access, correction or removal, subject to applicable rules and the requirement that access depends on local law.

We may collect details used for account creation, phone verification, sign-in, support and account changes. We can also record device type, browser events, cookie choices and transaction references. We use these records to provide the requested account path and investigate access or wallet questions.

Yes. The Privacy Policy covers references connected with DANA, OVO, GoPay and QRIS, as well as bank transfer and virtual account activity. We may use a reference, date and status to investigate a receipt query, but we do not need your wallet PIN or one-time code.

Cookies may keep a session open, remember a selected setting or help us measure use of a policy page. Your browser provides controls for accepting or removing them. Turning off certain cookies can affect sign-in, account continuity or the way a Privacy Policy page loads.

You can contact us through the account support route and ask for access to personal data connected with your profile. Tell us which record you mean, such as a phone verification event or wallet reference. We may verify account ownership before providing data to the correct person.

Send a correction request through the contact path shown in your account, naming the field that is wrong and the accurate replacement. We may confirm your phone or email before changing it. If a record must remain unchanged for a legal or transaction reason, we will explain that.

Retention depends on the type and purpose of the record. Active profile details may be handled differently from a transaction reference needed for dispute handling or a legal duty. The Privacy Policy describes this approach, and support can explain the next step for a specific deletion request.