Privacy Policy for your x4u account
At x4u, this Privacy Policy tells you what account, device, game-session and Pakistan payment data we collect before you open an account or use the lobby. Read it...
How this Privacy Policy applies
This Privacy Policy applies when you access x4u.bet, open an account, contact us, use account tools, or request cash-out checks in supported regions. We collect only the data needed to create your profile, keep your login secure, process KYC checks, display your balance, record game and sportsbook activity, manage promo eligibility, and answer privacy questions. Pakistan payment references such as JazzCash, Easypaisa,
SadaPay and Raast are used as transaction context, not as permission for unrelated use. We may share limited data with payment processors, identity checks, fraud controls, hosting providers, analytics tools and customer-care systems when needed to run the service. We keep records for legal, tax, security and dispute purposes, then reduce or delete them when retention is no longer needed under applicable
rules.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Contact paths for privacy requests
If you want to ask about your data, change account details, or raise a privacy concern, contact us through the route that matches your request. We may ask for account verification before discussing records, because privacy support must protect the same data you are asking about.
Privacy email
Use the privacy email for access, correction, deletion and data-use questions. Include your registered phone or email, but do not send card images or full ID files until our team asks for them.
Live chat
Live chat can route urgent privacy concerns, login alerts and wrong-contact details to the right team. We confirm your account first, then move sensitive replies away from shared screens where needed.
Account team
The account team handles KYC record checks, name spelling fixes and payment-reference matching. If a JazzCash or Easypaisa record needs tracing, we use only the transaction details required for that case.
How we keep the policy current
We write this page from the operator side of x4u, so the wording matches how your account flow actually works. Policy text is checked against account registration, payment...
Operator wording
Our privacy wording is based on the account screens, login checks and support tools we operate. When a form changes...
Local payment mapping
JazzCash, Easypaisa, SadaPay and Raast references are mapped to payment status, verification and dispute handling. The policy separates those references...
Security alignment
Password resets, device checks and session logs are handled as security records. The policy explains why these records exist, who...
Retention checks
We group records by purpose, such as account, transaction, support, security and legal retention. Each group has a reason for...
Cookie clarity
Cookie wording is matched with the banners and settings you see on x4u.bet. We separate required cookies from measurement tools...
Support training
Support replies use the same privacy terms as this page, so you receive consistent answers. Staff are trained not to...
Consistency across x4u policy pages
This page sits beside our terms, cookie text and security notices, but it has its own purpose. Here we focus on personal data: what we collect, why we...
| Terms connection | The terms describe account rules, while this Privacy Policy explains the data used to apply those rules. Where both pages mention verification, this page explains the privacy purpose behind the check. |
|---|---|
| Cookie page link | Cookie text covers browser storage in more detail. This Privacy Policy explains why cookies support login, fraud checks, language settings and measurement, then points you toward the setting path shown on site. |
| Security notice match | Security notices may describe alerts, device locks or password reset steps. This policy connects those actions to personal data handling, including session logs, IP records and contact details used for warnings. |
| Payment record boundary | Payment pages may show how to use JazzCash, Easypaisa, SadaPay or Raast. This policy explains the privacy boundary: references are used for processing, checks, disputes and record retention. |
| Support script match | When support asks account questions, the script should match this policy. We use verification to avoid exposing your records to another person, especially during email, phone or chat follow-ups. |
| Promo data separation | Promo pages may show account offers, while this policy explains the data logic behind eligibility. We avoid using payment or identity records for unrelated messages unless a lawful basis allows it. |
| Change tracking | When policy wording changes, the updated page should reflect real account handling rather than generic legal text. We keep the latest version available so you can read the current position. |
Visible privacy markers on this page
We design the Privacy Policy page so you can scan the parts that matter before opening an account. Section labels, short badges and contact cards are placed to...