Privacy choices inside 988 wan
988 wan gives you a clear privacy path before you open an account: what we collect, why we need it, and how your Pakistan payment records are handled...
How our privacy stance works
Our privacy posture is built around account accuracy, fraud checks, local payment reconciliation, and service communication in supported regions where local law permits. We collect only the details needed to create your account, confirm access, process requests, verify withdrawals, and keep the lobby running safely. When you use JazzCash, Easypaisa, SadaPay, or Raast, we may store transaction references, timestamps, status changes, and
account identifiers so your balance history can be matched without exposing unnecessary financial data. We also use device signals, IP location, and session logs to protect your account from unauthorised access. This policy explains those uses in plain Pakistani English and tells you how to ask for correction, access, or removal where applicable.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Reach us about your privacy
Privacy questions need a clear route, not a maze. We keep account, payment, and security queries separated so your request reaches the people who can check the correct records. When you contact us, include your account ID and the date of the privacy concern; do not send passwords, card images, or unrelated documents.
Privacy inbox
Our privacy email route is for access, correction, deletion, and consent questions. We match your message to account records, then reply with the next action we can take under local requirements.
Live chat check
Chat can confirm which privacy path fits your issue before deeper checks begin. Our agents may ask for account ID, registered mobile, and a short description, but not your password.
Security escalation
If you suspect account access by another person, we move the privacy request to security handling. Session logs, device changes, and payment references help us limit further exposure.
How we keep this policy current
Your privacy policy should not feel copied from another site. Our internal team checks this page against the way 988 wan actually collects account data, stores verification records, and handles Pakistan payment...
Process ownership
Each privacy clause is linked to an active account process, such as verification, login security, support history, or withdrawal checking. That keeps the wording connected to how your data is handled.
Plain language
We write this policy in clear Pakistani English so you can understand what is collected, why it is needed, and how to contact us without legal wording getting in the way.
Local payment context
Where Pakistan rails are involved, we name the relevant record types, including transaction references, wallet names, timing, and status changes. We do not ask you to share unrelated wallet secrets.
Access control
Privacy records are visible only to staff roles that need them for account support, verification, fraud checks, or compliance queries. Access is logged so unusual handling can be checked.
Change tracking
When we adjust this policy, we keep the wording aligned with active forms, account screens, and support scripts. That helps you understand current practice rather than old phrasing.
Data retention
Some records must stay for dispute handling, tax, security, or transaction matching. We set retention periods by data purpose, then remove or anonymise records when they are no longer needed.
Privacy wording across our pages
Privacy wording appears beside other account terms across 988 wan, but this page stays focused on personal data. The comparison below explains how we keep each policy area...
| Account terms | Terms explain account rules and service conditions. This Privacy Policy explains the personal data used to apply those rules, such as identity checks, contact records, and login evidence. |
|---|---|
| Cookie page | Cookie wording covers browser storage and similar tools. This page explains the wider privacy picture, including account details, transaction records, support messages, and security logs linked to you. |
| Offer terms | Offer terms describe eligibility and reward rules. This policy covers the data used to show, track, or withhold account offers, including region, device, and account status where needed. |
| Support records | Support pages explain how to reach us. This policy explains what we retain from those contacts, including message content, attachments you choose to send, and resolution history afterwards. |
| Security rules | Security wording covers account protection expectations. This privacy page explains the logs behind those checks, such as IP location, device fingerprints, failed login attempts, and session timing patterns. |
| Payment records | Wallet instructions show how transfers work. This policy explains the personal and transaction data attached to JazzCash, Easypaisa, SadaPay, and Raast reconciliation inside your account and balance records. |
| Regional access | Access wording may mention supported regions where local law permits. This policy explains how location signals are used for availability checks, account safety, and fraud monitoring before we store them. |
Visible privacy cues on this page
This page is laid out so privacy cues are easy to spot while you decide whether to join. We use short badges, labelled sections, and contact...
Badge row
The hero badges summarise collection, storage, and contact rights before the longer policy text begins. They are written as quick privacy markers, not as broad brand slogans here.
Section labels
Each label points to a privacy purpose, such as data use, contact routes, policy care, or your questions. The labels help you scan without changing the meaning of the policy.
Contact cards
The contact cards separate privacy access, chat sorting, and security escalation. That structure reduces back-and-forth because your request starts closer to the team that can act on it.
Policy signals
Security and retention cards explain why we keep certain records and who may view them. They give you context before you send an account change or privacy request to us.
FAQ placement
The question block turns common privacy doubts into direct answers. It covers access, correction, payment receipts, device logs, and account closure requests in one readable area for you.
Mobile reading
The layout keeps paragraphs short for phone screens, so you can read the policy on mobile before sharing account details, identity documents, or wallet references with our team.