Reference

m11toto Privacy Policy For Your Account

Our Privacy Policy explains what account, wallet and device details we collect, why we use them, and how you can ask about changes.

Account clarityWallet privacyDevice controlsLocal access
m11toto m11toto Privacy Policy For Your Account
HELP WITH PRIVACY

Get A Clear Answer About Your Data

We keep privacy questions close to the account and cashier paths, so you can ask about a record without repeating your full account history. Include the email or phone number linked to your account, the relevant transaction reference, and the specific Privacy Policy question. We will use those details to locate the request and avoid asking for unnecessary wallet credentials.

Team online

Account privacy request

Use the account support route to ask for a copy, correction or explanation of personal data. We may ask you to complete phone verification before discussing account-linked details.

Wallet record question

For DANA, OVO, GoPay or QRIS records, send the payment reference and status shown beside the cashier path. Never send a wallet PIN or one-time security code.

Policy contact route

If a Privacy Policy request concerns cookies, device access or retention, describe the issue through our contact path so the right account team can handle it.

CONTROL YOUR RECORD

What We Do With Account And Device Data

Privacy choices work best when you know which account step creates each record. We use phone verification to protect account access, payment references to trace wallet status, and device signals to detect…

Collected account details

We may hold your registration details, phone verification result and account activity needed to provide access. We use these records to match requests with the correct account rather than relying on an unverified message.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account request can create a reference record. We use it to reconcile the status shown in your account and investigate a receipt question.

Cookies and sessions

Necessary cookies can keep your session and selected settings available while you move from login to the lobby. You can clear browser data, though doing so may require another account verification step.

Device protection

We may assess device and sign-in signals when account activity appears unusual. This supports access checks without asking you to disclose a wallet password, PIN or one-time security code.

Retention choices

We retain personal data only while it supports the stated purpose, account records or a legal requirement. A request to remove data may be limited where a transaction record must still be kept.

Changes and contact

You can ask us to correct details, explain a data use or request an eligible deletion through support. Include your account contact and request scope so we can verify ownership before replying.

Privacy Policy Answers For m11toto Accounts

These Privacy Policy answers cover the searches we hear most often before account access. They explain wallet records, phone verification, cookies, device checks, retention and the route for asking us to change or remove eligible details.

It covers account details, phone verification, payment references, cookies, device signals, retention and contact requests. The policy explains why each category is used and how you can ask about your records.

Phone verification helps us confirm that an account request comes from the account holder. We may complete this check before discussing account-linked data, wallet status or a requested correction.

Yes. The Privacy Policy covers references connected with DANA, OVO, GoPay and QRIS, including status, time and amount. We do not need your wallet PIN to reconcile a payment record.

You can request a correction through the account support route. State which detail is wrong and provide the account contact used for verification; we may ask for an ownership check before changing it.

Necessary cookies can preserve a login session and selected settings as you move between account pages. Clearing them may sign you out or require another phone verification step on your next visit.

We keep records for the stated collection purpose, account administration or applicable legal needs. Retention can differ by record type, and we can explain the reason when you submit a specific request.

Use the support or contact path linked to your account and describe the Privacy Policy issue. Include your account contact and, for a wallet question, the payment reference; do not send PINs or security codes.