Reference

Open With Clear Privacy Choices

Your 3mtoto Privacy Policy explains what we collect when you create an account, sign in from a mobile browser, or connect DANA, OVO, GoPay or QRIS.

Data use explainedWallet details coveredAccount requests accepted
3mtoto Open With Clear Privacy Choices
PRIVACY SUPPORT

Reach Us When Privacy Questions Arise

A clear contact path matters when a privacy request affects your account or wallet status. We ask you to send enough account detail for us to locate the right record without placing sensitive credentials in a message. Our support route sits close to account and cashier help, so you can explain whether the issue concerns access, cookies, a payment reference or a correction request.

Team online

Account access

Use the account support route when you cannot reach your privacy settings or need help confirming which contact detail is attached to your account. We may ask for an account identifier before discussing records, but we will not ask you to send a password.

Wallet reference

For a DANA, OVO, GoPay or QRIS privacy question, include the payment reference and approximate activity date rather than sharing a wallet password or security code. This helps us trace the relevant record while keeping unrelated account details outside the request.

Data request

Send correction, access or removal requests through our support contact and state the action you want us to take. We review the account details involved, may verify your identity, and reply through the contact method already associated with your account.

DATA HANDLING

Browse How 3mtoto Handles Data

Privacy is easier to understand when each account step has a defined reason. We separate login protection, payment matching, service measurement and support handling instead of treating every piece of information the…

Account details

When you open an account, we use the contact and verification details you provide to create access and protect sign-in activity. Review the details before submission, because accurate account information helps us match privacy requests to the correct record.

Payment references

A wallet or bank reference helps us identify a transaction without treating the payment rail as a full profile of you. DANA, OVO, GoPay, QRIS, bank transfer and virtual account entries are handled for matching, status checks and account protection.

Cookies and sessions

Cookies can keep a mobile-browser session working, remember selected settings and show us which account pages need improvement. You can manage cookies through your browser controls, although removing them may require another login before privacy settings appear.

Security checks

We use sign-in checks, account verification and activity signals to reduce unauthorised access. If you change device or request help with a wallet record, we may confirm account ownership before revealing or changing personal details.

Retention periods

We keep records only for as long as they support the stated account, security, payment or legal purpose, subject to applicable requirements. When a record no longer needs retention, we remove it, restrict it or separate it from direct account use.

Changes and contact

To request access, correction, deletion or an explanation of data use, contact support through the account route and describe the record involved. We may need identity checks, then we record the request and respond using your available account contact.

Ask About Privacy Policy Access

These Privacy Policy answers focus on the account questions you are most likely to ask before opening access or connecting a local wallet. If your situation is not covered, use the support path with the smallest useful set of account details, and we can identify the relevant privacy record.

The 3mtoto Privacy Policy covers account details, sign-in activity, device and browser data, cookies, payment references, support messages, retention and privacy requests. It also explains how we use information to protect access and check activity linked with DANA, OVO, GoPay or QRIS.

We need selected account details to create access, confirm ownership, protect sign-in activity and respond to a data request. We use the details for those stated purposes rather than asking for unrelated personal records, and we may verify you before changing account information.

Yes. The Privacy Policy includes payment references connected with DANA, OVO, GoPay and QRIS, as well as bank transfer and virtual account activity where used. We use these references to match account activity, check status and investigate a payment-related privacy question.

Use the account support route and ask for access to your personal data. Include your account identifier and the contact method linked to it, but do not send a password or security code. We may confirm ownership before preparing the relevant records.

You can request a correction through support by naming the detail that is wrong and supplying the accurate replacement. This may include a contact detail or account reference. We check ownership first, then update eligible records and retain an audit record where required.

Cookies can keep your mobile-browser session active and remember privacy settings. You can adjust them through browser controls, but removing necessary cookies may sign you out or prevent a setting from being saved. The Privacy Policy explains their account and measurement purposes.

Where local law permits, you can ask us to remove eligible personal data through the support route. Some records may need to remain for account security, payment checking or legal duties. We explain the result after confirming the request and the records involved.