Terms page link
The Terms page explains account use, while this Privacy Policy explains the records created during that use. We keep the two pages aligned so account rules and data handling do not conflict.
999zt keeps account, device and transaction data in one plain Privacy Policy so you can see how your details move through our Pakistan account flow. Open your account...
Our Privacy Policy applies when you access 999zt in supported regions, where local law permits, and use our account, lobby, support, security or transaction features. We collect only the data needed to open and maintain your account, verify access, process requests, protect the service and meet legal duties. That may include your name, mobile number, login records, device signals, payment references, support
messages and withdrawal checks. We do not sell your personal data. We share limited records with service partners only when they help operate account access, fraud checks, payment routing, hosting, analytics or support. We keep records for as long as needed for these purposes, then remove or anonymise them under our retention process.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
This Privacy Policy is checked by people who operate account access, support queues, payment reconciliation and security monitoring for 999zt. When a process changes, we update the wording so you can see...
Our account team confirms what data is collected during opening, login and recovery. That keeps the policy aligned with the screens you see when creating or returning to your account.
Operations staff compare policy wording against JazzCash, Easypaisa, SadaPay, NayaPay and Raast reconciliation steps. We describe only the references we need to match funds and account history.
Device, IP and session signals are used to protect account access and detect unusual activity. We explain those signals because they can affect login checks and support verification.
Support messages may include account questions, screenshots or payment references. We limit access to trained staff and keep the records only for service, dispute and safety purposes.
Retention periods are tied to account operation, legal duties, payment disputes and fraud prevention. When a record is no longer required, we remove it or convert it into non-identifying data.
Material privacy changes are dated on the page and checked against internal process changes. You can revisit this policy whenever you want to see the current data handling position.
Our Privacy Policy connects with other legal pages, but it has its own purpose: explaining data collection, use, sharing, storage and your request routes. The points below show how we keep privacy...
The Terms page explains account use, while this Privacy Policy explains the records created during that use. We keep the two pages aligned so account rules and data handling do not conflict.
Cookie wording covers browser storage and device signals. This Privacy Policy connects those signals to account security, analytics and service operation, giving you the wider data handling context.
Identity and account verification are explained here from a data angle. Other legal pages may describe when checks happen, but this page explains what records support those checks.
Transaction pages may show status, reference codes and timing. This Privacy Policy explains how those references are stored, matched and shared with service partners when needed.
Support pages tell you how to reach us. This Privacy Policy explains how messages, attachments and chat history are used to solve your request and protect your account.
Security language stays consistent across account access pages and this policy. Here we explain the data behind login alerts, device recognition and unusual activity checks.
When related legal pages change, we check this Privacy Policy for matching data impacts. If a change affects collection, sharing or retention, the privacy wording is updated.
We designed this Privacy Policy so you can find the data point you care about without reading unrelated service copy. Each visible block has a role: what we...