How We Handle Your Privacy
mw2 keeps your Privacy Policy choices close to the account flow, so you can see how sign-in records, wallet references and device signals are handled before you open...
Our Privacy Policy For Pakistan
This Privacy Policy explains how mw2 handles personal data connected with your account, identity checks, login activity, wallet references and support messages where local law permits. We use account data to open and maintain your profile, protect access, process wallet requests, answer your questions and keep records required for safety, audit and dispute handling. Payment names such as JazzCash, Easypaisa, SadaPay and
Raast may appear in records when you choose those rails, but we do not ask you to send card passwords or one-time codes through chat. We keep data only for a practical legal, security or service reason, then restrict or remove it according to our internal retention steps.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Contact Us About Privacy Choices
Your privacy request should reach the team that can act on it, not a general inbox that delays the answer. Use the contact path that matches your issue, include only the details needed to identify your account, and avoid sending wallet passwords or one-time codes. We may ask follow-up questions before changing records.
Privacy mailbox
Write to privacy support with your account name, registered phone and the privacy choice you want logged. We answer in clear English and keep the thread tied to your case.
Live help escalation
If you start in chat, ask for a privacy escalation and describe the data concern briefly. Our agent moves the matter to a case queue before any account change is made.
Wallet record query
For JazzCash, Easypaisa, SadaPay or Raast references, share the transaction time and your account name only. We check records without asking for wallet PINs or app passwords.
How We Keep Policy Clear
We write this Privacy Policy from the systems we operate, not from generic legal wording. The page is checked against account creation, wallet handling, login security and support workflows so the wording...
Account flow basis
Policy wording is matched with the fields you see when opening your account, including phone, name and verification prompts. We avoid asking for data that has no clear account purpose.
Wallet data scope
Our privacy checks separate wallet references from private wallet credentials. JazzCash, Easypaisa, SadaPay and Raast entries may identify a request, while your PIN stays outside our records.
Device signal use
We may read device, browser and session signals to protect your access and detect unusual sign-ins. These signals support security decisions rather than public profile display.
Support access control
Support staff see the account details needed for your case, not an open file without limits. Sensitive actions require a logged reason before records are changed.
Retention checks
We keep records for account operation, dispute handling and legal needs, then reduce access when active use ends. The Privacy Policy explains why some records cannot vanish instantly.
Change logging
When privacy wording changes, we record the update date and the process behind it. This helps us explain what applied when you made a request.
Policy Alignment Across Account Pages
Your privacy expectations should not change as you move between account, wallet and support pages. We align this Privacy Policy with the shorter privacy prompts shown across mw2...
| Account page prompts | Short prompts near account fields match this Privacy Policy, so you can connect each field with its purpose. Phone and name entries are tied to access, checks and case handling. |
|---|---|
| Wallet screen wording | Wallet screens may show JazzCash, Easypaisa, SadaPay or Raast labels, while this page explains the related privacy handling. We keep rail names separate from secret wallet credentials. |
| Login alerts | Security alerts are linked to session data described here, including device and browser signals. We use those records to help protect access and investigate unusual account activity. |
| Support case scripts | Support scripts follow this Privacy Policy when agents ask for verification. You should be asked for enough detail to confirm the account, not extra private data. |
| Promo board privacy | When you check the promo board, any account matching uses the privacy basis explained here. We do not publish your private wallet or identity details there. |
| Lobby session records | Live casino, slots and sportsbook sessions create activity records attached to your account. This page explains how those records support history, security and dispute checks. |
| Policy change links | When a page links back here, it should point to the privacy reason behind the field or action. We use consistent wording to reduce confusion. |
Privacy Layout Cues You See
We designed the Privacy Policy page so the main choices are visible without making you hunt through dense legal blocks. Headings separate collection, use, sharing, security and contact...