Account data terms
We use the same meaning for account data across privacy, cookies and account terms. That avoids mixed wording when your name, phone number or verification status appears in different records.
p99o keeps your account, device, session and Pakistan payment data under one clear Privacy Policy, so you can see what we collect before you open your account. We...
This Privacy Policy sets out how we collect, store, use and protect data linked to your p99o account in supported regions of Pakistan. We collect details you provide, technical signals from your device, login activity, payment references, support messages and verification records needed to run your account safely. JazzCash, Easypaisa, SadaPay and Raast references are used to match your payment request with
your account history, check irregular activity and respond to support queries. We do not sell your personal data. We share limited records only with service providers, payment processors, security vendors or lawful authorities when a valid request applies. You may ask us to access, correct or delete eligible data, subject to records we must keep for fraud checks, dispute handling, accounting and
legal duties.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
We write this Privacy Policy from the way p99o actually handles account records, payment references, device sessions and support tickets. The wording is checked against internal process changes, so the page stays...
We map each account field to a purpose before it appears in the policy. That keeps collection reasons clear, whether the data comes from account setup, login security or support contact.
Pakistan-specific terms are checked for clarity in en-PK English. We name JazzCash, Easypaisa, SadaPay and Raast directly so you can recognise the payment records involved.
When a local payment flow changes, we check how reference numbers, receipts and verification records are described. The policy then reflects the data trail used for matching and dispute handling.
Security logs help us detect unusual access to your account. The policy explains these logs as privacy records, not as general site features, because they can relate directly to you.
We check how long different record types are needed for payment matching, dispute handling and legal duties. The policy separates routine account data from records that must stay longer.
Policy changes are tracked internally before publication. That gives us a clear trail of what changed, why it changed and which account or payment process it affects.
The Privacy Policy must work with our other legal pages without repeating the same text. We align terms, contact routes and record categories so your rights and our handling duties read the...
We use the same meaning for account data across privacy, cookies and account terms. That avoids mixed wording when your name, phone number or verification status appears in different records.
Cookie and device language stays aligned with this Privacy Policy. If a browser signal supports login security or session performance, we describe that use in matching terms.
Payment references are described consistently across cashier screens and privacy text. JazzCash, Easypaisa, SadaPay and Raast IDs are treated as account-linked records, not casual messages.
Security pages and privacy text share the same approach to login alerts, device checks and suspicious activity flags. We avoid vague labels when a record may identify you.
Support pages point privacy requests back to the same account verification route. This keeps sensitive questions out of the wrong queue and reduces repeated identity checks.
Where another page mentions stored records, we align that statement with this Privacy Policy. Payment disputes, fraud checks and legal requests can require different retention periods.
Any reference to lawful authority requests is kept narrow and consistent. We share data only when the request is valid and relevant to the records involved.
We make privacy content visible where your decisions happen. Account forms, cashier screens, login prompts and support flows point back to this Privacy Policy when they collect or...