Terms link
Our terms explain account conditions, while this Privacy Policy explains the data used to apply those conditions, such as identity checks, login records and case history.
LEGAL REFERENCE
Privacy Policy for Your z00m Account
z00m gives you one clear Privacy Policy for account data, identity checks, payment records and support chats tied to your Pakistan access. Read it before you open an...
Pakistan data contextAccount recordsSupport chat privacyRaast and wallet references
How We Handle Your Account Data
This Privacy Policy explains how z00m collects and uses data when you create an account, verify access, contact support or use services where local law permits. We process details such as your name, contact fields, device signals, login history, wallet reference numbers and transaction status updates so your account can be maintained, checked and protected. We do not ask for more data
than the account flow needs. Some records must be kept for security checks, dispute handling and legal requests, while other items are retained only for operational troubleshooting. Where payment providers send confirmation data, we keep the reference tied to your account rather than storing unnecessary wallet credentials.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
PRIVACY CONTACTS
Contact Us About Privacy
If you have a privacy question, we keep the contact path separate from general lobby help. Tell us which account field, support chat or transaction reference you mean, and avoid sending full wallet credentials. We may ask for account proof before changing or sharing personal records.
Team online
Privacy email
Write to [email protected] for access, correction or deletion requests. Include your account email and the relevant date range so we can locate records without asking for extra personal data.
Secure live chat
Use account chat for urgent privacy concerns tied to login activity or payment references. Our team can mark the case for privacy handling after checking that the account belongs to you.
Document requests
If you need a copy of account data, ask through the logged-in help area. We package available records carefully and may remove security-sensitive fields before release.
POLICY CHECKS
How We Keep Policy Work Accurate
Our Privacy Policy is maintained by people who work with account flows, security checks and Pakistan support cases. We check wording against real data paths rather than using broad legal filler. When...
Account mapping
We map each policy statement to an account step, such as signup fields, login checks, profile edits, KYC prompts, support chats or transaction references from Pakistan wallet rails.
Retention checks
We set retention periods around security needs, dispute windows and legal duties. Records that no longer support those purposes are reduced, archived or removed through internal data handling controls.
Access controls
Staff access to personal records is role-based. Support can see what is needed for a case, while sensitive checks require extra permission and leave internal access logs.
Payment separation
Wallet credentials stay with JazzCash, Easypaisa, SadaPay, NayaPay or Raast providers. We store transaction references, status messages and timestamps needed to resolve account questions.
Device security
We use device and session signals to detect unusual account access. These signals help protect your profile without turning the Privacy Policy into broad device tracking language.
Change logs
When policy wording changes, we keep internal version records showing what changed and why. This helps our team answer questions about older account activity accurately.
POLICY ALIGNMENT
Privacy Alignment Across Our Policies
Privacy wording must stay consistent with the rest of our legal pages. This section explains how we keep the Privacy Policy aligned without repeating every legal point. If another policy mentions account...
Cookie link
Our cookie page covers browser storage, while this Privacy Policy explains how session data connects with account security, personalisation and troubleshooting after you log in.
Promotions link
When promotions require account checks, this Privacy Policy explains which records may be checked, such as eligibility status, device signals, redemption history and support notes.
Payments link
Payment pages explain transaction steps, while this Privacy Policy explains how wallet references, bank confirmation data and failed transaction records are stored against your account.
Security link
Security wording focuses on account protection. This Privacy Policy explains the personal data behind those protections, including login timestamps, device markers and suspicious access alerts.
Support link
Support pages explain how to reach us. This Privacy Policy explains how chat transcripts, email replies, attachments and complaint history are stored, accessed and retained.
Regional access link
Where local law permits access, regional wording explains availability. This Privacy Policy explains how location signals and country settings may be used during account checks.
Policy Page Layout Signals
We designed this Privacy Policy page to make the data journey easier to read before you open an account. The layout highlights what is collected, where...
Plain headings
Each heading names the privacy issue first, so you can scan collection, use, sharing, retention and contact rights without reading unrelated lobby language.
Local context chips
Short chips mention JazzCash, Easypaisa, SadaPay, NayaPay and Raast only where privacy context matters, such as transaction references and confirmation records.
Account-first wording
We write in account terms rather than abstract legal phrasing. That helps you connect each privacy statement to login fields, support chats and wallet reference handling.
Contact placement
Privacy contact routes sit close to the policy explanation, so you can request correction, access or deletion without searching through general help topics.
Retention markers
Retention wording appears beside the relevant data category. You can see why certain records stay longer, especially security logs, dispute evidence and verification outcomes.
Update clarity
When we change the Privacy Policy, the page structure helps us show the affected area instead of rewriting unrelated sections or hiding changes in dense text.
Privacy Policy Questions for Pakistan
We collect account details you provide, verification results, login records, device signals, support messages and transaction references. The exact data depends on the account step, payment rail and support case involved.
No. Wallet PINs and app credentials stay with the payment provider. We keep only the reference details needed to match a transaction status, resolve disputes and keep account records accurate.
Device data helps us recognise account access patterns, reduce fraud risk and troubleshoot login issues. We use signals such as browser type, session timing and security markers tied to your account.
Yes. Send a correction request through [email protected] or the logged-in help area. We may ask for account proof before changing fields that affect access, verification or transaction handling.
Retention depends on the record type. Support chats may be kept for case history, while verification and transaction records can stay longer for security, dispute handling and legal duties.
We share only what is needed to process, confirm or investigate transactions through providers such as JazzCash, Easypaisa, SadaPay, NayaPay and Raast. We do not sell your personal account data.
Contact us from your registered email or logged-in account and ask for an account data copy. We verify the request first, then prepare available records with sensitive security fields removed.