How cm2 Handles Your Privacy
Your cm2 account connects live casino, slots and sportsbook activity with JazzCash, Easypaisa, SadaPay and Raast records, and this Privacy Policy explains how we handle that data where...
Policy Position For Pakistan Accounts
This Privacy Policy sets out how we collect, use, store and protect data linked to your cm2 account in supported regions of Pakistan. We collect account details you provide, device and session signals, identity checks, payment references, support messages and activity records needed to run the service safely. When you use JazzCash, Easypaisa, SadaPay or Raast, we may record reference numbers, timestamps
and verification outcomes, not your full banking credentials. We use this data to manage account access, process requests, detect unusual activity, answer privacy questions and meet legal duties where local law permits. We keep data only for as long as needed for account, security, tax, dispute or legal reasons, then remove or anonymise it through our internal process.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Contact Us About Privacy
Privacy questions should reach the team that can read your account context without asking you to repeat sensitive details in open chat. We separate normal lobby help from privacy requests, so account access, data correction and deletion questions move through a more careful channel.
Account privacy inbox
Use our privacy email path for access, correction or deletion requests. Include your cm2 account name, Pakistan region and the payment reference if your question concerns JazzCash, Easypaisa, SadaPay or Raast activity.
Live chat handoff
Chat can collect the first outline of your concern, then move the case to our privacy queue. We avoid asking for full wallet credentials or private banking data inside a chat window.
Security case route
If you see account access you do not recognise, tell us through the security route. We may lock the session, check device signals and verify payment references before reopening access.
How We Keep Policy Text Accurate
We write this Privacy Policy from our own operating flow, not from a template left untouched. The text is checked against account screens, wallet reference capture, support scripts and security tooling so...
Operator wording
We describe the data we actually handle inside cm2, including login signals, account records, payment references and support messages. We avoid vague claims that do not match our working tools.
Local payment checks
Our policy names JazzCash, Easypaisa, SadaPay and Raast because those rails create real reference records. We explain the receipt data we keep and the credentials we do not ask you to send.
Access verification
When you ask for data access, we verify that the request belongs to your account. That may involve account name, recent session details and payment reference matching before we release records.
Retention discipline
We connect retention periods to real reasons such as account management, security checks, dispute handling and legal duties. Data that no longer has a valid reason is removed or anonymised.
Support training
Our support team receives privacy handling rules, including what not to ask for in chat. Full wallet credentials, private banking passwords and unrelated personal files are not part of our request flow.
Change log habit
When we adjust the Privacy Policy, we update the page date and align support replies with the current text. Material changes are written in clear Pakistani English.
Policy Consistency Across Legal Pages
Your privacy rights touch other legal pages, so we keep their wording aligned. This page explains data handling, while our other pages explain service rules, cookies and account...
| Privacy Policy | This page focuses on personal data, session signals, payment references, privacy requests and retention. It is the page to read when you want to know how cm2 handles account data. |
|---|---|
| Terms page | The Terms page explains account rules and service use. We keep its wording aligned with this Privacy Policy when identity checks, account closure or security holds involve personal data. |
| Cookie page | The Cookie page explains browser storage and analytics signals. This Privacy Policy connects those signals to wider account handling, including session security and preference management. |
| Security notices | Security notices explain alerts, unusual access and account protection steps. This Privacy Policy explains what data we process when we investigate those events and contact you. |
| Payment wording | Payment text across cm2 uses the same local rail names: JazzCash, Easypaisa, SadaPay and Raast. This Privacy Policy explains the data footprint behind those references. |
| Support replies | Support replies should not contradict this page. When your request concerns access, correction or deletion, we route the answer through privacy wording rather than a general lobby response. |
| Account closure text | Closure wording explains what happens to access, while this page explains what happens to retained records. Some records may stay for security, dispute or legal reasons before removal. |
Visible Privacy Cues On cm2
We design the Privacy Policy page so you can see the main data points without searching through heavy legal phrasing. Labels, dates, contact routes and local account examples...