Reference

Privacy Policy For Your mp3tt Account

mp3tt Privacy Policy gives you a clear view of how we handle phone verification, device details and payment references when you open an account.

Clear data purposesPayment record controlsAccount access choicesSupport request path
mp3tt Privacy Policy For Your mp3tt Account
HELP WITH RECORDS

Get Privacy Policy Support From Your Account

A privacy question should not leave you searching through unrelated pages. We provide a direct support path from the account area, with a second route beside the cashier when your question concerns DANA, OVO, GoPay, QRIS or a receipt. Include your account phone number and the relevant reference, but never send a password or full payment credential. We use the details you provide only to identify the request and respond through the available account support route.

Team online

Account request

Use the support link inside your signed-in account to ask about stored records, correction requests or Privacy Policy access. Include the phone number attached to your account so we can locate the right record without asking for your password.

Payment receipt

For a DANA, OVO, GoPay or QRIS question, open the cashier support path and attach the receipt reference, date and status. We can check the payment record while keeping your wallet PIN, password and full credential out of the request.

Login concern

If an unfamiliar device appears after phone verification, contact us through the account help route before sharing anything else. Tell us the device type, approximate sign-in time and affected account number so we can review the security event.

DATA HANDLING

How mp3tt Applies This Privacy Policy

We apply this Privacy Policy through practical account and payment controls rather than broad promises.

Account details

We collect details needed to create and maintain your account, such as your phone number, verification result and sign-in events. We do not need your password in a support request, and you can ask which account details are held.

Payment matching

DANA, OVO, GoPay and QRIS references help us match a cashier event to your account. Bank transfer and virtual account checks use the same principle: status, time and reference data are reviewed without requesting your wallet PIN.

Cookies

Necessary cookies can keep a signed-in session, remember selected language or preserve a short-lived security token. Browser controls let you clear or block them, but clearing required cookies may send you back through phone verification.

Device security

We may record device type, browser details, IP address and failed sign-in events to identify suspicious patterns. If you switch from mobile to desktop, these records help us distinguish a normal device change from an access attempt.

Retention period

We keep account, payment and security records only for the period needed for the stated purpose, account administration or a legal request. When a record is no longer needed, we delete it or separate it from direct account identifiers.

Your requests

You can ask us to explain, correct, restrict or delete eligible personal records through the account support route. We may request account verification first, so a change is applied to the correct person rather than to an unrelated account.

Privacy Policy Questions About mp3tt

The answers below address the questions we expect you to ask before opening an account or sending a privacy request. Each answer stays focused on the records, controls and contact steps described in our Privacy Policy. If your situation is unusual, use the account support route with only the details needed to locate your record.

The mp3tt Privacy Policy covers account details, phone verification, device and sign-in events, cookies, payment references, support requests and retention. It also explains how you can ask us to access, correct, restrict or delete eligible records where local law permits.

Yes. Our Privacy Policy covers DANA and QRIS references, including payment status, time and the account connection needed for reconciliation. OVO, GoPay, bank transfer and virtual account records are handled for the same account and payment-checking purposes.

We collect device type, browser details, IP address and failed sign-in events to protect account access and investigate unusual activity. These records can also explain why a mobile-to-desktop change prompts another phone verification step.

Use the support link inside your signed-in account and ask for a copy or explanation of your records. Include your account phone number, but do not send a password, wallet PIN or full payment credential. We may verify your identity first.

You can request correction, restriction or deletion of eligible records through the account support route. We assess the request against account, payment and legal needs. Some records may remain for a required period, and access depends on local law.

Necessary cookies help maintain a signed-in session, remember language settings and support security checks. You can clear or block cookies through your browser. If required cookies are blocked, you may need to repeat login or phone verification.

Contact us through the account help route as soon as you notice an unfamiliar sign-in or device. Share the affected account phone number, device type and approximate time, while keeping your password and wallet credentials private.