Account terms match
Where the account terms mention identity checks or transaction records, this policy explains the privacy reason behind them. That makes the legal wording and the account flow easier to compare.
LEGAL REFERENCE
Privacy Policy for z111 accounts
z111 places account identity, lobby activity, device signals and Pakistani payment records under one Privacy Policy, so you can see how your data is handled before you open...
Account data useJazzCash contextEasypaisa contextPrivacy contact
How our privacy posture works
This Privacy Policy applies when you use z111 in supported regions and where local law permits access to our services. We collect the details needed to open and secure your account, confirm your identity, process local payment records, manage sessions, answer support requests, and protect the lobby from misuse. Payment references from JazzCash, Easypaisa, SadaPay and Raast are used to match your
account activity with the request you make, not to expose your banking app activity to the public lobby. We keep records for operational, security, tax, dispute and legal reasons, then reduce or remove them when they are no longer needed. We may update this policy when our account flow, support process or legal duties change, and we place the current wording on
this page.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
POLICY CHECKS
Signals behind this policy
We write this Privacy Policy from the way z111 is operated, not from a generic template. The wording reflects account opening, identity checks, local payment matching, support case handling, device security and...
Operational ownership
Our account, support and security teams feed into the policy wording because they handle privacy events every day. That keeps the page tied to real workflows rather than abstract legal wording.
Local payment clarity
We name JazzCash, Easypaisa, SadaPay and Raast because those rails create specific receipt and reference records. The policy explains how those records support matching, correction and dispute handling.
Session security
We collect device, browser and session signals to spot unusual access patterns and protect your account. Those signals are used for security checks, not for showing private activity to other account holders.
Data minimisation
We aim to ask only for data that supports account access, verification, payments, support or legal duties. When a field is optional, the account flow should make that clear before you submit it.
Update discipline
When we change account flows or support handling, the policy text is checked against those changes. We keep older internal references so our team can understand what wording applied at the time.
Plain language
We use direct Pakistani English so you can understand what happens to your data without decoding legal jargon. Where a term is unavoidable, we connect it to a practical account action.
PAGE ALIGNMENT
Consistency across privacy pages
This Privacy Policy sits beside our cookie wording, account terms and security messages. We keep the same data categories across those pages, so you do not see one purpose described here and...
Cookie wording link
Our cookie page deals with browser storage and similar tools, while this policy explains the wider data picture. Both pages use matching language for session, preference and security purposes.
Security message fit
Login alerts, password resets and device checks are described in the same practical style across the site. This policy adds how related records may be kept and used.
Support case consistency
When support asks for verification details, the request should match the privacy purposes listed here. We do not ask for unrelated personal data just to answer a simple policy question.
Payment record wording
Payment screens may show receipt references, provider names and status labels. This policy explains why those records are connected to your account and how they help resolve mismatches.
Region wording
Access statements use supported regions and where local law permits, and the same approach appears across related pages. That keeps privacy language aligned with availability wording.
Change handling
If we adjust wording on one privacy-related page, we check related pages for matching changes. That reduces conflicting language and helps you follow the same data journey.
VISIBLE CUES
What you see on this policy
The policy layout is built to help you scan data topics without losing the legal meaning. Each visible block points to a privacy purpose, a contact route or...
Privacy badges
The chips near the hero point to account data, payment...
Purpose-led blocks
Sections are arranged around why data is collected, not around...
Local context labels
When a Pakistani rail such as JazzCash or Raast is...
Actionable contact text
Contact cards explain what to include and why we may...
Plain reading order
The page moves from scope to contact, checks, alignment and...
FAQ focus
The questions cover practical privacy situations such as access, correction...
Questions about z111 Privacy Policy
We collect account details, identity check records, contact data, login signals, device data, support messages and payment references. The exact fields depend on what you do in your account and what checks apply.
JazzCash, Easypaisa, SadaPay and Raast references help us connect a payment request with the correct z111 account. They also help us investigate mismatches, reversals or support questions about a specific transaction.
Yes, you can contact us through the account email or signed-in chat. We may verify your identity first, then provide data that can be shared under applicable law and security controls.
We keep data while your account is active and for periods needed for security, disputes, tax, payment matching and legal duties. When records are no longer required, we reduce or delete them.
We may share necessary data with service providers that support payments, verification, hosting, security, analytics or customer care. They should use the data only for the purpose connected to z111.
Contact support from your account and explain what is wrong. We may ask for proof before changing identity, email, phone or payment-related records, especially if the change affects security.
We place the current Privacy Policy on this page and may update wording when our processes or legal duties change. You should read it again before sharing new account details.