Reference

pg11 Privacy Policy for Your Account

Our pg11 Privacy Policy explains how we handle the account details, device signals and payment references used when you open the casino lobby or check Live Football Odds.

Account clarityWallet data contextMobile access

Browse Our Lobby Read FAQ

Know How Wallet Data Is Used

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

This Privacy Policy describes the information we collect when you create an account, complete phone verification, sign in, browse Jungle Delight or use account services. We may handle contact details, login records, device information, security events and payment references needed to match a transaction with your

1
account. DANA, OVO, GoPay and QRIS can appear as context for a cashier event, but we do not treat a wallet label as permission to use unrelated data. We use information to provide account access, check unusual activity, respond to support requests and meet applicable legal
2
duties. Retention depends on the purpose and any required period. Access to pg11 and related services depends on local law. You can ask us to explain, correct or remove eligible information through our support route, subject to identity checks and legal limits.

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

HELP FOR DATA REQUESTS

Get Help With Privacy Requests

A clear support route helps when you want to ask about account information rather than a lobby title.

Account questions Use our site support route to ask what account details we hold, why a phone verification record appears, or which account step is needed before we can discuss your request.

Wallet references For DANA, OVO, GoPay or QRIS questions, include the relevant account event without sending a wallet password. We use the reference to locate the record and check its status.

Correction requests If your contact detail or account record needs correction, request a change through support. We verify account ownership first, then confirm whether the requested update can be made.

HOW WE HANDLE RECORDS

Keep Your Account Data Safer

Privacy depends on everyday account controls, not only on a page of legal wording. We separate sign-in checks from payment references, limit access to people handling the relevant request and use your…

Data handling

We use contact details, phone verification results, sign-in events and payment references for stated account purposes. We do not need unrelated personal details to show a lobby such as Aviator or Bingo.

Cookies and signals

Cookies and device signals can help remember a session, protect the login path and understand basic access errors. You can manage browser settings, though some account functions may then need another sign-in.

Account security

A clear phone verification step helps connect account access with you. Keep login details private, and contact support if a mobile browser shows an unfamiliar sign-in or wallet status.

Retention periods

We keep records only for the account, security, service or legal purpose that requires them, then remove or restrict them when the applicable retention period ends.

Requesting changes

Ask us to access, correct or remove eligible personal data through the site support route. We may check identity and explain any legal or security reason that limits a request.

Mobile account path

When you move from login to the lobby on a phone, technical records can help diagnose the route. This may include browser type, session time and security events, not private wallet credentials.

Answers About pg11 Privacy Policy

These Privacy Policy answers cover the questions we expect before you open an account or ask us to change a record. They explain the practical difference between account information, device activity and payment references, with the same access rule applying where local law permits.

It covers account details, phone verification, sign-in events, device signals, cookies, support messages and payment references connected with your use of pg11 services, including access to the Indonesian lobby.

No. The policy concerns transaction references and account events linked to DANA or QRIS activity. Do not send a wallet password to support; we use account checks to locate the relevant record.

Phone verification helps connect account access with the person opening the account and helps us investigate unusual sign-ins. The verification result may be retained for security and legal purposes.

Yes, you can ask through our site support route. We may confirm account ownership before releasing information, and the Privacy Policy explains when security or legal duties can limit the response.

Send a correction request through support and identify the affected account detail, such as a contact record. We check ownership first and confirm whether the requested change is permitted.

Retention varies by purpose. Security events, support records and payment references may need different periods, so we keep each category only as long as the account, legal or security reason requires.

Yes. The same Privacy Policy applies on a mobile browser, including the path from login to the lobby. Browser type, session details and security events may be used to protect account access.

pg11 Privacy Policy for Your Account

Get Help With Privacy Requests

Keep Your Account Data Safer

Data handling

Cookies and signals

Account security

Retention periods

Requesting changes

Mobile account path

Answers About pg11 Privacy Policy

01 What does the pg11 Privacy Policy cover?

02 Does the Privacy Policy store my DANA or QRIS password?

03 Why does pg11 need phone verification?

04 Can I request a copy of my personal data?

05 How do I correct information in my pg11 account?

06 How long does pg11 keep account information?

07 Does the Privacy Policy apply when I use a phone?

Related Pages