Reference

Privacy Policy For Your pro33 Account

pro33 explains how we handle your account details, device signals, cookies and wallet records before you open the lobby.

Account dataWallet recordsCookie choicesPolicy requests
pro33 Privacy Policy For Your pro33 Account
DIRECT POLICY HELP

Get Clear Answers About Privacy

A privacy question should not leave you guessing about the next step. We keep the policy link close to the account and cashier areas, so you can identify the relevant record before asking us to check it. Include your account phone number only through the secure account route, and do not send wallet passwords or one-time codes in a message. Our support process can help with access, correction, deletion requests and questions about a DANA, OVO, GoPay or QRIS reference.

Team online

Account support panel

Use the support panel after signing in when you need to ask about account data, phone verification or a device record. We can locate the right account from the details you submit through the secure path, while you keep passwords and one-time codes private.

Cashier status path

If a wallet record looks unfamiliar, open the cashier history and note the date, amount reference and method shown there. DANA, OVO, GoPay and QRIS entries can then be connected to a privacy query without asking you to share your wallet PIN.

Policy change request

For a correction, access request or deletion question, select the policy contact route from your account menu. Tell us which record you mean and why it is inaccurate; we may request account verification before changing or disclosing personal data.

DATA CONTROL POINTS

How We Handle Your Privacy

Privacy protection works through specific account steps rather than broad promises. We separate sign-in checks from wallet references, use session controls on mobile and desktop, and keep policy requests tied to the…

Account data use

We use your phone number and account details to create the requested account, complete phone verification and protect sign-in activity. The account menu is the practical place to check the policy connected with these details before you enter the lobby.

Payment references

A DANA, OVO, GoPay or QRIS transaction reference helps us match a cashier event with your account and investigate a status question. We do not need your wallet PIN or password for that check, so keep those credentials outside every support request.

Cookies and sessions

Cookies can keep your account session active, remember selected privacy choices and support the path from login to the lobby. On a shared device, sign out after use and clear site data through the browser privacy settings when you do not want the session retained.

Device security

We may use device and login signals to identify unusual account access, such as a changed browser or repeated verification attempt. If your phone is lost, change the account credential through the account route and contact support without sending a one-time code.

Record retention

We retain account, security and payment records only for the period needed for the stated service purpose, account protection and applicable legal duties. When a record is no longer required, our handling follows the retention process described in the current Privacy Policy.

Your privacy requests

You can ask us to access, correct or delete eligible personal data, or ask why a record is held. Start from the policy contact route, identify the account record clearly and complete reasonable verification so we do not disclose details to the wrong person.

Privacy Policy Answers Before Access

These Privacy Policy answers cover the searches we hear most often before account creation and wallet use. They explain the practical route for checking data, cookies, device activity, payment references and account requests. Read them alongside the full policy text, especially if your access depends on local law or you are using a shared phone in Indonesia.

The Privacy Policy covers account details, phone verification, login and device signals, cookies, support messages and payment references. It explains why we use each category, how long records may be kept and how you can ask about access, correction or deletion through the account policy route.

We use your phone number to create and protect the account and to complete the phone verification step before account access. The number also helps us connect a privacy request with the correct account. Do not place a one-time code in a support message.

Yes. The Privacy Policy covers references created when you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. These references help us match a cashier event and resolve a status question, but your wallet PIN and password should remain private.

Open your account menu, choose the policy contact route and specify whether you want access to a record or a correction. Identify the relevant account detail clearly. We may ask for reasonable verification before providing data or changing it.

You can submit a deletion request through the policy contact route in your account menu. We assess which records can be removed and which must remain for account security, payment checks or legal duties. Our response will explain the result for the records you identify.

Cookies can support your signed-in session and remember selected privacy choices on the browser you use. You can manage or clear them through your browser settings. Clearing cookies may require you to sign in again and repeat the phone verification path.

Yes. Access and eligibility depend on local law and are available where local law permits. The Privacy Policy still explains our handling of account, device and wallet records for an eligible account. Check the policy link before submitting personal details or opening the lobby.