Reference

Open mei303 Privacy Policy Before Account Access

The mei303 Privacy Policy explains what we collect when you create an account, verify your phone, use the mobile lobby, or choose DANA, OVO, GoPay and QRIS.

Account data explainedWallet records outlinedCookie choices coveredAccess requests available
mei303 Open mei303 Privacy Policy Before Account Access
PRIVACY HELP

Contact Us About Your Privacy Policy

A clear contact route matters when a privacy question affects your account or wallet record.

Privacy request Use the privacy contact path shown around account help when you want to ask…
Wallet record check For a DANA, OVO, GoPay or QRIS question, send the payment reference and approximate…
Access assistance If a privacy request is blocked by a forgotten login or a changed phone…
DATA PRACTICE

Secure Your Account Data On Mobile

We apply the Privacy Policy to the same account whether you open the lobby on a phone, tablet or desktop.

Account details

We collect the details you submit during account creation and the phone verification result used before account access. We use them to identify your account, respond to a privacy request and protect the login path. Keep your credentials private; our support route will not ask for a wallet password.

Cookies and devices

Cookies and device signals can record session preferences, security events and browser behaviour connected with a login. You can manage cookies through your browser settings, although disabling some may affect account access or require another verification step when you return.

Payment references

A DANA, OVO, GoPay or QRIS transaction can create a reference, amount status and time record linked to your account. Bank transfer and virtual account records follow the same purpose: matching a payment and checking its status, not reading unrelated wallet activity.

Security checks

We review login events, phone verification and unusual device changes to reduce the chance of account access by someone else. If a check pauses your session, use the account help route and provide only the requested verification details so we can examine the event.

Retention period

We retain account, security and payment-reference records only for the period needed for the purposes described in this Privacy Policy, including dispute handling and legal requests. When a record is no longer needed, our process is to remove it or keep it in a form that no longer identifies you.

Changes and requests

You can ask us to explain, correct or update personal details through the privacy contact path. Tell us which account field is affected and include the requested verification information. We may keep a request record so we can show how the change was assessed and completed.

Find Privacy Policy Answers Before Joining

These Privacy Policy answers address the searches we hear most often before account creation. They cover mei303 account data, Indonesian wallet references, cookies, mobile access, corrections and the route for asking us to explain a record. If your situation is not listed, use the privacy contact path with the smallest useful set of details.

It covers account details, phone verification, login and device events, cookies, payment references and requests to access or correct personal data. It also explains how we use those records for account protection, payment matching, support responses and applicable legal needs.

Our Privacy Policy describes payment references and status records, not unrelated wallet credentials. When you use DANA, OVO, GoPay or QRIS, we need enough transaction detail to match the payment to your account. Never send a wallet password through support.

Phone verification helps us confirm that the person requesting account access or a privacy change is connected with the account. The result can be recorded for security and support handling. If verification fails, use the account help route rather than sharing extra personal data.

Yes. Use the privacy contact path and state whether you want an explanation, a copy where available, or a correction. Identify the affected account field and complete the verification step we request. We assess the request under applicable law and this Privacy Policy.

Cookies can keep a session, remember selected settings and help us examine security events on a mobile browser. You can change cookie controls in your browser. If key cookies are blocked, login may require another check or some account functions may not work as expected.

We keep records for the period needed for the purposes stated in this Privacy Policy, such as account security, payment-status checks, dispute handling and legal requests. The period can differ by record type. When retention is no longer needed, we remove or de-identify the record.

Start with the privacy contact route linked to account help and mention that your request concerns the Privacy Policy. Include your account identifier and relevant payment reference only when necessary. Account access and eligibility depend on local law, including where local law permits access.