Reference

Open the free7m Privacy Policy

The free7m Privacy Policy explains what we collect when you open an account, sign in from a phone, or use DANA, OVO, GoPay and QRIS.

Account dataWallet recordsDevice controlsSupport requests
free7m Open the free7m Privacy Policy
CONTACT PATHS

Get privacy help beside your account

A clear support route matters when you need to ask about personal data rather than a lobby screen.

Account questions Ask us to explain the personal data connected with your account, including the phone…
Wallet records For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account query, send the…
Policy requests You can request a copy, correction or deletion assessment through the contact path shown…
HANDLING PRACTICES

See how we protect policy choices

We keep the Privacy Policy practical by describing the records behind familiar actions: opening an account, confirming a phone, checking wallet status and returning to the lobby from…

Account data

We use the details needed to create and maintain your account, including contact data supplied during the account path.

Payment matching

A payment reference lets us connect a DANA, OVO, GoPay or QRIS event with the correct account.

Device signals

When you sign in on a phone or desktop, we may record technical signals needed for session security and page…

Cookies

Cookies and similar storage can keep your session, language choice or policy acknowledgement available as you move between account pages.

Retention

We retain records for as long as needed for the stated service purpose, account security, payment reconciliation or a legal…

Security contact

If you suspect another person accessed your account, contact us through the support path and change your password from the…

Find answers about Privacy Policy

These Privacy Policy answers cover the searches we hear before an account is opened or a wallet record is checked. They explain the account path, device data, cookies, payment references, retention and contact process in plain language. If your situation is unusual, use the privacy contact route and describe only the minimum detail needed to identify your request.

It covers account details, phone verification, device and session records, cookies, payment references, support messages, retention and requests about your data. It also explains why we use those records for account security, payment reconciliation and service support where local law permits.

We use the phone verification step to confirm that the person requesting account access matches the account record. It can also help support identify the correct account when you ask about a DANA, OVO, GoPay or QRIS payment status.

Yes. The Privacy Policy covers payment references and receipt details connected with DANA, OVO, GoPay and QRIS. For bank transfer or virtual account questions, we may also check the reference, date and account match needed to resolve the status.

We may record technical signals linked to a phone or desktop session, such as access events and security-related device details. We use them to keep sessions secure, investigate unusual sign-ins and deliver account pages, not to replace your account identity.

Use the privacy support contact shown on the site and state whether you want a copy, correction or deletion assessment. We may request account or phone verification details before responding, so personal data is not sent to the wrong person.

Retention depends on the purpose of each record, such as account security, payment reconciliation, support handling or a legal duty. When the relevant reason ends, we follow our deletion or anonymisation process where applicable and explain limits on a requested deletion.

Yes. You can read the current Privacy Policy before completing the account path and contact us about wording you do not understand. When data practices change, we present revised policy wording through the site so you can check it before continuing.