Reference

Open zoom303 Privacy Policy Clearly

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

Account dataWallet recordsDevice choicesYour requests
zoom303 Open zoom303 Privacy Policy Clearly
CONTACT ROUTES

Browse Privacy Help Through Support

A clear contact route helps when you want to ask about a Privacy Policy request, an account record, or a wallet receipt. We keep privacy questions separate from a stalled cashier status so the right details reach the right team. Include your registered phone number, the subject of your request and any relevant reference, but do not send a wallet password or full payment credential. We will use the account path you provide to locate the request.

Team online

Account request

Use our account support path when you want to access, correct or remove personal details. We may ask you to complete phone verification before discussing an account record, so a request is linked to the right person rather than sent to an unrelated contact.

Wallet receipt

For a DANA, OVO, GoPay or QRIS receipt connected with your account, send the transaction reference and approximate date through support. We can compare that reference with the account record without asking you to reveal a wallet PIN or private login credential.

Privacy question

Ask about cookies, device data, retention or a correction through the same support route used for account help. State that your request concerns the Privacy Policy, and we will keep the conversation focused on personal data rather than general lobby assistance.

DATA CONTROLS

Switch Through Your Privacy Choices

We make this policy practical by linking each privacy choice to a familiar account action.

Account details

We may collect your name, phone number and verification result when you create or access an account. These details help us connect a request to your account path, and we describe the purpose in the Privacy Policy instead of treating every field as necessary by default.

Device signals

A phone or desktop session can provide browser, device and sign-in event details. We use these signals to understand access security and session continuity, including when you move from login to the lobby, without treating a device signal as your wallet password.

Cookie choices

Cookies can keep a session working and help us remember selected settings. Your browser controls whether cookies remain, while the policy explains their purpose and effect. Clearing them may require you to complete the phone verification step again on your next visit.

Payment references

DANA, OVO, GoPay, QRIS, virtual account and bank transfer records can include a reference, amount status and time. We use those fields to match a cashier event, while BCA, BRI, Mandiri or BNI details should be shared only when the payment step asks for them.

Retention requests

We retain records only for the purposes described in the Privacy Policy and for the period needed for an active account or a related account request. You can ask why a record remains, and we will explain the applicable account, payment or legal reason.

Corrections and access

You can request a copy, correction or clarification of personal details held on your account. Send the request through support with your registered phone number and subject; we may verify account ownership before changing a name, contact detail or payment reference.

Check Answers About Privacy Policy

These Privacy Policy answers address the searches we hear most often from people deciding whether to open an account. They cover the records created during phone verification, mobile access, cookies and local wallet activity. If your question concerns a specific receipt or account correction, include its reference when you contact support. Access depends on local law.

It covers account details, phone verification, sign-in and device events, cookies, payment references, retention and requests to access or correct data. It also explains how we handle records linked with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity.

We use your phone number to create and identify the account path and may verify it before account access or a privacy request. This helps us discuss personal records with the right account holder. The Privacy Policy explains the purpose connected with this detail.

Yes. The Privacy Policy covers browser, device and sign-in event details created when you use a phone or desktop. We use them for session continuity and account security checks. They do not replace your wallet PIN, payment password or other private credential.

We may receive transaction references, status and timing for DANA or QRIS activity connected with your account. These details help match a cashier event and receipt. We do not need your wallet PIN to check a reference, and the policy explains retention for such records.

Yes. Contact support and identify the request as a Privacy Policy matter, then provide your registered phone number and the detail you want checked. We may complete phone verification before releasing or changing a record, helping prevent an unrelated person from accessing it.

Cookies can preserve a session and selected settings between account steps. Your browser lets you clear or restrict them, but doing so may require another login or phone verification. The Privacy Policy explains each cookie purpose and the practical effect of changing browser settings.

We keep personal data for the period needed for the purpose described in the Privacy Policy, an active account request, payment tracing or another applicable obligation. You can ask why a record remains and request clarification through support, subject to account verification and local law.