Privacy Policy for Your mk1 Account
mk1 keeps privacy choices, account data and Pakistan payment records in one policy, so you can see what we collect before you open your account. The policy explains...
How We Handle Your Privacy Data
This Privacy Policy describes how mk1 collects, uses, stores and shares data connected to your account in supported regions of Pakistan. We collect details you give us, such as your name, mobile number, email address and login credentials, plus technical records such as device type, session timing, IP signals and security checks. When you use JazzCash, Easypaisa, SadaPay, NayaPay or Raast, we
may keep transaction references, account matching records and verification results so your balance activity can be reconciled. We do not ask you to send unnecessary screenshots or unrelated personal documents through open channels. Where local law permits, we use this data to manage access, secure your account, answer privacy requests and keep records required for payment and account safety checks.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
How We Keep This Policy Current
Our privacy wording is written from the way mk1 actually handles account data, not from a generic template. We check it against product changes, support flows and payment...
Account flow mapping
We compare the policy with the data fields you complete during account opening, login recovery and profile edits, so the...
Security data checks
Login alerts, session records and device signals are described because they protect your account from unwanted access. We keep the...
Local rail alignment
JazzCash, Easypaisa, SadaPay, NayaPay and Raast records are checked against our payment handling process, so privacy wording matches the references...
Support script matching
We align privacy contact wording with the answers our support team can actually provide. That keeps your request path clear...
Access control
Internal access to privacy records is limited by role, and sensitive requests move through identity checks. The policy explains these...
Change tracking
When we amend this policy, we keep internal change records showing what was altered and why. That helps our team...
Consistent Privacy Language Across mk1 Pages
Your privacy rights should not change from one mk1 page to another. We keep the core privacy message aligned across account pages, promotion screens, wallet records and support...
| Account pages | Profile and login pages use the same privacy base as this policy, covering identity details, contact records and security checks needed to keep your account reachable and protected. |
|---|---|
| Wallet screens | Wallet areas show payment references for JazzCash, Easypaisa, SadaPay, NayaPay and Raast, while this policy explains why those references may be stored and matched. |
| Support forms | Support forms ask for only the details needed to handle your privacy request or account issue. The policy sets the reason for collecting those contact and case records. |
| Promo board | If you check what is running this week, the privacy rules still apply to any account tags, eligibility records or contact preferences connected with that screen. |
| Live casino access | Live table access can create session and device records. This policy explains how those records support account security without changing your privacy rights on other pages. |
| Sportsbook records | Sportsbook activity may create account history and settlement records. The same privacy principles apply, including access controls, retention needs and request handling through support. |
| Mobile layout | The mobile view collects the same account data as the larger screen view, though menus may look different. This policy applies to both layouts equally. |
Privacy Page Highlights You Can Scan
We designed this privacy page so you can move from headline points to deeper details without losing the thread. The layout separates data collection, storage, sharing, contact paths...