Reference

milo4 Privacy Policy for Your Account

milo4 Privacy Policy explains how we collect, use and protect the account details needed for your lobby access, including phone verification before you enter.

Account detailsWallet statusCookie choicesAccess depends on local law
Browse Our Lobby Read FAQ
milo4 milo4 Privacy Policy for Your Account
CONTACT OUR TEAM

Ask About Your Privacy Policy Rights

A direct account-help request gives you a practical route when a Privacy Policy question concerns your phone verification, wallet record or sign-in device.

Account help Use the account-help route when you need to ask about phone verification, a sign-in device or the personal details attached to your milo4 account. We will use the account details supplied in the request to locate the relevant record and explain the Privacy Policy step connected with it.
Wallet status For a DANA, OVO, GoPay or QRIS record, include the wallet name and the transaction reference when you contact us. This lets our team separate a payment-status question from unrelated account data and respond about the specific record covered by the Privacy Policy.
Receipt checks When a bank transfer or virtual account receipt needs checking, send the reference through the available support path rather than sharing unrelated personal details. We use the receipt to trace the account action, then explain what was retained and what request options apply under the Privacy Policy.
HOW DATA IS HANDLED

Explore Our Privacy Controls and Records

We designed this Privacy Policy around the account events you can recognise: phone verification, sign-in, wallet matching and support contact.

Phone verification

Before account access, we use your phone verification details to confirm that the sign-in step belongs to you. We do not need a separate explanation for every lobby title you open, but a verification record can be connected to account protection and a request about suspicious access.

Sign-in devices

When you move between a mobile browser and another device, we may record device, browser and connection signals linked to the sign-in event. These signals help us identify unusual account access. Ask through account help if you want us to explain the device record connected with your account.

Cookie settings

Cookies can keep a necessary session active and remember settings that support your account path. They are handled for the purposes described in this Privacy Policy. You can ask us which cookie category relates to your session and what changes are available for your browser.

Wallet records

A DANA, OVO, GoPay or QRIS reference can be stored with an account action so we can match status questions accurately. For bank transfer and virtual account activity, the relevant reference may identify the transaction route. We do not need unrelated wallet details to answer a policy request.

Retention requests

We keep personal data for the stated account, security, support or legal purpose, then remove or anonymise it when that purpose ends where applicable. Retention can vary by record type. Ask us to explain the period or restriction connected with your specific account record.

Data changes

You can request correction, access or deletion of eligible personal data through account help. Include your account identifier and describe the requested change clearly. We may need to verify the request before acting, so another person cannot alter or obtain your account records.

Browse Privacy Policy Answers for milo4

These Privacy Policy answers address the account and payment questions we hear most often from people in Indonesia. They cover the point at which data is collected, the reason a device or wallet reference may appear, and the account-help route for requests. If your question concerns a record not listed here, contact us with the smallest amount of detail needed to identify it.

The milo4 Privacy Policy covers personal data collected during account creation, phone verification, sign-in, payment-status checks, cookie use and support contact. It explains why we use each category, how account security affects handling, how retention works and how you can request access, correction or deletion where applicable.

We use phone verification before account access to connect the sign-in step with the correct account and help identify unusual access. The verification record can also help us answer an account request. The Privacy Policy explains the purpose and request path for this data.

Yes. The Privacy Policy covers account-linked payment references for DANA, OVO, GoPay and QRIS when they are needed to match a status or receipt question. A bank transfer or virtual account reference can be handled in the same way, with unrelated wallet details excluded from your request.

A mobile browser sign-in may provide device, browser and connection signals associated with that access event. We use them to support account protection and investigate unusual sign-in activity. Ask through account help if you want details about the device record linked to your account.

Send an account-help request describing the specific correction, access request or deletion request you want to make. Include your account identifier and only the payment reference needed for a related record. We may verify your identity before processing the request under the Privacy Policy.

Retention depends on why the record exists, such as account access, security, support, payment matching or a legal need. We remove or anonymise data when the stated purpose ends where applicable. Contact account help to ask about the retention period for a particular record.

Yes. Cookies may support a necessary session and remember browser settings connected with your account path. You can ask us which cookie category was used, why it was needed and what browser changes are available. We will answer using the policy terms that apply to your session.

Related Pages

milo4 Indonesia Access guide Samarinda Live Table About Us Account information