Privacy Policy for Your pompak Account
pompak keeps your account, casino, sportsbook and payment data in one privacy record so you can see what we collect before you open an account. This Privacy Policy...
How Our Privacy Policy Applies
Our Privacy Policy explains what we collect when you create a pompak account, enter the lobby, use wallet features, contact support or update your profile. We keep data tied to account safety, transaction checks, session security, device protection and service messages. Where local law permits, access may depend on your region, identity checks and the payment rails available to you in Pakistan.
We do not sell your personal data. We share limited records only with service providers who help us process payments, protect accounts, run support queues, detect misuse or meet lawful requests. Payment references from JazzCash, Easypaisa, SadaPay and Raast are stored with restricted access, so wallet activity can be checked if you raise a privacy or account query.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
How We Keep This Policy Accurate
We maintain this Privacy Policy as an operating record, not a generic legal page. Changes are checked against our account flow, payment logs, support handling and security controls before the wording is...
Account mapping
We link each policy clause to a real account action, such as login, profile edit, wallet check or support contact, so the wording reflects what pompak actually collects.
Payment checks
JazzCash, Easypaisa, SadaPay and Raast references are handled as transaction records. Our policy wording separates payment proof from broader account data to keep the explanation clear.
Security logs
We describe device, session and IP records because they help us protect access. These records are kept for account security and fraud checks, not public display.
Support training
Our support team uses the same privacy wording when answering account questions. That keeps replies consistent when you ask about data access, correction or account records.
Access controls
Personal data is limited to teams that need it for support, wallet checks, security or lawful handling. Internal access is logged so sensitive actions can be traced.
Policy dates
When we change this Privacy Policy, we update the page wording and keep the prior internal draft for comparison. That helps us explain what changed if you ask.
How Our Policy Pages Stay Aligned
This Privacy Policy sits beside our account terms, cookie wording, wallet rules and security messaging. We keep the pages aligned so a privacy request does not conflict with...
| Account terms | Our account terms explain your account duties, while this Privacy Policy explains the data used to run those duties. The two pages are checked together before edits go live. |
|---|---|
| Cookie wording | Cookie wording covers browser storage and similar tools. This Privacy Policy connects those tools to session safety, preference settings and analytics used to keep account access stable. |
| Wallet rules | Wallet rules cover payment flow, while this page explains the personal records behind that flow. Payment references are treated as privacy data when they identify your account. |
| Security messages | Security messages may ask you to verify access or reset credentials. This Privacy Policy explains why device signals and login history can be used during those checks. |
| Support scripts | Support replies must match this policy when handling data requests. We avoid asking for extra personal details unless they are needed to verify the account safely. |
| Promo board | If you check the promo board, we may record eligibility markers. This policy explains those records without mixing them with payment records or identity documents. |
| Regional access | Where local law permits, regional checks may apply. This Privacy Policy explains the data behind those checks, including location signals and account verification results. |
Policy Page Layout Cues
We designed this page so privacy choices are easy to scan before you join pompak. The layout separates collection, use, sharing, storage and contact paths, helping you find...