Privacy Policy
This page explains what data 99an collects, how we use it, who may process it for us, and how you can ask about access, correction, deletion or restriction where available.
LEGAL REFERENCE
99an Privacy Policy for Pakistan
99an puts your Privacy Policy in front of the account journey, so you can see what data we collect, why we need it, and how it supports access...
Pakistan privacy wordingJazzCash contextEasypaisa contextRaast records
How We Handle Your Data
This Privacy Policy explains how 99an collects, uses, stores and shares data connected with your account, your device, your support chats and your Pakistan transaction records. We use data to create and protect accounts, verify access, process wallet activity, detect abuse, answer privacy requests and meet duties that apply in supported regions. Where local law permits, we may use service partners for
hosting, fraud checks, analytics and payment reconciliation, but we keep their access limited to the task they perform for us. We do not sell your personal data. We keep records only for as long as they are needed for account operation, legal reasons, dispute handling or security checks, then we delete or anonymise them under our internal retention schedule.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
POLICY CARE
How We Keep Privacy Clear
We write this Privacy Policy from the operator side, using the same account, security and support flows you see on 99an. Each change is checked against local access...
Named data categories
We describe account details, device signals, wallet references, chat records and verification material separately, so you can understand which data...
Local wallet context
JazzCash, Easypaisa, SadaPay and Raast appear in this policy only to explain transaction records and reconciliation data. We do not...
Access controls
Internal access to privacy records is limited by role, task and system permission. Support agents see what they need for...
Retention checks
We keep records while they are needed for account operation, legal duties, fraud checks or dispute handling. When a record...
Change tracking
When we adjust this Privacy Policy, we update the wording on this page and align support scripts with the new...
Security signals
We collect login time, device type, IP signals and session behaviour to protect your account from misuse. These signals help...
POLICY MATCH
Consistency Across Policy Pages
Our Privacy Policy sits beside terms, cookie wording and account rules, but it has its own job. This page focuses on personal data, while related pages explain site conditions, cookie choices or...
Cookie wording
Cookie wording explains browser storage, analytics tags and preference tools. It connects with this Privacy Policy because cookies can create device signals, session records and security markers linked with your account.
Terms page
Terms set the rules for account access and site use. The Privacy Policy supports those rules by explaining what data is needed to verify access, respond to disputes and keep records accurate.
Security wording
Security wording explains account protection steps such as passwords, OTP checks and session controls. This Privacy Policy explains the related data records and why those signals are collected by 99an.
Wallet records
Wallet wording explains transaction flow, while this policy explains the personal data around that flow. That includes wallet references, timestamps, reconciliation status and support messages about Pakistan payment rails.
Support scripts
Support scripts use the same privacy language you see here, so agents do not ask for unnecessary details. If a request needs escalation, the privacy wording stays consistent across the handover.
Account notices
Account alerts may refer you back to this page when data handling matters. That keeps privacy explanations in one place instead of scattering different wording across popups and chat replies.
Visible Privacy Cues Across 99an
We place privacy cues where they help you make account decisions: before you share details, when cookies appear, and when support asks for verification. These visible...
Clear account forms
Registration fields are kept focused on account creation, access checks and contact needs. When a field is required, we aim to make its purpose clear before you submit the form.
Cookie control area
Cookie prompts explain browser storage used for sessions, preferences, analytics and security. You can make choices where controls are available, and those choices connect with the wider privacy wording here.
Session alerts
If our systems detect unusual account access, we may show alerts or request checks. The related privacy records can include login time, device details, IP signals and recent account activity.
Profile edit points
Your profile area lets you check key account details and request correction if something is wrong. We may need verification before changing data that affects security or transaction history.
Support privacy prompts
When support handles a privacy matter, prompts remind agents not to ask for OTP codes, full wallet credentials or unrelated documents. This reduces unnecessary exposure during chat and email contact.
Policy date marker
This page carries a visible update marker so you can see when the wording changed. Major changes may also appear through account messages or site banners where appropriate.
Privacy Policy Questions Answered
We collect account details you provide, login and device signals, wallet references, support messages and verification material when needed. We use these records to run your account, protect access and answer privacy requests.
We keep wallet references to reconcile account activity, resolve disputes and meet record duties in supported regions. These records may include timestamps, transaction status, account ID links and support messages about the transaction.
Yes, you can ask us to correct inaccurate account details through support or the account area. We may verify your identity first, especially where the change affects access, wallet history or security records.
We use service partners for hosting, analytics, fraud checks, support tools and payment reconciliation. Their access is limited to the task we give them, and they must handle the records under agreed controls.
We keep records for as long as needed for account operation, security, legal duties, disputes or transaction reconciliation. After that period, records are deleted or anonymised under our retention process.
Cookies can store session status, preferences, analytics signals and security markers. This Privacy Policy explains how those signals may connect with your account, while cookie controls explain the browser choices available.
Use the account help area for requests tied to your profile, access logs or wallet records. For detailed matters, email the privacy desk and include your account ID without sending OTP codes.