Reference

Open mcmtoto Privacy Policy clearly

mcmtoto Privacy Policy explains what we collect when you open an account, use a mobile browser, check wallet status or contact support.

Account dataWallet recordsCookie choicesAccess requests
mcmtoto Open mcmtoto Privacy Policy clearly
HELP PATH

Check your privacy support route

A clear contact path helps when your Privacy Policy question concerns a phone number, wallet receipt or account record.

Account data request Ask us to locate the personal details connected with your account. Include your account identifier and phone verification context so we can match the request safely before discussing records or making a correction.
Wallet record question For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, send the payment reference and visible status. We use those details to separate a receipt query from unrelated account activity.
Access and correction If a cookie choice, phone detail or account record appears inaccurate, tell us what should change. We may ask for an account step that confirms you control the request before updating our records.
CONTROL DETAILS

Explore how account data stays controlled

We handle Privacy Policy requests as account matters, not as general lobby questions. Account details, device signals, cookie events and payment references are used only for the stated account, access, support and…

Account details

We may collect your name, phone number, verification responses and sign-in events when you open or use an account. These fields help connect a request to the correct account before we disclose or change personal data.

Cookies and devices

Cookies can keep a mobile-browser session active, remember a language or device preference and help us identify unusual access. You can clear browser cookies, though doing so may require another sign-in before account records appear.

Payment references

A DANA, OVO, GoPay or QRIS reference, as well as bank-transfer and virtual-account details, can appear in account records. We use the reference to match a receipt or status question without requesting your wallet password.

Account protection

Phone verification is part of account access, and support may ask for matching account details before discussing personal records. Keep your sign-in information private and avoid sending passwords or full payment credentials in a request.

Record retention

We keep personal and transaction records only while they serve account access, support, security or legal needs. When a retention need ends, records are removed, anonymised or kept only where a valid requirement still applies.

Your requests

You can ask for a copy of personal data, correction of an inaccurate field, clarification about cookies or deletion where applicable. Use the support route with your account identifier so we can verify the request before responding.

Ask about mcmtoto Privacy Policy

These Privacy Policy answers cover the searches we hear most often before an account is opened. They explain the records connected with sign-in, local wallet activity, mobile browsing and support requests, while keeping access wording subject to local law. If your situation is different, send the account identifier and the specific record you want us to check.

It covers account details, phone verification, sign-in activity, cookies, device signals, support messages and payment references. That includes records connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity when those details are linked to your account.

We use your phone number as part of the account path and phone verification before access. It also helps us match a Privacy Policy request to the right account. We do not need your wallet password to locate a DANA or QRIS receipt question.

Cookies can maintain a sign-in session, remember a device preference and help identify unusual access. You can clear them through your browser settings. After clearing cookies, you may need to complete the account sign-in and phone verification steps again.

Yes. Send a request through the account support route with your account identifier and the records you want us to locate. We may confirm control of the account first, then explain the available copy, correction or access process.

You can ask us to correct an inaccurate phone, profile or payment reference. You may also ask about deletion where applicable. Some records may need to remain for account security, transaction checking or a requirement that depends on local law.

Yes, the policy describes how we handle account activity from Indonesia, including wallet references and mobile-browser sessions. Access and eligibility depends on local law. If you are unsure whether access applies to your location, contact support before sharing sensitive account details.

Use the account support path and state whether your request concerns data access, a cookie, a correction, deletion or a wallet record. Add your account identifier and transaction reference when relevant, but never include a password or full wallet credential.