Personal data
This page explains collection, use, storage, sharing and rights connected with identifiable account activity, contact details, device signals and support correspondence.
This Privacy Policy explains how 00zh88 collects, uses, stores and protects data connected with your account, access and support requests. We built the policy for people in Pakistan...
When you create or use a 00zh88 account, we may collect contact details, login records, device signals, approximate location, transaction references and messages sent to support. We use these details to provide account access, check unusual activity, process requests, meet applicable legal duties and keep our services functioning. Payment partners may send us confirmation references rather than complete wallet credentials. JazzCash, Easypaisa,
SadaPay and Raast records can therefore appear in your account history without exposing your full payment password. We retain data only for as long as needed for the stated purpose, legal requirements, dispute handling or security checks. Access is available only in supported regions and where local law permits. You may ask about access, correction or deletion by contacting us through the
channels shown below, subject to identity checks and records we must retain.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Our support paths are designed for privacy questions rather than general account promotion. Tell us what you want to understand, amend or remove, and include enough account detail for us to locate the correct record without sending passwords or wallet PINs. We may request additional proof before discussing personal data, helping prevent another person from taking action on your account.
Send a data request through the privacy contact shown in your account area. Include your registered email, request type and preferred reply route; never include a password, one-time code or JazzCash PIN.
Use our logged-in support chat for questions about stored profile details, access history or correction requests. We can explain the next step while keeping sensitive payment credentials outside the conversation.
We record the date, scope and status of each privacy request so our team can follow it through. If identity checks are needed, we will explain the reason before handling the request.
This page reflects the way our account and support flows are operated, not a generic statement detached from the service. We separate login protection from payment confirmation, limit staff access according to...
When an access or data request needs confirmation, we compare account details through a controlled process. This helps us respond to the right account holder without asking you to disclose private wallet credentials.
Browser, operating system and session details can help us detect unusual sign-ins or troubleshoot an account. These signals support security and service continuity, rather than serving as a public profile.
JazzCash, Easypaisa, SadaPay and Raast may provide confirmation identifiers for account reconciliation. We use those references to match a request while avoiding storage of your wallet password or PIN.
Our internal handling separates ordinary support work from sensitive account actions. Staff access is limited by task, and requests involving personal data can require an additional identity check before release.
Different records may remain for different periods because security logs, payment references and correspondence serve different purposes. We remove or anonymise data when the applicable need has ended.
The policy is written in clear English for Pakistan-facing account flows. If a privacy question needs clarification, support can explain the relevant process and the records connected with your request.
Privacy terms work alongside the account, cookie and service notices linked across 00zh88. Each page has a distinct purpose, so this policy focuses on personal data rather than describing every account feature...
This page explains collection, use, storage, sharing and rights connected with identifiable account activity, contact details, device signals and support correspondence.
Cookie choices concern browser storage and session tools. They may affect how pages remember settings, while this policy explains the wider handling of account-related data.
Login and security notices describe steps for protecting access. Privacy questions about sign-in records, device markers or identity checks belong with this policy.
Wallet confirmation references can support reconciliation and request handling. This page explains their data role without asking for your JazzCash, Easypaisa or SadaPay credentials.
Messages sent to our team may be retained for continuity, security and dispute handling. You can ask what correspondence is linked with your account.
Availability depends on supported regions and local law. Privacy rights may vary by location, so we use your relevant region when assessing a request.
If our data practices change, we may update this page and show a revised date or notice. The current wording applies to the active 00zh88 service.
The privacy side of 00zh88 is arranged to make important details easy to locate before you open an account or contact support. These visible elements identify...
A dedicated policy label keeps this page focused on personal data, account records and privacy choices rather than mixing legal subjects into one general message.
The main notice uses direct sentences to explain why data is collected, which records may appear and how long different categories may remain available.
Pakistan and supported-region wording appears where access or legal treatment can differ, helping you understand that availability and rights may depend on location.
Contact options sit close to the policy text so you can move from a question to a data request without searching through unrelated account pages.
Identity checks, limited staff access and protected account handling are highlighted because privacy depends on confirming who is making a request.
A visible policy update area can show when wording changes, allowing you to distinguish the current privacy terms from an earlier version.