Privacy Policy for your j99 account
j99 keeps your account data, payment checks and device signals tied to clear privacy purposes, so you know why each detail is asked for before you open an...
How our privacy terms apply
This Privacy Policy explains how j99 handles data when you create an account, verify access, move through the lobby, contact support or use Pakistan payment rails where local law permits. We collect only the details needed to run your account flow, check transactions, protect sessions and answer privacy requests. Some data comes from you, such as name, phone, email and payment reference
details. Other data is created by your device, browser, app session, IP range and security logs. We may share limited data with payment processors, verification partners, hosting vendors and support tools when that access is needed for the service you requested. We keep internal access restricted by role and retain records only for account, legal, security and dispute needs.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Contact paths for privacy requests
If you want to ask about account data, corrections, transaction records or access logs, start from the contact route that matches your request. We may ask you to confirm account ownership before discussing private records. That check protects your account from third-party access.
In-account support
Use the help area after login when your privacy request relates to a live account. We can match your message to account records faster and avoid asking you to repeat payment references.
Email privacy desk
Send a clear request by email if you need a written trail for data access, correction or deletion questions. Include your registered contact detail, but never send passwords or full wallet PINs.
Payment query route
For privacy questions linked to JazzCash, Easypaisa, SadaPay or Raast checks, include the transaction time and masked reference. We use those details only to trace the related account record.
How we keep this policy accurate
Our privacy text is maintained by the team that runs account access, payments, security and support. When a flow changes, we check whether the policy still matches what happens on j99. That...
Product sign-off
Account, wallet and support changes are checked against this policy before the wording is updated. We look at what data is collected, why it is needed and who can access it.
Security input
Our security team reviews session logs, device signals and risk checks described here, so the policy reflects how we protect account access without exposing methods that could weaken security.
Payment mapping
We map each Pakistan payment rail to the data it creates, such as masked references, status codes and timing. That helps us explain wallet-related records without asking for sensitive wallet secrets.
Plain wording
We write privacy terms in direct English for Pakistan readers, avoiding legal fog where possible. When a legal phrase is necessary, we link it to a practical account or support example.
Request tracking
Privacy requests are logged with time, channel and outcome so we can answer consistently. Access to that log is limited to staff who need it for account service or compliance work.
Update records
When this policy changes, we keep the prior version internally with the change reason. That record helps us explain what applied when an older privacy question or dispute is raised.
How this policy connects across j99
This page sits beside our account, cookie and terms pages. Each page has a different job, but they should not conflict. If a privacy point affects another policy...
| Account terms | Account terms explain eligibility, access and use rules, while this policy explains the data handled during those steps. Together they show what we ask from you and why it matters. |
|---|---|
| Cookie notice | The cookie page covers browser storage and tracking choices in more detail. This Privacy Policy points to the same device signals when those signals support login, security or performance checks. |
| Payment rules | Payment wording explains transaction handling, while this policy explains related records such as wallet references, verification status and support messages. We keep financial data details limited to what the account flow needs. |
| Security terms | Security wording covers login protection and account controls. This policy adds the privacy angle by naming the log data, device markers and access checks used to protect your account. |
| Support standards | Support terms describe how we answer account questions. This policy explains what support staff may view, when identity checks are needed and how privacy requests are recorded. |
| Regional access | Access wording may differ by supported regions and local law. This policy uses the same regional approach when explaining data handling, verification and account availability for Pakistan. |
| Policy updates | Update wording appears across legal pages so changes are easy to spot. This page focuses on privacy changes, including data purposes, sharing partners and request routes. |
Privacy page elements you can use
We design this page so privacy details are easy to scan before you create or manage an account. The layout separates collection, use, sharing, storage and...
Scope panel
The scope panel explains where the policy applies, including account creation, login, support and payment checks. It sets expectations before you reach more detailed wording about records and partners.
Data purpose blocks
Purpose blocks connect each data type to a reason, such as account access, transaction tracing or security checks. This helps you see why a detail is collected rather than just naming it.
Local context chips
Short chips name JazzCash, Easypaisa, SadaPay and Raast only where payment privacy context is needed. They remind you which Pakistan rails may create transaction records inside your account.
Request path cards
Contact cards separate account access questions from written privacy requests and payment-linked privacy queries. That split helps your message reach the right team with less back-and-forth.
Retention wording
Retention text explains why some records must remain for account, legal, security or dispute needs. We avoid vague storage claims and tie retention to practical account operations.
Change marker
A change marker is used when policy wording is adjusted after account, security or support flows change. It helps you understand whether a privacy point is current for your request.