Reference

Privacy Policy For Your pro3bet Account

Our Privacy Policy explains how pro3bet handles the details you provide when opening an account, signing in, checking DANA or QRIS status, and contacting support.

Clear data purposesCookie choicesAccount access requestsIndonesia account context
pro3bet Privacy Policy For Your pro3bet Account
HELP WITH PRIVACY

Three Ways To Ask About Your Data

A direct support route helps you resolve privacy questions without guessing which account screen to use.

Account privacy chat Use our support chat for questions about the Privacy Policy, stored account details, phone…
Payment record check When DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity appears in your…
Change request path Ask support to open a privacy request when you need a correction, access copy…
DATA HANDLING

How pro3bet Applies This Policy

Privacy work follows the same account steps you already recognise: registration, phone verification, sign-in, wallet status checks and support contact.

Account details

We may handle your registration details, phone verification result, sign-in history and support messages so we can provide account access…

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference can help us match a cashier event to your…

Cookies

Cookies can retain selected settings, recognise an active session and help us understand whether privacy pages load correctly.

Security signals

Phone verification, sign-in time, browser details and device signals help us detect account access that does not match your usual…

Data retention

We retain account, payment-reference and support records only for the operational, security or legal period that applies to them.

Privacy requests

You can ask for access, correction, deletion where available, or an explanation of how a record is used.

Privacy Policy Answers For Indonesian Accounts

The questions below address the privacy points that matter when you open an account from Indonesia, move between a phone and desktop, or ask about a wallet record. Each answer stays tied to our Privacy Policy and the account path used to verify ownership. If your situation is not listed, contact support with the smallest useful detail rather than sending a password or wallet PIN.

It covers account registration details, phone verification, sign-in and device records, cookies, support messages, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains retention, security measures and how to request access or correction.

Phone verification helps us confirm that the person requesting account access or a privacy change controls the registered account. We record the result and related security event, not your phone password. If verification fails, use support rather than sending your one-time code in a message.

Yes. Send an access request through the support chat with your account identifier and a clear description of the records you want checked, such as sign-in history or payment references. We may verify ownership first, then explain the available response under local law.

We may use a DANA or QRIS reference, amount, date and status to match a cashier event with your account and resolve a receipt question. These details support account and payment checks; we do not ask you to disclose your wallet PIN or full credentials.

Cookies can keep a session active, remember selected settings and show whether the Privacy Policy page works correctly on your mobile browser. You can control them through browser settings. If you disable required cookies, signing in or restoring account preferences may require extra steps.

Contact support through the account privacy chat and identify the incorrect field, such as a contact detail or phone verification record. We may ask for an ownership check before changing it. Do not include your password, wallet PIN or complete payment credentials in the request.

You can ask about deletion through support, and we will assess the specific record and applicable retention requirement. Some account, security, payment-reference or support records may need to remain for operational or legal reasons. Your access depends on local law and the record category involved.