Cookie wording
The cookie page explains browser storage, while this Privacy Policy explains account data. Where both mention device signals, we use matching wording so tracking choices are easier to understand.
LEGAL REFERENCE
Privacy Policy for Your cz99 Account
cz99 gives you a clear Privacy Policy for account data, device records, support chats and Pakistan payment references before you open your account. We explain what we collect...
Account data usePakistan payment contextSupport privacy pathsPolicy update tracking
How We Handle Your Data
Our Privacy Policy applies when you use cz99 in supported regions of Pakistan where local law permits. We collect only the data needed to create your account, keep access secure, process transaction references, respond to support requests and meet platform safety checks. This may include your name, contact details, device signals, login times, IP data, wallet reference IDs and messages you send
to us. We do not sell your personal data. We may share limited records with hosting partners, verification tools, fraud-screening providers, payment processors and support systems when that sharing is needed to run your account. We keep records for the period required for account handling, dispute checks, transaction tracing and legal duties, then remove or anonymise them when retention is no longer
needed.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
POLICY CONTROLS
How We Keep This Policy Current
We treat the Privacy Policy as a working account document, not a static page. When a tool, support channel or payment rail changes the data we handle, we check whether the wording...
Named data categories
We separate contact data, login signals, device records, payment references and support messages so you can see why each category exists and which account task it supports.
Local rail mapping
Pakistan rails are described by reference type, not by unnecessary wallet access. JazzCash, Easypaisa, SadaPay, NayaPay and Raast checks use transaction IDs and account matching fields.
Access permissions
Only staff roles that need account records for support, risk checks or transaction tracing can view them. Access is logged, limited and removed when a role no longer requires it.
Retention checks
We keep records for account handling, disputes, fraud checks and legal duties. When those reasons end, we aim to delete, aggregate or anonymise data instead of keeping full records.
Change log practice
When this Privacy Policy changes, we update the effective wording and keep older internal copies for comparison. That helps us answer questions about which terms applied earlier.
Plain language checks
Before publishing changes, we check whether the wording can be read on mobile and whether key actions, such as access or correction requests, are easy to find.
POLICY ALIGNMENT
Policy Pages Read the Same Way
Our Privacy Policy sits beside related legal pages, and we keep the wording aligned so your rights, contact routes and data descriptions do not conflict. Each page has its own purpose, yet...
Account terms
Account terms describe service access, and this page describes data handling linked to that access. We align identity checks, login security and contact details so the pages do not clash.
Promotion records
If a promotion creates account records, this Privacy Policy explains how those records are stored. Related terms explain eligibility, while privacy wording covers retention, correction and support access.
Payment references
Transaction pages may show how a payment is submitted. This Privacy Policy focuses on the records created afterward, including reference IDs, matching checks and limited sharing with processors.
Support transcripts
Support terms explain how to contact us. This page explains how chat and email transcripts are linked to your account, who can view them and when they may be retained.
Security wording
Security pages may describe login protection. This Privacy Policy explains the personal data used for those protections, including device markers, access times and failed login signals.
Regional wording
Where access depends on supported regions, the same phrase appears across our legal pages. That keeps Pakistan-focused access wording consistent without adding broad claims outside this policy.
PAGE SIGNALS
Privacy Layout You Can Scan
The Privacy Policy is arranged so you can find the answer before sharing more data with us. We use short headings, local examples and direct contact cues rather...
Short section labels
Each Privacy Policy section starts with a clear label, so...
Local examples
Pakistan examples appear where they help explain real records, such...
Action cues
When you can ask for access, correction or removal, the...
Plain data labels
We use labels like contact details, device records and support...
Mobile reading flow
The page avoids dense blocks where possible, with card-style explanations...
Change awareness
The policy layout makes updates visible through dated wording and...
Privacy Policy Questions Answered
We collect account contact details, login records, device signals, IP data, transaction references and support messages. Each category supports account access, security checks, transaction tracing or customer help under this Privacy Policy.
No. We do not need your wallet PIN for privacy or transaction checks. We may store reference IDs, timestamps and matching details so a payment record can be traced safely.
Device and login records help us protect account access, detect unusual activity and respond to disputes. The Privacy Policy explains these records separately so you can understand their security purpose.
Yes, you can contact support to request a correction. We may verify account ownership first, then update eligible records or explain why a transaction or legal record must stay unchanged.
We share limited data only when needed for hosting, verification, fraud checks, payment processing, support tools or legal duties. We do not sell your personal data to outside advertisers.
Retention depends on the record type and the reason it exists. Account, support and transaction records are kept for required handling periods, then deleted, aggregated or anonymised when no longer needed.
When the policy changes, we update the page wording and may highlight practical changes through account or support channels. You can contact us if you need clarification on older wording.