Terms alignment
Our terms explain account rules, while this policy explains data handling behind those rules. Both pages use the same account and verification language.
cz999 keeps your account details, payment records and session activity under one clear Privacy Policy, so you know what we collect before you open your account. We explain...
This Privacy Policy explains how we collect, use, store and share data connected with your cz999 account in supported regions of Pakistan. We may process your name, phone number, email address, login device, IP address, wallet references, game session records and support messages so we can run account access, verify payment events and respond to privacy requests. JazzCash, Easypaisa, SadaPay and Raast
references are used as context for payment record matching, not for unrelated profiling. We keep records only for operational, security, legal and dispute handling needs. Where local law permits, you may ask us to correct, access or remove data that is no longer needed.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Privacy questions should reach the team that can read account logs, wallet references and message history without asking you to repeat sensitive details. We separate privacy requests from general account chat, then confirm your identity before we discuss records or make changes.
Open chat from your account area and ask for privacy help. We may request recent login or wallet reference details before discussing records tied to your cz999 profile.
Send privacy requests to [email protected] with your account name and reachable email. Do not include wallet PINs, passwords or screenshots showing full account balances.
If your request involves correction or deletion, we may contact you again to confirm ownership. This protects your records from changes requested by another person.
Our Privacy Policy is maintained as an operating document, not a decoration. We link each privacy statement to real account steps, payment checks and support actions, then keep...
Privacy wording is checked against how our account, wallet and support teams actually handle records. If a process changes, the...
Staff access to account records is limited by role. Support can see only the data needed to answer your request...
Login attempts, device changes and wallet actions can create security logs. These logs help us detect unusual access and answer...
JazzCash, Easypaisa, SadaPay and Raast references are stored for matching and dispute handling. We avoid storing unnecessary wallet secrets or...
Cookies help remember sessions, language choices and security signals. You can adjust browser settings, though some account features may need...
When privacy wording changes, we keep internal version records so our team can explain what changed and why a newer...
Your privacy expectations should not change as you move between legal pages. We keep this page aligned with related account, cookie and security wording so the same data practice is described consistently...
Our terms explain account rules, while this policy explains data handling behind those rules. Both pages use the same account and verification language.
Cookie wording here matches the cookie controls shown elsewhere on cz999. Essential, preference and security cookies are described with the same practical purpose.
Where our security wording mentions login checks, this policy explains the data behind those checks, including IP address, device signals and session records.
Payment references across cz999 describe record matching in the same way. JazzCash, Easypaisa, SadaPay and Raast data is tied to account reconciliation.
Support agents use privacy language that reflects this page. They should not ask for wallet PINs, passwords or private app access during assistance.
Record retention statements remain consistent across legal pages. We keep data for account, security, legal and dispute needs, then remove what is unnecessary.
Requests to access, correct or remove data use the same identity checks wherever they appear. This keeps your privacy request route predictable.
This page is arranged so you can scan the parts that affect your account before you continue. Each visible element points to a privacy action, from what we...