Privacy Policy for your p2e account
The p2e Privacy Policy explains what account data we collect, why we use it, and how we protect it when you open your account in supported regions. Read...
How p2e handles your data
This Privacy Policy applies when you access p2e.onl, open an account, contact us, or use our casino, live casino, slots, and sportsbook areas where local law permits. We collect only the data needed to run your account flow, keep access secure, process wallet activity, answer privacy requests, and meet record-keeping duties. That may include your contact details, login activity, device signals, game-session
records, transaction references, and support messages. We do not sell your personal data. We share limited data with service partners only when they help us operate hosting, security, account checks, support tools, or Pakistani payment verification. We keep records for as long as needed for account, legal, security, and dispute purposes.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
How we keep policy accurate
We write this Privacy Policy from the operator side, using the same account, security, payment, and support flows that your data passes through. Updates are checked against current site behaviour, so the...
Operator wording
The policy is written in our voice because we control the account journey, wallet checks, live table access, slot records, sportsbook logs, and support tools described on this page.
Data mapping
We match policy wording to real data points, including login timestamps, device details, transaction references, game-session records, and messages you send through chat or account inbox.
Security input
Our security checks shape the policy language around access logs, account verification, unusual-session alerts, and steps used to prevent another person from viewing your private account data.
Payment context
JazzCash, Easypaisa, SadaPay, and Raast references are included only where they affect account records, verification trails, refund handling, or privacy duties around transaction support.
Support feedback
Questions received through chat and account inbox help us clarify privacy wording, especially around data access, correction requests, cookie choices, and identity checks before records are shared.
Change log
When the way we collect or use data changes, we update this policy and keep the wording close to the actual account flow rather than adding vague legal language.
Consistent across our policy pages
This Privacy Policy works alongside our other legal pages, but it has a separate job: explaining data use. We keep definitions, contact paths, and account terms aligned, while...
| Terms page | Our terms explain account rules, while this policy explains the data behind those rules. When both pages mention verification, the privacy section explains what records may be checked. |
|---|---|
| Cookie page | Cookie wording connects directly to this policy by naming browser storage, analytics signals, and preference choices. You can compare both pages to see how site behaviour is measured. |
| Security page | Security wording covers account protection steps, while this policy explains the data used for those steps, such as login records, device signals, and unusual-access checks. |
| Promotions terms | Promo pages may describe eligibility rules, but this policy explains how related account data is handled, including participation records, wallet references, and support queries about eligibility. |
| Payment wording | Payment pages describe transaction steps; this policy describes the privacy side of transaction records, including JazzCash, Easypaisa, SadaPay, and Raast reference handling. |
| Support wording | Support pages tell you how to reach us. This Privacy Policy explains how your support messages are stored, linked to your account, and protected during follow-up. |
| Update wording | All legal pages may change, but privacy updates matter when data collection, sharing, retention, or account-rights wording changes. We keep those changes visible on this page. |
Visible cues on this policy
We designed this privacy page so you can scan the parts that affect your account before you join p2e. Short labels, clear sections, and repeated contact...
Plain section labels
Each section uses direct labels such as data use, sharing, retention, and contact paths, so you can move through the policy without decoding legal phrasing first.
Account-first wording
Examples are tied to real p2e account moments, including login, verification, game sessions, wallet checks, and support messages, rather than abstract privacy language.
Choice markers
Where a setting can be changed, the policy points to the relevant account, browser, or support route so you know where privacy choices are handled.
Sharing limits
The layout separates data we use ourselves from data shared with service partners, making it easier to see why a partner may receive limited records.
Retention cues
Record-keeping wording is grouped by purpose, so account, security, legal, transaction, and dispute records are explained without mixing them into one unclear paragraph.
Contact reminders
Privacy contact paths appear near the sections where questions usually arise, helping you send account-correction, access, or deletion queries to the right channel.