Privacy Policy For Your 999wan Account
This Privacy Policy explains how 999wan collects, uses, stores and protects information connected with your account, device and account activity in Pakistan. We keep the policy focused on...
How We Handle Personal Data
We collect details you provide when you create or maintain an account, such as your name, contact details, login credentials and verification material. We also receive technical signals including browser type, device identifiers, IP address, language preference and session events, which help us secure access and diagnose faults. Transaction records may include the selected Pakistani rail, reference number, amount, status and timestamps
for JazzCash, Easypaisa, SadaPay or Raast requests. We use this material to operate account services, check unusual activity, answer enquiries, meet applicable legal duties and improve reliability. Access is limited by role, retained only as long as reasonably needed, and handled in supported regions where local law permits. You may contact us to ask about access, correction or deletion, subject to legal
and security requirements.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Ways To Ask About Your Data
Our support routes are designed for privacy questions rather than general account browsing. When you contact us, include the email or phone detail linked with your account and describe the request clearly, but do not send a password or one-time security code. We may ask for reasonable account confirmation before discussing personal data, changing contact details or responding to a deletion request.
Account help
Use the signed-in support route for questions about profile details, access records or a correction request. We can ask for account confirmation before exposing or changing personal data.
Privacy requests
Send a privacy enquiry through our contact channel when you want to ask about collected data, retention, processing purposes or a copy of information linked with your account.
Security alerts
Tell us promptly if your account details appear changed without permission. We can restrict access, check recent sessions and guide you through secure recovery using verified contact details.
Controls Behind This Policy
This policy reflects the operational checks used around account access and Pakistani payment requests. We separate identity details from routine session signals where practical, restrict internal access according to work needs and...
Access records
Login time, device signals and approximate network details may be recorded to detect suspicious access. These records support account protection and are not treated as a public profile.
Payment matching
JazzCash, Easypaisa, SadaPay and Raast references help us match account requests with transaction status. We do not ask for your wallet password or security code.
Withdrawal checks
A withdrawal may require account and transaction checks before release. We compare relevant records, investigate mismatches and contact you through a verified route when clarification is needed.
Device signals
Browser, operating system, language and device identifiers can help us maintain sessions and diagnose display faults. You can manage some browser permissions, though certain features may then work differently.
Limited access
Only authorised personnel and service partners with a business need should access protected records. We expect suitable safeguards from partners handling technical, payment or support tasks.
Retention review
We keep records for operational, dispute, security and legal needs, then remove or de-identify them when those purposes no longer require identifiable detail.
What This Policy Covers Clearly
The points below make this page easy to compare with our other policy pages without blending their subjects together. Each item states what you can expect from our...
| Collection | We describe the account, technical, communication and transaction details that may reach 999wan when you use our services or contact our team. |
|---|---|
| Purpose | We connect each data category with practical purposes such as access control, payment matching, security checks, support handling and legal compliance. |
| Choice | You may ask about access, correction or deletion, although certain records can remain where security, disputes or legal duties require continued retention. |
| Sharing | We limit disclosures to necessary service partners, authorities where required, and internal personnel whose work requires access to the relevant record. |
| Protection | We use account controls, restricted permissions, verification checks and monitoring practices to reduce the chance of unauthorised access or alteration. |
| Retention | Records are kept according to operational need and applicable requirements, with removal or de-identification considered when identifiable detail is no longer needed. |
| Contact | A clear privacy enquiry should include enough account context for us to locate the record, while excluding passwords, wallet codes and other secret credentials. |
Key Privacy Areas At A Glance
This page layout brings the most useful privacy subjects into view without asking you to search through unrelated account material. The opening section sets the scope...
Clear scope
The opening statement identifies the account, device, transaction and support data covered by this policy, helping you understand its boundaries before reading the detailed wording.
Local context
Pakistani payment references are named directly so you can see how JazzCash, Easypaisa, SadaPay and Raast records may relate to account administration.
Request routes
Dedicated contact guidance separates privacy questions from routine account support and explains what details help us respond without exposing unnecessary secrets.
Security view
The security section describes access records, device signals, withdrawal checks and internal permissions in practical language rather than vague assurances.
Retention view
The page explains why records may remain for operational, dispute, security or legal needs and when removal or de-identification may be considered.
Questions answered
The final questions address common concerns about collection, sharing, payment evidence, account closure, contact changes and requests for access or correction.