Reference

Open your mpo555 Privacy Policy

Our Privacy Policy explains what we collect when you open an account, verify your phone, sign in from mobile, or use DANA and QRIS.

Account recordsWallet activityCookie choicesPolicy requests
mpo555 Open your mpo555 Privacy Policy
CONTACT ROUTES

Use the right privacy contact path

A clear request route helps us locate the correct account record without asking you to send unnecessary details.

Account contact path Use the privacy contact route displayed inside your account when you want to ask about stored details, a policy point or the status of an earlier request.
Wallet record query For a DANA, OVO, GoPay or QRIS record question, mention the relevant reference and date. We use those details to separate wallet history from unrelated account activity.
Access assistance If login or phone verification blocks a privacy request, explain the step that stopped you. Do not send a password; we use account checks before discussing personal records.
DATA PRACTICES

Explore how we handle your data

We keep the Privacy Policy practical by connecting each data practice to a visible account action.

Data we receive

We may receive your phone number, account settings, verification result, device details and activity records. Payment references can identify DANA, OVO, GoPay, QRIS, virtual account or bank transfer events.

Cookie controls

Cookies and similar browser storage can remember a session path or security preference. You can manage browser permissions, although changing them may require another login or affect saved choices.

Account protection

We use phone verification, session checks and device signals to reduce unauthorised access. Never share your password or verification code, even when a message appears to discuss a wallet record.

Retention approach

We retain records for the period needed to provide account access, resolve payment questions, protect against misuse and meet applicable legal duties. The period can differ by record type.

Sharing boundaries

We disclose personal records only when needed for an account service, a security process, a payment check or a lawful request. We do not treat your Speed Baccarat or sports activity as public material.

Change requests

You can ask us to correct account details, explain a record or review a request under applicable law. Include the affected account step so we can assess the change accurately.

Find answers about Privacy Policy

These Privacy Policy questions cover the points you are most likely to check before opening an account. We explain the account path, wallet references, mobile access, cookies and request process in plain terms. If your situation is different, use the privacy contact route shown in your account and avoid sending passwords or verification codes.

It covers account details, phone verification, device and session records, cookies, game or sports activity references, wallet history and the ways we respond to lawful access or correction requests.

We may store transaction references, status and timing connected with DANA, OVO, GoPay or QRIS. The Privacy Policy explains how those records support account checks without exposing your wallet credentials.

A device type, browser path or login event helps us recognise an account session and investigate unusual access. The same approach applies when you move from phone login to the lobby.

Use the privacy contact path displayed inside your account and describe the records you need. We may verify your phone-linked account first, then assess the request where local law permits.

Yes, you can request correction of inaccurate account details or ask us to explain a record. Include the relevant account step, such as phone verification or a QRIS status entry.

Cookies can retain a session path, security preference or browser choice. You can change permissions in your browser, but the next visit may require fresh login or repeat account verification.

Describe the login or verification step that prevents access through the available support route. Do not send a password or code; we will use an account check before discussing personal data.