LEGAL REFERENCE

Privacy Policy for your mk2 account

mk2 puts account data, privacy choices and Pakistan payment context into one clear policy before you open your account. Read how we handle your details for identity checks...

Pakistan privacy contextJazzCash record handlingEasypaisa privacy flowRaast payout logs

Explore the Lobby Read FAQ

How this policy applies at mk2

This Privacy Policy explains how we collect, use, store and share data when you create an mk2 account, browse the lobby, contact support or use Pakistan payment rails in supported regions. We collect the details needed to run your account, protect access, process wallet movements and keep service records accurate. That may include your name, contact details, device signals, login history, payment

reference numbers and messages you send us. We do not ask for more than we need for account operation, checks, security and legal duties. If a request involves JazzCash, Easypaisa, SadaPay or Raast, we may keep transaction references so our support team can trace a credit, payout or failed attempt without exposing extra personal data.

Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.

CONTACT ROUTES

Privacy questions reach real support

If your privacy request needs human help, contact us from inside your account or through the help channel shown on mk2.one. We...

CHECK RHYTHM

How we keep policy wording current

Our policy is checked against the way mk2 actually operates, not against a template. When account screens, wallet labels, security tools or support flows change, we adjust this page so your privacy...

Account flow checks

We compare this policy with the data collected during account opening, login recovery and profile updates. If a field is added or removed, the privacy wording is updated to match that change.

Wallet record checks

Payment wording is checked against JazzCash, Easypaisa, SadaPay and Raast handling. We focus on transaction references, status logs and support visibility, not unnecessary access to your wallet app.

Security wording checks

Device, session and access-control language is checked when our security tools change. The policy explains why signals are used, how they protect your account and when support may inspect them.

Support script checks

We compare privacy replies with the policy so you get consistent answers. Support should explain data access, correction and account checks in plain Pakistani English rather than vague legal wording.

Retention checks

Record-keeping periods are tested against account, payment and legal needs. We keep data while it is needed for service operation, dispute handling, security checks or duties that apply in supported regions.

Change log discipline

When policy wording changes, we keep an internal record of what changed and why. That helps our team answer your privacy questions without giving mixed explanations across support channels.

Same privacy stance across mk2 pages

This Privacy Policy connects with our terms, cookies wording and support replies. Each page has a separate job, but the data handling position stays aligned so you can...

Terms connection

Our terms explain account rules, while this policy explains the data used to apply those rules. The two pages should never give conflicting wording about identity checks, access records or payment traces.

Cookie connection

Cookie wording covers browser storage, session tools and preference signals. This privacy page explains how those signals fit into account access, security monitoring and smoother navigation after you return.

Support connection

Support replies should follow this policy when answering privacy requests. If your question involves stored contact details, payout references or login activity, the answer should match the wording here.

Security connection

Security pages may describe account protection in action. This policy explains the personal data behind that protection, including device signals, login timing and checks used to detect unusual access.

Payment connection

Wallet pages may show JazzCash, Easypaisa, SadaPay and Raast as options. This policy explains how related references are stored and used when a transaction needs support attention.

Promotion connection

If we display account rewards or campaign records, this policy covers the profile and activity data behind them. You can ask support how such records connect to your account history.

Region connection

Where local law permits access, this policy applies to supported regions in Pakistan. If availability changes, we adjust account messaging and privacy wording so the position remains clear.

Visible privacy cues around mk2

Privacy should be easy to notice while you move through mk2. We place account, security and support cues near the actions that create data, so you...

Profile prompts

When we ask for profile details, the screen should make the purpose clear. Your contact data supports login, account recovery, support replies and account checks rather than unrelated use.

Session cues

Login and device records help us recognise your access pattern. If a session looks unusual, those records let support ask focused questions instead of requesting broad personal documents.

Wallet labels

Payment labels show which rail is involved, such as JazzCash, Easypaisa, SadaPay or Raast. Clear labels help you connect a privacy query to the right record quickly.

Message context

Support chat and email threads are kept with account context so we can continue a privacy case accurately. We avoid asking you to repeat sensitive details already confirmed.

Preference controls

Where settings are available, they help you manage account contact choices and browser preferences. We design them to be direct, visible and tied to the data purpose shown on screen.

Policy access

The privacy link stays available from mk2.one so you can return to it before opening an account, during wallet checks or after contacting support about stored records.

Privacy Policy questions from Pakistan

We collect details needed to run your account, such as contact data, login records, device signals, payment references and support messages. The purpose is account access, service operation, security checks and legal record duties.

Payment references help us trace JazzCash, Easypaisa, SadaPay and Raast activity when you ask for support. They show status, timing and account connection without requiring access to your wallet app.

Yes. Contact support from your account or verified email and ask about your stored records. We may complete identity checks first so your data is not shared with another person.

We use login records, device signals and account checks to detect unusual access. These tools help protect your profile, limit unauthorised changes and give support a clear path when recovery is needed.

We share only what is needed to process or trace a transaction through supported rails. For Pakistan requests, that may involve JazzCash, Easypaisa, SadaPay or Raast references connected to your account.

We keep records for as long as needed for account service, security, transaction disputes and legal duties in supported regions. When a record is no longer required, we aim to remove or limit it.

We update this page when our data handling changes. If a change meaningfully affects your account, wallet records or privacy choices, we may also show a notice inside mk2.