Legal terms for your cm2 account
cm2 sets out account rules, privacy handling, payout checks and Pakistan access limits before you open your account. Read this page so your next step is clear where...
Our Pakistan legal notice
This legal notice explains how cm2 presents access, account creation, identity checks, wallet records and dispute handling for Pakistan. We make access available only in supported regions and where local law permits. You are expected to give accurate account details, keep your login secure and use payment channels that are in your own name. When JazzCash, Easypaisa, SadaPay or Raast records are
used to confirm a transfer, we may ask for matching references before releasing a payout. We may pause an account while we check identity, unusual activity, duplicate profiles or requests from a payment provider. These terms sit beside our privacy and cookie policies, so your account record, device signals and contact history are handled under one legal framework.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
How to reach our legal desk
Legal questions need a clear route, not a maze. We separate account help, privacy requests and payment disputes so you can send the right record first and avoid repeating yourself later.
Live chat escalation
Start with chat when your legal question is linked to a current account action. Our team can collect your account ID, payment reference and device time, then move the matter to the right internal queue.
Privacy mailbox
Use the privacy mailbox for data access, correction or removal requests. We ask you to confirm account ownership first, then we log the request with a dated record for later checking.
Payout dispute route
If a payout check is delayed, send the wallet reference, requested amount and account email together. That gives our legal and payments staff the same record instead of scattered screenshots.
How we keep policies dependable
Our legal copy is maintained by the cm2 team that handles accounts, payments and privacy requests. We update wording when our account flow changes, when Pakistan access wording needs refinement or when...
Plain wording
We avoid hidden legal phrasing where a direct sentence works. If we need a technical term, we place it beside the account action it affects, such as verification, payout release or data storage.
Account evidence
Policy decisions rely on records you can identify: account email, wallet reference, device time, chat transcript and payout status. That keeps legal handling tied to events rather than vague internal labels.
Pakistan context
We write for Pakistan in clear English, including JazzCash, Easypaisa, SadaPay and Raast references where they affect verification. We do not copy generic wording that ignores local payment habits.
Change tracking
When policy text changes, we keep a dated internal record and note the account process that caused it. That helps support explain which rule applied when your request was made.
Privacy separation
Privacy requests are separated from ordinary support messages because they may involve identity proof, data export or removal. This protects your account record from casual handling during routine chat contact.
Fair dispute handling
Disputes are checked against the same account records used by our operations team. We look at timing, wallet references, login signals and prior support contact before responding with a position.
How legal pages stay consistent
This page is the starting legal layer, while our related policy pages handle narrower matters. We keep the same voice, account definitions and Pakistan access wording across them...
| Terms page | The terms page expands on account creation, suspension, wallet use and game settlement. This legal page points to those duties without replacing the detailed clauses you accept when opening an account. |
|---|---|
| Privacy page | The privacy page explains what personal data we collect, why we use it and how long we keep it. This page only summarises that privacy duties form part of our account framework. |
| Cookie page | The cookie page covers device identifiers, session tools and preference storage. We reference it here because legal access, fraud checks and login security can depend on device signals during account use. |
| Payments policy | The payments policy contains wallet processing detail for JazzCash, Easypaisa, SadaPay and Raast. This page frames those checks as legal account controls, especially where name matching or references are required. |
| Promotions rules | Promotional rules explain eligibility, expiry and reward release conditions. This legal page reminds you that any offer shown in your account is still subject to the wider account terms. |
| Security policy | The security policy deals with passwords, account access and suspicious activity. This page links that duty to your obligation to keep login details private and report unusual access quickly. |
| Complaint process | The complaint process explains how we receive, sort and answer disputes. This page gives the legal basis for asking you to send records that help us check the matter properly. |
Visible cues in our legal area
The legal area is designed to make key duties easy to find before you join. We use labels, short cards and clear account links so the page feels...