How We Handle Your Privacy
xe777 keeps casino, sportsbook and wallet privacy under one plain policy, so you know what we collect before you open an account. We explain account records, device checks...
Data Posture For Pakistan Accounts
This Privacy Policy explains how we collect, use, store and share data connected with your xe777 account in supported regions. When you join, we record details you provide, login signals from your device, wallet references from Pakistani payment rails, and messages you send to support. We use that data to create your account, protect access, confirm payment status, answer privacy requests, detect
misuse, and keep accurate records required for service operation. Where local law permits, we may share limited data with payment processors, security tools, game studios such as Pragmatic Play or Evolution when a session needs validation, and advisers who help us manage legal duties. We do not sell your personal data. Retention periods depend on the record type, fraud checks, accounting needs
and lawful request handling.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Contact Us About Privacy
Privacy requests need a secure route, so we keep each contact path tied to account matching rather than public comments. Use the channel that matches your question: email for access or deletion requests, chat for quick policy pointers, and wallet tickets when a payment reference is involved.
Privacy email
Send your privacy request to [email protected] from the email linked to your account. We match the request, confirm key details, and reply with the next action in clear English.
Secure chat
Use account chat when you need help understanding a policy clause. Our team can point you to the right section, but sensitive copies or deletion requests move to email.
Wallet reference ticket
If your privacy question involves JazzCash, Easypaisa, SadaPay or Raast, include the transaction reference. We use it only to trace account records and payment status.
How Policy Checks Stay Current
We treat the Privacy Policy as an operating document, not a static footer link. Each change is checked against the data we actually process: sign-in logs, wallet references, identity checks, support messages...
Change log discipline
Every policy edit is dated internally before it appears on this page. We check whether new wallet flows, device controls, or account forms change what data we collect from you.
Access control
No employee can read full wallet records without role access. Sensitive entries are masked in dashboards, while reference numbers remain visible for resolving JazzCash, Easypaisa, SadaPay or Raast queries.
Local payment mapping
When a local transfer clears, we store the payment reference, account match and status response. We do not need your wallet PIN, app password or private banking login.
Device security logs
We record device type, IP range, browser signals and login time to spot unusual account access. These logs help us protect your account without reading unrelated device content.
Studio session checks
For live tables or slot sessions, we may share a session token with the relevant studio. The token confirms access and round status, not your full account profile.
Request handling
Access, correction and deletion requests follow identity checks before action. We answer in plain Pakistani English and explain when a record must be kept for legal or security reasons.
One Privacy Standard Across Pages
Your privacy rights should not change depending on which xe777 page you read. We align this policy with account forms, cookie banners, wallet screens, support replies and security...
| Account creation | The account form collects only the fields needed to open and protect your account. This policy explains those fields before you send them, including contact details and password handling. |
|---|---|
| Login prompts | Security prompts may ask for extra confirmation when a new device appears. The same policy basis applies: protect your account, reduce misuse and keep a clear access record. |
| Cookie banner | Cookie choices are written to match this page, so tracking categories are not hidden behind vague labels. You can understand what is essential and what supports measurement. |
| Wallet screens | Wallet screens show payment names and reference fields that connect to this policy. We explain why those records exist, how they are matched, and why PINs are never requested. |
| Support replies | Support replies follow this policy when staff ask you to confirm identity. We ask for enough to locate your account, not extra private details unrelated to the request. |
| Security alerts | Security alerts refer back to the same device and access logging described here. If an alert is triggered, the privacy basis is account protection and misuse detection. |
| Policy archive | When we replace policy wording, we retain earlier versions for internal checks. This helps us answer what applied to your account at the time of a past request. |
Visible Privacy Cues On Page
We designed this policy page so you can scan the parts that matter before you share data. Headings, chips, contact cards and question blocks each point to a...