Reference

Privacy Policy For Your mc88i Account

Our Privacy Policy shows how we collect, use and protect the account details needed for mc88i access, including phone verification before you enter the lobby.

Account dataWallet recordsCookie choicesDevice security
mc88i Privacy Policy For Your mc88i Account
CONTACT PATHS

Get Privacy Help From Your Account

A clear contact path matters when you need a copy of your data, a correction or an explanation of a wallet record.

Account request Use the support route inside your account to ask for access, correction or removal of personal data. Include your registered phone detail and request type so we can match the request to the correct account record.
Wallet receipt For a DANA, OVO, GoPay or QRIS privacy query, attach the payment reference rather than wallet credentials. We use the receipt detail to check the linked record while keeping your password and security code private.
Sign-in concern Tell us when an unfamiliar device or login appeared and which account step was affected. We can check the access record and explain the next verification step without requesting your full payment password.
DATA PRACTICE

Six Practical Privacy Commitments

We keep this policy practical by tying each data use to an account action you can recognise.

Phone verification

Before account access, we may use your verified phone detail to distinguish your request from an unapproved sign-in. Keep the number on your account current, and contact support if the verification step does not match your device.

Payment matching

DANA, OVO, GoPay and QRIS references help us connect a receipt to the correct account. We use the reference for status checks and support replies, not as a substitute for your wallet password or security code.

Cookie control

Our website may store cookies for sign-in continuity, security and selected page settings. Your browser controls can remove or restrict them, although changing cookie settings may require you to repeat an account step.

Device records

We may record device type, browser details and access time to help identify unusual activity. This supports account protection when you move from a mobile browser to desktop and report a sign-in you do not recognise.

Retention period

We keep personal data only while it serves the stated account, security, support or legal purpose. When a record is no longer needed, our handling process removes it or separates it from direct account identifiers.

Change requests

You can ask us to correct account data, explain its use or request deletion through your account support route. We first confirm that you control the account, then respond with the action taken or the reason a record remains.

Privacy Policy Questions About mc88i

These answers address the privacy questions that usually come before account access: what we collect, why wallet references appear, how device activity is handled and where to send a request. Read the full Privacy Policy beside these answers, then use the account contact route when you need a case-specific response. Access remains subject to local law.

It covers account details, phone verification, device and login records, cookies, support requests and payment references from DANA, OVO, GoPay or QRIS. It also explains why we use each category, how long records may remain and how you can request access or correction.

We use your phone detail to complete verification before account access and to distinguish an approved request from an unfamiliar sign-in. It also helps support locate the correct account. Do not send your password or wallet security code in a support message.

Yes. The Privacy Policy covers payment references connected with DANA, OVO, GoPay and QRIS, along with bank transfer or virtual account references. We use those records to match receipts and answer status questions without requesting your wallet credentials.

Sign in to your account and use the support route to request access, correction or deletion. State the account detail concerned and include the registered phone or email. We verify control of the account first, then explain the action or any reason a record must remain.

We may record your device type, browser details, access time and related security signals when you use the mobile browser or desktop path. These records help us investigate an unfamiliar login and protect the account; they are handled for the purposes described in the Privacy Policy.

Cookies can keep sign-in continuity, security settings and selected page preferences on your browser. You can restrict or remove them through browser controls. After that change, you may need to repeat an account step, and the Privacy Policy explains the related use.

Use the signed-in account support route and describe the privacy request clearly. For a wallet-related matter, provide the receipt reference from DANA, OVO, GoPay or QRIS. We use the account detail to verify the request and keep the reply focused on your data.