Your Data, Explained By Us
Open an account with mwc casino and this page sets out exactly what we record, why we keep it and how you can ask us to correct it...
What Our Privacy Policy Covers
Your account gathers personal and payment data, and this policy sets out how mwc casino handles both. We collect your name, phone number, date of birth, device identifiers, login history, and the transaction references returned by JazzCash, Easypaisa, SadaPay and Raast when money moves in or out. We hold those records while your account stays open, and afterwards only for the retention
window local rules require. Data reaches processors that verify identity, clear payments and keep the lobby running, and only where local law permits that transfer. Staff access is limited to people who need your record to answer a query or meet a duty, and every look-up is logged. Rights such as requesting a copy depend on where you live, so steps differ
across supported regions.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Who Writes And Checks This
This policy is drafted by the team that operates mwc casino's account systems, then checked against the data rules applying in each market we serve. We date every change, keep earlier versions...
Written In-House
Every clause comes from the people who run the platform instead of a borrowed template. We can explain, line by line, which field is held and where it travels.
Checked Twice A Year
We read the wording against live systems at least twice a year, and again when a payment rail changes. Every update carries a date, visible in the header.
Old Versions Kept
Replaced versions stay archived with the date they were swapped out. If you want to know what the terms said when you opened your account, our desk can find that revision.
Local Rules Watched
Pakistan is our home market, so we track how JazzCash, Easypaisa, SadaPay and Raast handle customer records. Our wording follows what those partners and local law ask.
Edited For Clarity
Drafting passes through editors before publishing. Long clauses get split, defined terms are explained once, and paragraphs that read like a wall of text are rewritten for scanning.
Corrections Logged
Spot something unclear and tell us. Verified corrections reach the team owning that clause and appear in the next dated revision, so the fix stays visible rather than silent.
How Our Policy Pages Match
Our privacy wording sits beside the account terms and cookie notice, and the three read as one set. Where a term appears in more than one place it...
| Shared Definitions | Words like account data, processor and retention period mean the same here as in our account terms. One glossary runs across every policy page we publish for Pakistan. |
|---|---|
| Same Date Stamps | When one page changes, the others are checked the same day. You will rarely see a policy dated weeks apart from its siblings unless one clause genuinely moved alone. |
| Matching Contact Routes | The chat, email and help routes here are the same ones printed in the account terms. One desk owns privacy, security and payment queries instead of splitting them. |
| Consistent Retention | How long we hold a record is stated the same way on each page: account life plus the period local rules ask for. No page promises a different window. |
| One Consent Model | Optional cookies and promotional messages are turned on the same way wherever they appear, with the same off switch. Turning a channel off here clears it in settings. |
| Aligned Security Text | Encryption, login checks and staff access rules are described once, then referenced everywhere. Change how accounts are protected and the update lands across all pages. |
| Cross-Linked Pages | Each page links to the others from the footer and from the clause you are reading. A link mid-sentence opens the matching section, not a general landing screen. |
How We Lay Out The Wording
Each policy screen opens with a short summary before the full clauses, so you can tell quickly whether the section you need sits here. Side anchors...
Revision Badge
A dated badge sits at the head of every policy screen and moves each time we publish a change. One look tells you if the wording you read last month still stands.
Clause Anchors
Side links jump straight to the retention, sharing and access clauses. Handy when our support desk points you at one paragraph during a chat about your account record.
Summary Strip
Three plain sentences above the main text say what we hold, where it goes and how long we keep it. Full clauses follow underneath for anything the summary leaves open.
Field Table
A compact table lists each field we store beside its purpose and retention window. Scanning it beats reading the whole screen when you only want to know why one field is held.
Region Markers
Wording that changes by market is flagged, with the Pakistan position spelled out first. Readers in supported regions can see which clause follows local law rather than ours.
Contact Footer
Every screen closes with the same chat, email and help routes, so you never scroll back to find them. Quote a clause number when your query is about one paragraph.