Account terms link
Where account rules require identity checks, this Privacy Policy explains the data side of that process without repeating service conditions from our separate account terms page.
zd888 explains how your account data, payment records and device signals are collected, used and kept under this Privacy Policy for Pakistan. Open your account with clearer privacy...
Our Privacy Policy applies when you create or manage a zd888 account, contact support, pass security checks, or use Pakistan payment rails in supported regions. We collect only the data needed to operate your account, confirm wallet activity, prevent account misuse, respond to your privacy requests, and meet legal duties where local law permits. We do not sell your personal data. Where
a third party such as a bank rail, wallet provider, fraud-screening tool, or hosting partner handles data for us, we restrict its role to account service, safety, record keeping, or support delivery. You can ask us to explain, correct, or remove eligible data, subject to legal and security retention needs.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
If you need help with a privacy request, we route it to the team that can check account ownership and respond without exposing your data to the wrong person. Use the same name, phone number, or email linked to your zd888 account so we can match your request safely.
Ask chat to log a privacy request, correct account details, or explain a data record. We may ask security questions before discussing wallet, device, or access history.
Send a written request if you want a copy, correction, or deletion check for eligible data. Include your account email and avoid sharing wallet PINs or screenshots with secret codes.
If you suspect account access by another person, contact us quickly. We can lock sensitive changes while we check sign-in signals, device records, and recent privacy-related activity.
We write this Privacy Policy from our own account flow, not from generic wording. Each privacy point is checked against how zd888 collects data during sign-in, wallet matching, security checks, support chats...
Each data category in the policy is tied to a clear purpose, such as account access, wallet matching, safety checks, support handling, or legal record keeping in supported regions.
Only staff with a service need can see account records. Support sees enough to help you, while deeper wallet or security logs require extra internal permission.
JazzCash, Easypaisa, SadaPay, and Raast references are used to match transactions, solve account disputes, and meet audit duties. We do not ask for wallet passwords.
We use device and session signals to detect unusual access, protect your account, and keep login records accurate. These signals support safety rather than personal profiling for sale.
Some records must stay for legal, accounting, or security reasons. Other data can be corrected or removed when it is no longer needed for your account relationship.
Privacy requests are checked against account ownership before we respond. This protects you from another person trying to obtain your account or wallet history.
Your privacy rights connect with other zd888 legal pages, so we keep the wording aligned. The Privacy Policy explains data handling, while account terms explain service rules and cookie terms explain browser...
Where account rules require identity checks, this Privacy Policy explains the data side of that process without repeating service conditions from our separate account terms page.
Cookie text stays focused on browser storage, analytics, and session control. The Privacy Policy connects those signals to your wider account data and request rights.
Wallet pages may describe JazzCash or Easypaisa flows, while this page explains why related references are stored, who can see them, and when they may be retained.
Support pages explain how to reach us. This Privacy Policy explains how chat logs, email messages, and complaint records are handled after you contact us.
Security language stays consistent across sign-in, account recovery, and privacy requests. We use the same ownership checks before showing or changing sensitive account data.
Access language uses supported regions and where local law permits, so the Privacy Policy does not imply availability beyond the markets we can serve.
When we amend legal text, we adjust related pages so data, cookie, account, and support wording do not conflict with your current privacy rights.
We designed this Privacy Policy so you can find the data point you care about without reading unrelated service copy. Section labels separate collection, use, sharing, storage, rights...