Reference

Open the pgbet Privacy Policy

Our Privacy Policy explains what data we collect when you create an account, sign in from a mobile device, or use DANA and QRIS for a wallet step.

Account dataWallet recordsCookie choicesPrivacy requests

Browse Our Lobby Read FAQ

Browse what our Privacy Policy covers

pgbet Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our Privacy Policy applies to the details you provide during account creation, including contact data used for phone verification before account access. We record operational events such as sign-in time, device type, security checks and requests linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual

1
account activity. Payment records help us match a wallet or bank status to the correct account without treating a payment number as public profile data. Cookies can remember session settings and help us identify unusual access patterns. We use data for account operation, fraud prevention, support
2
handling and legal duties where local law permits. If you browse from a phone in Bandung, the same policy applies to the mobile page and its session cookies. The policy does not change the fact that eligibility depends on local law. Read each section before opening
3
an account, and contact us through the routes below if a term is unclear.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT ROUTES

Open a privacy request through support

A clear support route matters when your account data needs attention. We ask you to use the account support path for identity checks, wallet status questions and requests connected with the Privacy Policy. Include the email or phone detail attached to your account, but never send a wallet PIN or password in a message. Our team can then locate the relevant record and explain the next step.

Team online

Account data route

Use the support path attached to your account when you want to ask what contact data is held for your pgbet profile or why a phone verification record appears.

Wallet record route

For DANA, OVO, GoPay or QRIS status records, share the transaction reference and account identifier through support; keep passwords, PINs and full authentication codes private.

Privacy request route

Ask support to correct, access or remove eligible personal data under the Privacy Policy. We may request account verification before discussing records or applying a change.

DATA PRACTICE

Explore how pgbet handles your data

We keep the Privacy Policy practical by connecting each data use to an account task.

Account creation

When you open an account, we use the details you submit to create your profile and complete phone verification.

Device sessions

A mobile sign-in may create session and device records, including technical details used to protect account access.

Cookie controls

Cookies can keep your selected page state and help identify suspicious session changes.

Payment matching

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references may be checked against your account record so we can…

Retention approach

We retain account, support and transaction records for operational or legal needs, then remove or restrict them when the applicable…

Change requests

Contact support from your account to request a correction, copy or eligible deletion of personal data.

Find answers about Privacy Policy access

These answers address the Privacy Policy questions you may have before opening an account or checking a wallet record. We keep the process tied to real account steps, mobile sessions and payment references, while eligibility and any legal request remain dependent on local law.

You can read the Privacy Policy on this page before opening an account. It covers account creation, phone verification, mobile sessions, cookies, payment references and requests about personal data.

It covers details you submit for your account, contact and phone verification records, device and session signals, cookie data, support messages and payment references linked to DANA, OVO, GoPay or QRIS.

Phone verification helps connect account access with the contact detail you provided and supports security checks. We use that record for account operation and handle it according to the Privacy Policy.

Yes. The Privacy Policy applies when you sign in from a phone, including session cookies and technical device signals. Clearing browser data may end a session and require you to verify access again.

We may use DANA or QRIS references to match a wallet event with your account and investigate its status. The Privacy Policy does not ask you to send a PIN or password to support.

Yes, contact support through the account route and state whether you want access or a correction. We verify account ownership first, then assess the request where local law permits.

We keep records while they serve account operation, security, support or legal needs. The Privacy Policy explains the retention approach, and support can address a specific record request after verification.

Open the pgbet Privacy Policy

Open a privacy request through support

Account data route

Wallet record route

Privacy request route

Explore how pgbet handles your data

Account creation

Device sessions

Cookie controls

Payment matching

Retention approach

Change requests

Find answers about Privacy Policy access

01 Where can I read the pgbet Privacy Policy?

02 What personal data does the Privacy Policy cover?

03 Why does pgbet need phone verification data?

04 Does the Privacy Policy cover mobile browsing?

05 How are DANA and QRIS records handled?

06 Can I request a copy or correction of my data?

07 How long does pgbet keep account and support records?

Related Pages