Privacy Policy for Your cx66 Account
Live tables, slots and sportsbook access all create account records, and this Privacy Policy tells you how cx66 handles them. Open your account only when you are comfortable...
How We Handle Your Data
This Privacy Policy explains how we collect, use, store and share data when you create a cx66 account, enter the lobby, contact support, or use payment rails available in supported regions of Pakistan, where local law permits. We collect account details, device signals, transaction references, verification records and support messages so we can secure access, process withdrawals, answer privacy requests and meet
lawful duties. We do not sell your personal details. Limited service partners may handle payment routing, identity checks, hosting or fraud controls under contractual privacy duties. We keep records for as long as needed for account safety, dispute handling, tax or legal requirements, then delete or reduce them where practical.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Privacy Contacts That Reach Us
Your privacy request should reach the team that can act on it, not a general inbox loop. We give you three clear paths for access, correction, deletion, account-lock checks and data-use questions, with identity checks before any account record is changed or shared.
In-lobby chat
Use in-lobby chat for account access, correction, or removal questions. Ask for the privacy queue, share your account ID only inside the secure chat pane, and our team will trace the request.
Privacy email
Email [email protected] when you need a written record of your request. Include your account email, Pakistan mobile number if attached, and the privacy action you want us to check.
Account centre
Your account centre shows editable profile fields and security settings. Use it first for small corrections, then contact us if a locked field needs verification before we can change it.
How We Keep This Policy Accurate
We treat the Privacy Policy as an operating document, not a static footer link. Product, support and payment teams check the wording whenever account flows, verification steps or...
Local wording
We write privacy terms in clear Pakistani English, using the same labels you see during account setup, withdrawal checks and...
Payment records
JazzCash, Easypaisa, SadaPay and Raast references are described as transaction records, not public profile data. Access is limited to teams...
Access control
Internal tools separate support views from deeper verification records. Team access is logged, permissioned by role, and removed when staff...
Retention checks
We compare stored account records against legal, tax, dispute and security needs. Where a record is no longer needed, we...
Change log
Material policy changes are dated inside the page. When a change affects how we use your account data, we aim...
Support training
Support scripts include privacy request handling, identity checks and escalation paths. That helps the first agent route your request without...
Aligned Wording Across Policy Pages
Our Privacy Policy connects with other legal pages on cx66, but it has its own job: explaining data handling. We keep definitions, account terms and cookie wording aligned...
| Account terms | The account terms explain your use of cx66; this Privacy Policy explains what happens to the personal details linked with that use, including login activity, verification files and support history. |
|---|---|
| Cookie page | Cookie wording covers browser storage and similar tools. This page connects those tools to wider privacy handling, including device signals used for security, session continuity and fraud checks. |
| Cashier rules | Cashier rules set payment steps, while this page explains how related references are stored, who may see them, and why some records must remain available after a withdrawal request. |
| Security terms | Security text describes account protection measures. The Privacy Policy adds how security logs, failed login attempts and device markers are handled as personal or account-related records. |
| Support terms | Support terms describe contact channels and conduct. This policy explains how chat transcripts, email trails and uploaded files are used to answer your request and protect your account. |
| Promo rules | Promo rules may refer to eligibility checks. This Privacy Policy explains the data side of those checks, such as account status, transaction history and location signals in supported regions. |
| Withdrawal checks | Withdrawal wording explains processing steps. This policy explains the privacy layer: identity matching, payment reference storage, fraud screening and limited sharing with service partners when needed. |
Privacy Layout Signals You Can See
The Privacy Policy page is arranged so you can scan the legal parts without losing the action you need. Labels, badges and short panels show where...
Section labels
Each page block uses a short label before the heading, so you can quickly separate collection, use, sharing, retention and contact rights without reading the whole policy in one sitting.
Context chips
Short chips name records such as JazzCash references, Easypaisa receipts, SadaPay status and Raast IDs. They show the payment context without turning the policy into cashier instructions.
Action wording
Request wording is written around actions you may take: access, correct, delete, object or ask for clarification. We avoid vague labels when a direct privacy path is more useful.
Security markers
Lock and clock markers highlight account protection and retention points. These visual cues help you spot where we discuss restricted access, storage periods and deletion or reduction steps.
Update area
The policy layout leaves room for visible update dates and change text. When the Privacy Policy changes, this area helps you see what changed before you continue with cx66.
Mobile reading
On small screens, policy blocks remain short and stacked. You can open your account flow, return to the policy, and still find privacy contact details without hunting through long legal text.