Reference

mc888com Privacy Policy for Your Account

mc888com Privacy Policy explains how we handle the details you provide when opening an account, verifying your phone, entering the lobby and using DANA, OVO, GoPay or QRIS.

Clear data purposesWallet record contextCookie choicesPhone verification steps
mc888com mc888com Privacy Policy for Your Account
CONTACT ROUTES

Reach Us About Privacy Policy

A direct privacy question should not be mixed with a wallet status request. We separate account access concerns, payment-record questions and personal-data requests so your message reaches the right handling path.

Privacy request Use our account contact route to ask what personal data we hold, why it is used or whether an eligible correction can be made. Add your registered phone detail so we can locate the right account without requesting your password.
Wallet record check If a DANA, OVO, GoPay or QRIS reference appears incorrect, send the receipt detail through account support. We can compare the account record with the submitted payment reference while keeping your security code private.
Sign-in concern When phone verification or a device session looks unfamiliar, contact account support before changing repeated settings. We use the account step, device path and recent activity you provide to help protect access to your personal data.
DATA PRACTICES

How We Handle Account Privacy

Our Privacy Policy follows the same account path you use to enter the lobby: identify the account, confirm the requested action and limit the response to the relevant record.

Account details

We collect details you submit at account opening and during phone verification. These details help us connect your requests to one account, prevent mistaken disclosures and reply about the specific Privacy Policy issue you raise.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references may appear in our records when you use them. We use the reference to check status, not to request your wallet password or private security code.

Device activity

A phone, tablet or desktop can create different session details when you sign in. We use device and session signals to identify unusual access, investigate a locked account and keep your account path connected to the right request.

Cookies

Cookies can retain a selected setting or help us measure page activity connected with the policy and account path. You can manage cookie permissions through your browser, although refusing some cookies may change how the page remembers choices.

Retention

We retain personal data only while it supports account operations, security checks, dispute handling or a legal need. When a record no longer serves one of those purposes, we remove it or restrict its use under our retention process.

Policy changes

If this Privacy Policy changes, we place the revised wording on this page and update its policy context. Check the page before opening an account or sending a request, especially when your phone, device or wallet details have changed.

Privacy Policy Answers for Indonesia

These Privacy Policy answers address the account questions you are most likely to have before opening an account or contacting us. They explain the data connected with phone verification, wallet references, cookies, device sessions and requests for access or correction. If your situation is not covered, use the privacy contact route and describe the exact account step involved.

The mc888com Privacy Policy covers account details, phone verification, device sessions, cookies and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains retention, security handling and ways to request access, correction or eligible removal.

We use the phone verification result to connect account access with the correct account and reduce mistaken disclosures. It can also help us investigate an unfamiliar sign-in or locked session. We do not need your password or one-time code for a Privacy Policy request.

Yes. The Privacy Policy covers the payment reference, status detail and receipt information connected with DANA or QRIS, as well as OVO, GoPay, bank transfer and virtual account routes. We use those records to check an account request without asking for private wallet credentials.

Use the account contact route and state that you are making a Privacy Policy data request. Include your registered phone detail and the type of record you need, such as account or device data. Do not include your password, wallet PIN or one-time verification code.

Cookies may remember a setting and help connect page activity with your account path. You can manage them through your browser on a phone, tablet or desktop. If you refuse some cookies, the page may not retain selected choices between sessions.

You can ask us to correct inaccurate personal data or remove eligible records through the privacy contact route. We may need to confirm the account detail linked to your request, and some records can remain restricted when security, dispute handling or local law requires retention.

Yes. Account access and any data request depend on local law and apply where local law permits. We assess the request against the relevant account record, security needs and retention duties, then explain any restriction if the full request cannot be completed.