Privacy Policy
This page explains which data we collect from your account, device, session, and payment activity. It also explains why we use that data and how you can raise a privacy request.
LEGAL REFERENCE
How 7jj Handles Your Privacy
7jj puts account privacy, payment records and security checks in plain language before you open your account. This Privacy Policy explains what we collect, why we need it...
Pakistan data careAccount privacy choicesSecurity-first accessClear contact routes
Privacy Terms For Pakistan Accounts
This Privacy Policy applies when you use 7jj in supported regions, create an account, verify access, browse our lobby, or connect a Pakistan payment rail. We collect account details you provide, device signals needed for security, transaction references, service messages, and records created when you use privacy or account settings. We use this data to operate access, confirm identity, protect balances, process
requests, maintain service integrity, and meet duties that apply where local law permits. We do not ask you to send unnecessary documents in open chat, and we restrict internal access to staff who need the record for a clear purpose. If a third-party service helps us with hosting, security checks, analytics, or payments, we share only the data needed for that task
and require careful handling.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
POLICY ASSURANCE
How We Keep Policy Work Accountable
Our Privacy Policy is kept as an operating document, not a page we forget. We check wording when our account screens, payment partners, or security tools change, and...
Internal ownership
A named internal role owns privacy wording at 7jj, so edits do not drift between product, payment, and support teams...
Change checks
When we add a payment rail, security screen, or account setting, we check whether the Privacy Policy needs fresh wording...
Access control
Your identity files, transaction references, and chat records are not open to every staff member. We assign role-based access, log...
Data minimisation
We ask for the least data needed to run your account, verify a request, or complete a privacy response. Extra...
Pakistan context
Our policy names JazzCash, Easypaisa, SadaPay and Raast because those records have real privacy impact for you. Payment references are...
Readable drafting
We write privacy terms in clear Pakistani English and avoid legal clutter where a simple phrase works. You should be...
CONSISTENT WORDING
Aligned Privacy Terms Across 7jj Pages
7jj policy pages must work together, so we use matching terms for account data, cookies, payments, and security checks. This Privacy Policy explains collection and use; related pages handle rules for account...
Terms page
Our terms page may describe account conduct and service use, but it relies on this Privacy Policy for data handling. If privacy wording differs, we correct the page that needs alignment.
Cookie section
Cookie wording sits inside the privacy framework because device identifiers can affect security, login continuity, and service measurement. We explain the categories without burying them in unrelated site text.
Payment text
Payment pages may mention JazzCash, Easypaisa, SadaPay or Raast for account funding paths, while this policy explains the data traces behind those actions and how long records may remain.
Security pages
Security content explains how you protect access; this policy explains how we handle security data. Login timestamps, device checks, and risk flags are covered here as personal data.
Promo board
If our promo board uses account activity to show eligible offers, this policy explains that data use. We keep preference choices and service messages separate where the account screen allows.
Support help
Support content tells you where to ask for help; this policy explains what happens to the data inside that request. We keep privacy escalation paths clear for sensitive account matters.
Policy Cues Built Into The Page
The privacy page is designed to be usable, not hidden behind dense legal blocks. We place account rights, data categories, contact paths, and Pakistan payment references...
Short badges
The badges near the hero summarise privacy themes such as account data, security access, and Pakistan payment records. They help you see the scope before reading the full policy text.
Plain labels
We use labels like account data, device signals, payment references, and support records instead of vague legal wording. Each label connects to an action you recognise inside 7jj.
Local chips
JazzCash, Easypaisa, SadaPay and Raast appear as context chips because payment references are personal data. The chips remind you which records may link back to your account.
Contact cards
The contact cards separate email, chat, and urgent security messages. That layout reduces the risk of sending sensitive data through the wrong channel when you need a privacy response.
Rights language
We state that you can ask about access, correction, and deletion where local law permits. The wording stays practical, so you know what to send and why checks may apply.
Update cues
Policy updates are handled through clear page edits rather than buried phrasing. When a privacy change affects how your data is used, we aim to make the change visible.
Privacy Questions From 7jj Accounts
We collect details you provide, such as your mobile number, account credentials, identity checks where required, device data, session logs, and payment references. We use them for access, security, service operation, and privacy requests.
Those Pakistan payment rails can create account-linked records, including reference IDs, status updates, timing, and support messages. Our Privacy Policy explains how those records are used, protected, and kept separate from general browsing data.
Yes, you can ask us to correct account data that is inaccurate or incomplete. We may verify your identity first, especially if the change affects login access, payment records, or security history.
We use cookies and device signals to keep sessions stable, protect login access, measure service performance, and detect unusual activity. Where choices are available, your account or browser settings may let you adjust them.
We may share limited data with services that help operate hosting, security checks, analytics, customer contact, or payment processing. Each share must connect to a service need, privacy duty, or lawful request.
Retention depends on the record type, such as account access, payment reference, security event, or support message. We keep data only as needed for service, dispute handling, safety checks, or legal duties.