Privacy Policy for your pcx2 account
pcx2 gives you one Privacy Policy for account setup, lobby access, payment checks and support records, so you can see what data we collect before you open an...
How we handle your account data
This Privacy Policy applies when you use pcx2 in supported regions where local law permits. We collect the details needed to create and protect your account, confirm payment activity, respond to support messages and keep access records accurate. That can include your name, mobile number, account email, device signals, IP address, session logs, wallet reference records and messages you send to us.
We do not ask for more data than our account, security and legal duties require. When you use JazzCash, Easypaisa, SadaPay or Raast, we record transaction references so our team can match your request with your pcx2 balance history. We keep privacy language practical, and we update this page when our data handling changes.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
How our policy stays current
Our Privacy Policy is maintained as an operating document for pcx2, not a copied legal page. We connect the wording to real account actions: joining, logging in, funding through Pakistani rails, using...
Operational ownership
The policy is handled by people who understand account setup, wallet matching and support workflows. That keeps privacy wording tied to what we actually collect when you use pcx2.
Access records
We describe device, IP and session records because they help protect your account from unusual access. These records are used for security checks and support investigations, not casual profiling.
Payment trace clarity
JazzCash, Easypaisa, SadaPay and Raast references are stored to reconcile account balance activity. We state this clearly so you know why transaction records sit beside your pcx2 wallet history.
Change log discipline
When policy wording is amended, we keep the page focused on the new data practice or account process. We do not hide material privacy changes inside broad brand copy.
Support confirmation
Before we act on a privacy request, support may ask for matching details from your account. This helps us protect your records from being shared with the wrong person.
Plain English drafting
We write this policy in clear Pakistani English so you can understand what happens to your data without legal guesswork. Short labels, direct purposes and local payment examples keep it usable.
Aligned privacy pages across pcx2
Your privacy rights should not change because you move from one pcx2 legal page to another. We keep related pages aligned so account, cookie, wallet and support wording...
| Account terms | Where account terms mention identity checks or access rules, this Privacy Policy explains the related data record. The pages work together so you can see both the rule and the data use. |
|---|---|
| Cookie notice | Cookie wording covers browser storage and site measurement, while this policy explains how those signals connect to account security. We keep the boundary clear so each page answers a distinct privacy need. |
| Wallet wording | Payment pages may describe JazzCash, Easypaisa, SadaPay and Raast flows. This policy explains the privacy side, including reference matching, support checks and retention of transaction records. |
| Security text | Security wording may mention login alerts and device checks. This policy explains which device and session records support those checks, and why they are kept with your account activity. |
| Support pages | Support pages tell you how to reach us. This policy adds what we may collect during that exchange, such as screenshots, message history and verification details connected to your request. |
| Promo board | If you check what is running this week, we may record account eligibility markers. This policy explains those markers without turning privacy wording into broad promotional copy. |
| Regional access | Access wording refers to supported regions where local law permits. This policy explains how location signals may be used to apply those regional checks and protect your account access. |
Policy layout built for clarity
The privacy page is arranged so you can move from collection to purpose, storage, sharing and contact steps without hunting through unrelated copy. Each visible element has a...