Cookie statement
The cookie statement uses the same device language as this Privacy Policy. That makes browser identifiers, session logs and preference records easier to connect with your account choices.
LEGAL REFERENCE
Privacy Policy for your 9ppp account
9ppp keeps privacy controls close to your account flow: sign-up details, device checks, payment records and support messages are handled under one clear Privacy Policy for Pakistan access...
Account dataDevice checksPakistan payment recordsSupport messages
How we handle privacy in Pakistan
Our Privacy Policy explains how 9ppp handles personal data when you create an account, confirm access, contact support or use Pakistan payment rails. Where local law permits, we collect only what we need for account set-up, identity checks, account safety, transaction tracing, fraud screening, service messages and privacy requests. We do not sell your personal data. Limited details may be shared with
payment processors, technical service providers, verification partners or authorities when required for lawful handling, dispute checks or account protection. JazzCash, Easypaisa, SadaPay and Raast records may include names, masked account references, timestamps and amounts. We keep those records only for operating, legal and security reasons, then restrict or remove them when retention no longer applies.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
POLICY CARE
How we keep this policy reliable
We write this Privacy Policy from the systems we operate, not from abstract wording. The policy connects account creation, payment records, support messages, device signals and verification checks...
Policy owner
A named internal owner keeps the Privacy Policy aligned with account, payment and support flows. That person checks wording with...
Local payment context
We reference JazzCash, Easypaisa, SadaPay and Raast because these records carry privacy impact in Pakistan. The policy explains what can...
Access checks
Privacy requests are matched against account identifiers before we release or change data. This prevents another person from using a...
Sharing limits
The policy separates service partners from broader third parties. We describe when processors, verification services or authorities may receive limited...
Retention map
We link record retention to clear reasons such as account operation, dispute handling, finance checks and legal duties. When a...
Change record
When the Privacy Policy changes, we keep the update tied to the date and reason. That helps you see whether...
POLICY MATCH
Aligned wording across policy pages
Your privacy rights should not change because you moved from one legal page to another. We keep this Privacy Policy aligned with our cookie statement, account terms, promotion terms, security wording and...
Account terms
The account terms explain your account duties, while this Privacy Policy explains data handling. We keep both pages aligned where identity checks, contact details and access security overlap.
Offer terms
Offer terms point back to this Privacy Policy when account eligibility checks use contact details or transaction history. We keep the wording narrow so extra data is not implied.
Security wording
Security wording explains how we protect access, while the Privacy Policy explains what data supports that protection. Device signals, login times and alerts are treated consistently.
Support rules
Support rules explain how we answer you, but this Privacy Policy explains how messages are stored. We align both so chat records, attachments and contact history are handled clearly.
Payout checks
Payout check wording connects to this Privacy Policy where identity, bank reference or mobile wallet records are used. We state the privacy reason before asking for extra evidence.
Regional access
Regional access wording uses the same phrase where local law permits. That keeps privacy statements consistent for Pakistan access and prevents wider claims about unsupported regions.
Privacy cues you can see
We do not hide privacy handling in a long legal block only. Across the 9ppp account flow, we add short cues beside forms, verification steps and...
Form labels
Sign-up fields show short labels for contact, access and verification data. Those labels help you connect each field with the Privacy Policy before you submit account details.
Consent cues
Where we ask for a choice, the page shows the purpose in plain language. This keeps marketing messages, service alerts and privacy requests separated in your account settings.
Data purpose tags
Account areas use purpose tags for identity, security, payment records and support history. The tags make it easier to understand why data exists before you ask to change it.
Session prompts
Device and session prompts explain when we use browser, app or location signals for account protection. The Privacy Policy gives the fuller wording behind those prompts.
Request trail
When you send a privacy request, we keep a limited trail of the request and response. That trail helps us prove handling without keeping unnecessary attachments forever.
Regional wording
Pakistan-facing pages use the same regional phrasing as this Privacy Policy. That makes access, payment record handling and support routing clearer for your local account context.
Privacy questions before you join
We collect details needed to create and protect your account, such as contact data, login credentials, device signals and verification records. The Privacy Policy explains each purpose before we use that data.
Payment records can include sender names, masked wallet references, timestamps and amounts. We mention JazzCash, Easypaisa, SadaPay and Raast so you understand what local records may be stored.
Yes. Send a correction request through your account or our privacy form. We may verify account ownership first, then update records we control or explain why a record must remain.
Retention depends on the record and legal reason. Account, payment and support records may be kept for operation, disputes, security checks or legal duties, then restricted or removed when no longer needed.
We share limited data when a partner helps run account access, verification, payments, hosting, security or support. The Privacy Policy limits that sharing to the service purpose and required records.
Device checks help detect unusual access and protect your account. They may use browser type, app session data, login time and technical identifiers, with handling explained in this Privacy Policy.