Reference

mee303 Privacy Policy: Know Your Account Data

Our Privacy Policy shows how mee303 handles the details you provide when opening an account, confirming your phone, checking DANA or QRIS status, and entering the lobby.

Clear data purposesWallet reference handlingAccount request pathCookie choices
mee303 mee303 Privacy Policy: Know Your Account Data
CONTACT ROUTES

Get Privacy Help Beside Your Account

A clear contact route helps you ask about the Privacy Policy without sending sensitive details through an unverified channel.

Account privacy request Use the support route inside your account to ask for a copy, correction or explanation of personal details connected with your phone verification and account access.
Wallet reference check For DANA, OVO, GoPay or QRIS questions, include the payment date and reference shown in your receipt. We use those details to check status without requesting your wallet password.
Security concern If Secure Account Access shows an unfamiliar device or session, contact us through the account support path and change your password before sharing any further account detail.
HANDLING DETAILS

How mee303 Applies This Privacy Policy

Our handling process follows the point at which a detail enters the account journey. Phone verification confirms that an access request belongs to the account holder, device signals help us spot unusual…

Account details

We use the phone number, email and verification result you submit to create an account path and respond to account requests. Keep these details current so a privacy response reaches the correct account holder.

Device signals

A phone or computer may send browser, session and device signals when you sign in. We compare these signals with account activity to identify unusual access, including activity connected with Secure Account Access.

Cookies

Cookies can remember sign-in state, security preferences and selected page settings. You can manage cookie controls in your browser, although refusing required cookies may interrupt account access or a privacy request.

Payment references

DANA, OVO, GoPay and QRIS records may provide a reference, amount status and time needed to match a receipt. We do not need your wallet password to investigate a payment status question.

Retention process

We keep account, support and security records only while they serve an operational, protection or legal purpose. When a record is no longer needed, our process removes it or separates it from direct account identifiers.

Your request

You may ask what account details we hold, request a correction or ask whether removal is available. Send the request through your account support path, and we may verify ownership before making a change.

Privacy Policy Answers For Indonesia

These Privacy Policy answers address the questions we hear most often before an account is opened or a wallet receipt is checked. They cover the data used for access, cookies, payment references, device activity, correction requests and local availability. If your situation is not covered, use the support route inside your account so we can assess the request against the relevant record.

It covers details connected with account creation, phone verification, sign-in sessions, device signals, cookies, support messages and payment references. It also explains why we use those details, how long they may be retained and how you can request access, correction or eligible removal.

Yes. The Privacy Policy covers the reference, status and timing details needed to match a DANA or QRIS receipt with your account. We do not ask for your wallet password, and a support request should include only the receipt details needed for that check.

Phone verification helps connect an access request to the correct account and gives support a reliable way to assess a privacy request. We record the verification result and related account details for access security, rather than treating verification as permission to collect unrelated personal data.

You can request details associated with your account through the support route shown after sign-in. Include your linked phone or email, and we may complete an ownership check before responding. The response can cover account records, device signals, payment references and support messages held for stated purposes.

Send a correction request through the account support path and identify the field that appears wrong, such as a phone number or email. We may ask for an ownership check before changing it, then use the corrected detail for future access and support handling.

On a mobile browser, cookies may keep a security state or page preference between sign-in steps. You can adjust them in browser settings, but required cookies may be needed for account access. The same approach applies when you move from a phone to a computer.

Yes, access depends on local law. The Privacy Policy explains our handling of account and device details for supported access, but it does not change local eligibility rules. If you need a location-specific answer, contact us through the account support route with your Indonesia account details.