Reference

2mtoto Privacy Policy For Your Account

2mtoto Privacy Policy explains how we collect, use and protect the details connected with your account, including login records and wallet activity.

Account dataWallet recordsCookie choicesPolicy access
2mtoto 2mtoto Privacy Policy For Your Account
CONTACT YOUR WAY

Privacy Questions Through Your Account

A clear contact route matters when you want to ask about the Privacy Policy, correct an account detail or understand a wallet record.

Policy request Use the account support route to ask what personal data we hold, why it is used or how long a category is kept. We may ask you to complete the clear phone verification step before discussing account-linked records.
Data correction If your phone detail, email or account record is inaccurate, tell us through support after login. We compare the request with the account step and security checks before making a change, helping prevent another person from altering your details.
Wallet record For a payment record, send the reference and name the rail used, such as QRIS, DANA or bank transfer. We can then check the matching status without asking you to share a wallet PIN, card secret or login password.
DATA HANDLING

What Our Privacy Controls Cover

The Privacy Policy is supported by practical account controls rather than a general statement alone.

Account details

We may use your phone number and account credentials to create access, complete the clear phone verification step and protect sessions. The Privacy Policy explains which details are required for account security and which requests can be made after login.

Payment references

DANA, OVO, GoPay and QRIS can create reference, amount and status records linked to your account. Bank transfer and virtual account activity may carry a bank reference as well, allowing our support route to trace a reported mismatch.

Cookies

Cookies and similar device signals can keep your session connected and help us detect an unusual login path. You can manage browser cookie settings, though changing them may affect sign-in continuity or the way policy choices are saved.

Security checks

Before we disclose account-linked data or change a phone detail, we may compare your request with login and verification records. Never place a password, wallet PIN or full payment credential in a support message.

Retention

We keep records only for the period explained in the Privacy Policy or where a legal, security or account-resolution need requires continued storage. When a record no longer serves that purpose, our handling follows the stated retention process.

Change requests

To ask for correction, access or deletion of eligible data, use the support route from your account and describe the request clearly. We may need identity checks, and some records cannot be removed while a legal or security duty applies.

Privacy Policy Answers For 2mtoto Accounts

These Privacy Policy answers address the account and wallet questions you are most likely to have before opening access. They explain what we collect, how you can request a change and why a security check may be needed. If your question concerns a specific DANA, OVO, GoPay, QRIS, bank transfer or virtual account record, keep its reference ready when contacting support.

It covers account details, login and device security records, cookies, payment references, support requests, retention and your available data choices. It also explains how we use information to provide access, investigate account issues and meet duties that apply where local law permits.

We may collect your phone number, account credentials, verification details, login activity, device signals and support messages. When you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, we may receive transaction references and status details needed to match activity.

Yes, send an access request through the support route after login and identify the account detail connected with it. We may verify your phone before responding, and the Privacy Policy explains any records that cannot be disclosed because another legal or security duty applies.

Use account support to request a correction to your phone detail, email or other eligible record. Include the change clearly, but do not send your password or wallet PIN. We compare the request with phone verification and security records before applying an approved update.

We use the reference and status connected with DANA or QRIS to match a wallet action to your account and answer a payment query. We do not need your wallet PIN in a support message. The same approach can apply to OVO, GoPay and bank transfer records.

Cookies can maintain your signed-in session, while device and login signals help identify unusual access. These details support account security and policy choices rather than replacing your account verification. Browser settings can restrict cookies, but sign-in continuity may then change.

A request may be limited when disclosure would expose another person’s data, weaken account security, conflict with a legal retention duty or prevent an active account matter from being resolved. We explain the reason through support and apply the policy where local law permits.