Reference

Privacy Policy for Your Account Path

Your pgbet slot Privacy Policy explains what we collect when you open an account, sign in from a phone, or check DANA, OVO, GoPay and QRIS status.

Account dataWallet recordsDevice choicesCookie controls
pgbet slot Privacy Policy for Your Account Path
CONTACT PATHS

Privacy Help Beside Your Account

A clear contact route matters when a privacy question appears beside a login or wallet issue.

Account data request Use the signed-in support route to ask which account details we hold.
Wallet record question If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, share only the transaction…
Access concern For a sign-in alert or an account detail you did not change, contact us…
HANDLING DETAILS

Six Practical Privacy Controls

We keep this policy practical by linking each privacy choice to an account action you can recognise.

Account identifiers

We handle details such as your registered phone number, email address and account reference so we can complete sign-in checks…

Phone verification

Before account access, a phone verification step may connect your sign-in with the account record.

Device signals

When you move from a mobile login to a desktop session, we may record browser, device and session signals.

Cookie choices

Cookies can keep a session active, remember a selected setting and support account navigation.

Wallet references

A payment reference can show that a DANA, OVO, GoPay, QRIS, bank transfer or virtual account event relates to your…

Retention requests

We retain records only for the stated account, security, support or legal purpose, subject to applicable requirements.

Privacy Policy Questions From Indonesia

These Privacy Policy answers focus on the account actions you are most likely to take before opening or using pgbet slot. They cover the data connected with local wallets, mobile access, verification and contact requests, so you can choose the next step without guessing which record or channel matters.

It covers account details, phone verification, device and browser signals, cookies, support records and payment references linked with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains retention, permitted disclosures and how you can request access or changes.

Wallet and payment references can be connected with your account when you check a deposit or receipt status. The Privacy Policy explains how we use those references to investigate an account question, while your wallet password, PIN and private security code should remain outside our support messages.

We use account matching, phone verification and device-session records to review access concerns. If a sign-in looks unfamiliar, contact us through the signed-in account route and provide the registered phone or email. We will use the details needed to investigate rather than asking for unrelated private data.

Yes, you can request a correction through the account support path shown after sign-in. Tell us which detail is inaccurate and include the registered account contact so we can verify the request. Where local law permits, we will explain the next step for eligible changes.

Retention depends on why the record exists, such as account access, security checks, wallet status or support history, and on applicable legal requirements. The Privacy Policy does not treat every record alike. You can ask support to explain the purpose and retention position for a specific item.

You can change cookie permissions in your mobile browser settings. Necessary session cookies may still be required for sign-in, account navigation and privacy requests, while preference cookies can often be limited. If a page behaves differently after a change, contact support from the account route.

Yes. Account access and eligibility depend on local law, including for Indonesian access from Bandung, Medan or another location. Our Privacy Policy explains data handling when you reach an account page, but it does not override local requirements or determine whether access is permitted.