Reference

mgo55 Privacy Policy for Your Account

Our mgo55 Privacy Policy explains what account details we use, why wallet records may be checked, and how you can request access or changes.

Clear data purposesWallet record handlingAccess request pathCookie choices

Browse Our Lobby Read FAQ

What This Policy Covers in Indonesia

mgo55 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

This Privacy Policy covers details collected when you open an account, complete phone verification, sign in, contact support, or use a wallet route. We may record account identifiers, device signals, session activity, payment references and support messages so we can protect access and match a transaction

1
to the correct account. DANA, OVO, GoPay, QRIS, bank transfer and virtual account references are used for payment status checks, not as a reason to collect unrelated details. We share details only for stated operational needs, such as processing a requested wallet action or protecting an
2
account. Where local law permits, you can ask what we hold, request a correction, or ask us to explain a retention period.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT ROUTES

Where To Ask About Your Data

A clear support path helps when a privacy question follows a login or wallet check. Use the support route shown in your account area and include the account phone number, the subject of your request, and any relevant payment reference. We use those details to locate the correct record without asking you to send a full wallet password or private authentication code.

Team online

Account access

If phone verification or sign-in exposes a privacy concern, use the account support path and describe the step that failed. We will ask for enough detail to locate your record.

Wallet records

For DANA, OVO, GoPay or QRIS questions, include the transaction reference and date rather than a password. This lets us check the payment record while limiting extra account details.

Policy requests

For access, correction or deletion questions, identify the account phone number and requested action through our support path. We may verify account control before making any change.

DATA PRACTICE

How We Handle Account Data

Our privacy process follows the same account steps you see on the site: identify the account, check the relevant record, and respond through the available support path.

Account details

We use your submitted account details to create access, complete phone verification, maintain sign-in records and respond to support requests. We avoid collecting details that do not serve one of those purposes.

Device signals

Your browser or mobile device may provide session and security signals, such as a device type or sign-in time. These help us spot unusual access without reading unrelated device content.

Cookies

Cookies can keep a session active, remember selected settings and help us understand whether a policy page loaded correctly. You can manage cookie behaviour through your browser settings.

Account security

Phone verification and sign-in checks help connect requests to the correct account. We will not ask you to disclose a password or one-time authentication code in a support message.

Retention periods

We retain account, support and wallet records for the period needed for the stated purpose, security checks and applicable legal duties. A request can ask us to explain the relevant period.

Changes and requests

You can ask to access, correct or remove eligible details through the support path. We may confirm account control first, then explain what can change and when the update applies.

Privacy Policy Questions Before Opening

These Privacy Policy answers focus on the decisions you make before opening an account: which details are needed, how wallet references are handled, what your device shares, and how to reach us. If your question concerns access or eligibility, the applicable position depends on local law.

The mgo55 Privacy Policy covers account details, phone verification, device signals, cookies, support messages and wallet references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

We use your phone number to create and identify your account, complete phone verification and connect a privacy request to the correct record. We do not ask for your authentication code in support messages.

Yes. The Privacy Policy covers payment references and status checks connected with QRIS, DANA, OVO, GoPay, bank transfer and virtual account routes. These records help match a requested transaction to your account.

You can request access through the support path shown in your account area. Include your account phone number and the request subject; we may verify account control before responding.

Send a correction request through the support path and identify the account record that needs updating. We will check the request, explain any required verification and confirm the resulting change.

We keep account, support and wallet records for the time needed for their stated purpose, security checks and applicable legal duties. You can ask support to explain the period for a specific record.

Yes. The Privacy Policy explains cookies and device signals used for sessions, settings and security. You can also manage cookie behaviour through your browser settings and contact support with a specific concern.

mgo55 Privacy Policy for Your Account

Where To Ask About Your Data

Account access

Wallet records

Policy requests

How We Handle Account Data

Account details

Device signals

Cookies

Account security

Retention periods

Changes and requests

Privacy Policy Questions Before Opening

01 What does the mgo55 Privacy Policy cover?

02 Why does mgo55 need my phone number?

03 Does the Privacy Policy cover QRIS and wallet records?

04 Can I request a copy of my mgo55 account details?

05 How do I correct details under the Privacy Policy?

06 How long does mgo55 keep account records?

07 Can I ask about cookies or device tracking?

Related Pages