LEGAL REFERENCE

Privacy Policy for one jj Accounts

one jj keeps your account, device, identity and Pakistani payment records under one privacy policy, so you know what we collect before you open an account. We explain...

Pakistan privacy scopeJazzCash data checksEasypaisa receipt recordsSadaPay and Raast context
one jj Privacy Policy for one jj Accounts

How We Handle Your Data

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

PRIVACY HELP

Reach Us About Privacy

Your privacy questions should reach the team that can act on them. We separate general account help from privacy requests so access, correction, deletion and consent queries are handled with the right checks. Before changing or sharing account data, we may ask for identity proof linked to your one jj account and Pakistani mobile number.

Team online

Email privacy request

Send a privacy request from the email linked to your account. Include your mobile number, the request type and any payment reference only when it helps us locate the data.

Live chat privacy queue

Use chat for time-sensitive privacy concerns such as wrong account data or a receipt attached to the wrong profile. We verify you before discussing personal records.

Account centre request

Inside your account, privacy messages carry your account ID automatically. That helps us confirm ownership faster while keeping replies away from shared phones or open inboxes.

POLICY CHECKS

How We Keep Policy Wording Current

We write this policy from our own account flow rather than copying generic clauses. The wording is checked against how our sign-in screens, payment receipts, withdrawal checks, cookies and support tools actually...

Policy owner

A named internal owner keeps the Privacy Policy tied to our real account flow, including sign-in records, identity checks, payment references, support cases and cookie choices.

Plain English wording

We keep legal phrasing short enough for normal account decisions. You should see what data is collected, why it is used and how to contact us.

Local rail mapping

Payment privacy clauses mention JazzCash, Easypaisa, SadaPay and Raast because those references may appear in receipts, sender matches, withdrawal checks and support cases.

Access controls

Only authorised staff can open privacy-linked account records. Access is logged, role-based and limited to work such as verification, support response or fraud investigation.

Change record

When privacy wording changes, we keep a dated record of the section adjusted. That helps you see whether collection, use or retention wording has moved.

Cookie checks

Cookie language is matched with the scripts we run for security, session handling and measurement. If a cookie purpose changes, the policy wording follows.

CONSISTENT RIGHTS

Same Privacy Rights Across Pages

Your privacy rights should not change depending on which legal page you open. We keep this policy aligned with account terms, cookie wording, contact forms and security language, so requests about access...

01

Privacy Policy

This page explains the full privacy scope: data collection, lawful use, storage, sharing, security controls, retention periods and your choices for account records.

02

Terms page

Our terms may describe account rules, but personal data handling points back here. That prevents conflicting wording about identity checks, payment references or support records.

03

Cookie page

Cookie wording stays connected to this policy. Session cookies, security checks and preference settings are described consistently, without changing your broader privacy rights.

04

Security page

Security language covers account protection, while this policy explains the related data handling. Login alerts, device signals and access logs are treated consistently.

05

Contact page

Contact forms collect only the details needed to answer you. If your message is a privacy request, it moves into our privacy handling process.

06

Payment privacy

Payment references from JazzCash, Easypaisa, SadaPay and Raast are used for matching, verification and dispute handling, not for unrelated profiling or sale.

07

Promo board

If you choose to view account offers, related privacy wording still applies. We keep preference and eligibility data connected to your account choices.

PAGE MARKERS

Privacy Layout You Can Read Quickly

This policy is arranged so you can find the privacy point you need without digging through unrelated text. The page uses plain headings, short labels and visible contact...

Version banner A visible date tells you when the policy wording last...
Data category blocks Personal details, device records, payment references and support messages are...
Purpose labels Each data category is paired with a purpose label, such...
Choice links Links for access, correction and deletion requests sit near the...
Retention panels Retention wording explains why some records stay longer than others...
Contact card The privacy contact card gathers email, chat and account-centre routes...

Privacy Policy Questions for Pakistan

We collect data needed for account access, security and transaction matching, such as name, mobile number, login records, device signals, identity checks, payment references and support messages.

We keep payment references to match your account, confirm sender details, answer disputes and verify withdrawals. We do not use JazzCash or Easypaisa receipt data for unrelated sale.

Yes. Send an access request through email, chat or the account centre. We verify your identity first, then provide the account data we can lawfully share.

Contact us with the corrected detail and proof linked to your account. We update records when the request is verified and no legal record rule prevents the change.

Retention depends on the record type. Account, payment and security records may stay longer for verification, disputes, fraud checks, audit needs and legal duties.

We share data only when needed for account operation, payment checks, security tools, support handling or legal requirements. Any partner access is limited to the assigned task.