Reference

Privacy Policy for Your Account

Your mulia189 Privacy Policy explains how we handle account details, device signals and payment records when you open an account or use the lobby.

Clear data purposesWallet record contextMobile access detailsContact route
mulia189 Privacy Policy for Your Account
HELP WITH RECORDS

Contact Us About Privacy Policy

A direct request helps us resolve a Privacy Policy question without asking you to repeat account details across several routes.

Account request Tell us which account detail needs correction, such as your registered contact or verification…
Wallet question For a DANA, OVO, GoPay or QRIS record, include the payment rail, date and…
Privacy contact Send a clear request through our available support contact when you want to ask…
HANDLING DETAILS

How We Manage Privacy Requests

Privacy work is tied to practical account events rather than vague labels. We separate account data from ordinary browsing signals where our systems allow, record security checks around sign-in and connect payment…

Account details

When you open an account, we receive the contact and login details needed for that step. We use them to create the account record, support sign-in and respond to requests about your personal data, rather than treating every page visit as a full account profile.

Cookies and sessions

Cookies can keep a session connected while you move from login to the lobby on a phone or desktop browser. They may also help us detect an unusual sign-in. You can manage browser cookie settings, although changing them may affect account access.

Device signals

We may record device type, browser details, approximate session timing and security events to protect account access. These signals help us distinguish a normal mobile visit from an unfamiliar login without requiring you to share private device content.

Payment references

A DANA, OVO, GoPay or QRIS transaction can create a payment reference, amount status and time record linked to your account request. Bank transfer and virtual account records follow the same purpose: matching a submitted payment with the correct account.

Retention period

We keep different records for different periods, based on account operation, security needs and applicable legal duties. When a record no longer serves those purposes, our handling process considers removal or further restriction, subject to local requirements.

Change requests

To request access, correction or removal, contact us with the account detail involved and a safe way to confirm ownership. We review the request before acting, explain any limit, and avoid changing records that must remain for security or legal reasons.

Privacy Policy Questions for mulia189

These Privacy Policy answers address the searches we hear most often from Indonesian account holders. They cover what happens at account opening, how payment references and devices are handled, how cookies affect a session and how you can contact us. If your question concerns eligibility, access depends on local law, and our support route can explain the next safe step.

The mulia189 Privacy Policy covers details you submit when opening or using an account, such as contact data, login details and verification records. We use them for account access, security, support and policy requests. We do not need your password or one-time code to answer a privacy question.

Yes. The Privacy Policy covers payment references connected with DANA, OVO, GoPay and QRIS, including status and timing needed to match an account request. Bank transfer and virtual account records can receive the same treatment. We do not ask you to send a password or security code.

We may handle device type, browser details, session timing and security events when you sign in from a phone or desktop browser. These signals help protect the account and identify unusual access. We do not describe them as access to private content stored on your device.

Cookies may keep your login session connected while you move between the lobby and an account page, and can support security checks. You can adjust cookie settings in your browser. Some changes may interrupt sign-in or require you to confirm the account path again.

You can contact us to request access, correction or removal of eligible personal data. Include the account detail and a safe ownership check. We review each request under the Privacy Policy, and some records may remain where security, account operation or local law requires it.

Retention depends on why a record exists. Account, payment and security records may be kept for account operation, fraud prevention, dispute handling or legal duties. Our Privacy Policy applies different handling periods, and support can explain the relevant process for your specific request.

Use the support contact displayed on our site and state that your request concerns the Privacy Policy. Include your registered contact and the record involved, but not your password or verification code. Access and eligibility depend on local law, including for account holders in Indonesia.