LEGAL REFERENCE

Privacy Policy for mp5 Pakistan

mp5 keeps your privacy choices clear before you open an account, so you can see what data we collect, why we need it, and how it supports account...

Pakistan account dataJazzCash recordsEasypaisa checksSadaPay referencesRaast context
Explore Lobby Read FAQ
mp5 Privacy Policy for mp5 Pakistan

How We Handle Your Data

This Privacy Policy explains how mp5 collects, uses, stores, and shares data linked to your account, device, login activity, support messages, and local transaction references. We use these details to open and protect your account, process account actions, verify requests, respond to privacy questions, and meet duties that apply in supported regions where local law permits. We do not present this page

as licence advice or legal advice for every city or province in Pakistan. If a rule requires us to keep records for safety, audit, fraud prevention, or dispute handling, we keep the relevant data for the required period, then remove or anonymise it when retention is no longer needed.

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

REQUEST ROUTES

Contact Paths for Privacy Requests

Your privacy request should reach the team that can act on it. Use the account area for routine edits, live chat for identity-linked questions, or email when you need a written record. We may ask for verification before sharing or changing account data.

Team online

Account centre

Open your account area to correct profile details, check stored contact fields, and see recent security activity tied to your login. These edits stay within your account history so privacy changes remain traceable.

Live chat

Use chat when a privacy question is linked to an active session, recent login, or payment reference. Our team verifies account control before discussing personal data or explaining why a record is retained.

Email privacy desk

Send written privacy requests to [email protected] if you need access, correction, deletion, or a retention query logged. Include your account email only, not wallet PINs or full identity document numbers.

POLICY CHECKS

How We Keep This Policy Current

We maintain this Privacy Policy as part of our account operations, not as a detached legal page. Changes are checked against live account flows, support scripts, fraud controls...

Account flow checks

When we change registration fields, login steps, or verification prompts, we check whether this Privacy Policy still explains the data...

Support script alignment

Our support replies must match this policy when you ask about access, correction, deletion, or retention. If a script changes...

Local rail references

Where JazzCash, Easypaisa, SadaPay, or Raast references appear in account records, we describe them as transaction context, not as extra...

Security logging

Login attempts, device signals, and session events are treated as security data. We keep them only for account protection, fraud...

Retention checks

We separate data that can be deleted on request from data we must keep for account safety, audit trails, disputes...

Plain English updates

Policy wording is kept in clear Pakistani English so you can understand what mp5 collects, what choices you have, and...

Consistency Across Our Legal Pages

Our legal pages work together, but this page stays focused on privacy. If another page discusses account rules, cookies, promotions, or site terms, this Privacy Policy explains the...

Terms page link
The Terms page may describe account duties, while this page explains the data used to apply those duties, such as login records, verification checks, and support conversations.
Cookie page link
The Cookie page covers browser storage, while this policy explains how cookie-linked data can connect with your account, session safety, analytics, and consent choices.
Promotion page link
If a promotion page records eligibility or opt-in status, this policy explains how those account signals are stored, checked, and removed when no longer required.
Security page link
Security wording may describe controls, while this policy explains the personal data behind those controls, including device signals, failed login attempts, and verification outcomes.
Support page link
Support pages explain how to reach us, while this policy covers the privacy of chat logs, email messages, attachments, and identity checks used during help requests.
Payments page link
A payments page may name JazzCash, Easypaisa, SadaPay, and Raast, while this policy explains how transaction references are recorded for account checks and disputes.
Update consistency
When a linked legal page changes, we check this Privacy Policy so the data purpose, retention wording, and request routes do not drift apart.
VISIBLE CONTROLS

Privacy Elements You Can See

We place privacy cues where you can act on them, not only at the bottom of the site. Account screens, consent panels, support forms, and security prompts show...

Consent panels Where optional tracking or preference choices appear, the panel explains...
Field labels Account forms label required and optional fields so you know...
Security prompts When extra verification appears after a risky login pattern, the...
Support uploads If you attach a file in a support case, we...
Retention labels Where account history is displayed, we separate recent activity from...
Privacy links Key account pages link back to this Privacy Policy so...

Privacy Policy Questions Answered

We collect account details, contact fields, login records, device signals, support messages, and transaction references. The exact data depends on the account action you take and what is required in supported regions.

Transaction references help us match account activity, handle disputes, check fraud signals, and respond to support questions. We treat JazzCash, Easypaisa, SadaPay, and Raast references as account records, not unrelated profile data.

Yes. Use your account area for simple edits, or contact support if a locked field needs correction. We may verify account control before changing data that affects access or security.

You can ask us to delete data that is no longer needed. Some records may be retained for security, audit, dispute handling, or duties that apply where local law permits.

We share data only when needed for account operations, security checks, support handling, payment processing, analytics, or legal duties. Partners receive only the data needed for their assigned task.

We update the page date or wording when the policy changes. If a change materially affects your account privacy choices, we use suitable account or site messaging to draw attention to it.