LEGAL REFERENCE

Privacy Policy for your 99jj account

99jj keeps your account privacy clear: we collect the data needed to open your account, protect access, process checks and respond to your requests. Read this Privacy Policy...

Account data usePakistan privacy contextSecurity checksSupport contact paths
99jj Privacy Policy for your 99jj account

How our privacy stance works

Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.

CONTACT PATHS

How to reach us about privacy

Privacy questions should come through channels that let us verify your account safely before sharing account-related data. We may ask for a matching mobile number, email address, recent login clue or wallet reference before we act. This helps us avoid sending private account details to the wrong person.

Team online

Live chat privacy route

Use live chat for privacy access questions, correction requests or account-data concerns. We first confirm your account link, then move sensitive cases to a private support thread.

Email request channel

Send privacy requests by email when you need a written record. Include your account phone or email, but never send passwords, full wallet codes or card-style secrets.

Security escalation

If you suspect account access without permission, contact us quickly. We can freeze sensitive changes, check login traces and explain what personal data may need securing.

CARE CHECKS

Privacy checks behind this policy

We write this Privacy Policy from the way 99jj actually handles account records, verification queues and support replies. Our privacy wording is checked against our signup flow, wallet reference screens and access...

Account flow match

We check this policy against the fields you see during account opening, login recovery and profile edits, so the privacy wording reflects actual data collection points.

Wallet reference care

JazzCash, Easypaisa, SadaPay and Raast references are treated as account-service data. We keep only the context needed to match requests, checks and records.

Access control checks

Our team access is role-based, meaning support and operations staff see data tied to their task rather than every field stored on your account.

Retention review

We keep privacy records for as long as account, security, dispute or legal reasons require, then remove or reduce data when continued storage is not needed.

Device signal use

Device and login signals help us detect suspicious access, repeated failed attempts and session risk. These checks protect privacy by limiting account misuse.

Policy update checks

When our account screens, support tools or wallet handling changes, we check whether this Privacy Policy needs clearer wording before the new flow stays live.

How this policy aligns with others

This Privacy Policy sits beside our terms, cookie wording, account rules and verification pages. Each page has a different purpose, but the privacy meanings stay aligned. If another...

Terms page linkOur terms explain account rules, while this Privacy Policy explains the personal data used to apply those rules, handle requests and protect account access.
Cookie wording linkCookie wording covers browser storage and preference tools. This Privacy Policy explains how those signals may connect to sessions, security checks and analytics.
Verification page linkVerification pages ask for proof when account safety or lawful handling requires it. This policy explains how those checks are stored and restricted.
Wallet page linkWallet screens show payment rail choices, while this Privacy Policy explains how reference numbers, status checks and support messages are handled.
Support page linkSupport pages help you contact us. This policy explains why support messages, timestamps and identity clues may be retained after a case closes.
Security page linkSecurity wording explains access protection. This Privacy Policy explains the login data, device signals and alerts used to make those protections work.
Promo page linkIf a promo screen asks for account status, this policy explains how eligibility data is checked without exposing more account data than needed.
PRIVACY LAYOUT

Privacy cues across the page

We design the Privacy Policy page so you can find the parts that affect your account quickly. The layout separates collection, use, sharing, retention and request rights. That...

Clear section labels Each privacy section uses plain headings so you can separate...
Local context chips Pakistan payment chips appear only as data-context markers, showing where...
Request wording Access, correction and removal requests are written as direct actions...
Sharing boundaries The sharing section separates service providers, lawful requests and safety...
Retention markers Retention wording explains why some records stay for disputes, security...
Update date area A policy update area helps you see when privacy wording...

Privacy Policy questions answered

We collect data needed for account opening, access, verification, wallet reference checks, security logs and support replies. This may include your name, contact details, device signals and account activity records.

Wallet references from JazzCash, Easypaisa, SadaPay or Raast help us match account requests, resolve disputes and check transaction status. We use this context for account handling, not resale.

Yes, you can ask us to correct eligible account data. We may verify your identity first and may retain records that are needed for security, disputes or lawful duties.

We share limited data only when needed for hosting, verification, security checks, analytics, payment routing, support handling or lawful requests. Service partners must handle the data for assigned tasks.

Retention depends on the data type and purpose. Security logs, support cases and wallet reference records may stay while account, dispute or lawful reasons still apply.

Contact us through live chat or email with your account phone or email. We verify the request before discussing personal data, changing records or handling removal requests.