Reference

MT661 Privacy Policy for Your Account

Open your MT661 account with a clear view of how we handle phone verification, device access and wallet records.

Account data explainedWallet records coveredContact paths included
MT661 MT661 Privacy Policy for Your Account
CONTACT ROUTES

Ask Us About a Privacy Policy Request

A clear support path helps you ask what data is held, why a record appears, or how to request a correction. Start from the account support route and include the phone number or account reference linked to your MT661 access. We can then match the request safely, including when a DANA receipt or QRIS status needs context.

Team online

Account privacy request

Use the support route attached to your account and state whether you want access, correction or deletion. We may ask for account details before discussing personal records.

Wallet record question

For DANA, OVO, GoPay or QRIS questions, include the payment reference and date. We use those details to locate the relevant record without asking you to send a wallet password.

Access concern

If your phone verification or sign-in behaves unexpectedly, contact account support through the available route. We use the account and device context you provide to check the request.

HANDLING PRACTICES

See How MT661 Handles Your Data

We keep this Privacy Policy practical: you should know what enters an account record, how we use it, and where to ask for a change.

Account data

We may hold your phone number, verification result, account reference and sign-in history to maintain access and respond to account requests. We use these records for stated account purposes.

Device signals

When you move between a mobile browser and desktop, we may receive device and connection signals linked to that session. These help identify unusual access and protect your account.

Cookies

Cookies or similar browser tools may remember session choices and support account continuity. You can manage browser controls, although changing them may affect sign-in or policy-page access.

Account security

Phone verification and sign-in checks help us distinguish an account holder from an unauthorised attempt. Never send us a wallet password, full PIN or private security code.

Record retention

We retain account, payment-reference and support records only for as long as needed for the stated service, security, dispute and legal purposes. Retention can vary by record type.

Change requests

To request access, correction or removal, contact us through the account support route with your account reference. We may verify your identity before making a privacy change.

Find Answers About This Privacy Policy

These answers address the privacy questions you are most likely to have before opening an account. They cover payment records, mobile access, phone verification, cookies and requests to change personal data. If your situation is not listed, use the account support route and describe the record you want us to check.

It covers account details, phone verification, device signals, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

We use the verification result to support account access and identify unusual sign-in attempts. It also helps us match a privacy request to the correct account without exposing records.

Yes. The policy covers payment references and account-side status records connected with DANA, OVO, GoPay and QRIS. A provider may separately handle data under its own privacy terms.

A mobile browser or desktop session may create device and connection signals linked to your account activity. We use them for session continuity, security checks and investigating unusual access.

Contact us through the account support route, identify the account reference, and explain the record that needs correction. We may verify your identity before changing personal account data.

You can submit a deletion request through account support. We assess the request against active account, security, dispute and legal record needs before confirming what can be removed.

The policy is written for Indonesian access where local law permits. Eligibility and access depends on local law, so the terms applying to your location may affect how we handle a request.