How 7jjj Handles Your Privacy
7jjj sets out this Privacy Policy so you know what account, device, location and transaction data we collect before you open an account. We explain how privacy works...
Our Privacy Position For Pakistan
This Privacy Policy describes how 7jjj collects, uses, stores and shares personal data linked to your account in supported regions of Pakistan. We collect details you give us during account creation, security checks, support chats and payout handling, plus technical records such as device type, IP address, browser data and session activity. Where local law permits, we use this data to keep
your account accessible, process transactions, check unusual activity, answer support requests and meet record keeping duties. We do not sell your personal data. Limited data may be shared with service partners that help with verification, hosting, security monitoring, payment routing and customer support, under confidentiality controls.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Privacy Contact Paths At 7jjj
If you have a privacy question, we want the route to be clear before you send account details. Use the same contact name and account reference across messages so we can connect your request correctly. We may ask for identity checks before releasing, changing or closing data tied to your account.
Live chat privacy queue
Use live chat for quick privacy requests linked to account access, device changes or payout checks. Our team may move the case to email if documents or longer written confirmation are needed.
Email data requests
Email support when you need a written record of a privacy request, such as data access, correction or deletion where permitted. Include your account ID and avoid sending card images unless asked.
Security escalation
Contact us at once if your account privacy may be at risk through a lost phone, shared password or unfamiliar login. We can lock access while ownership checks are completed.
How We Keep Privacy Accurate
Our privacy wording is maintained by people who handle account flows, support cases and payout checks for 7jjj. The policy is checked when we adjust verification steps, add security tools or change...
Operational checks
We compare policy wording with real account steps, including login checks, document requests and payout verification. If a workflow changes, the privacy language is updated to match the data we request.
Regional wording
We write for Pakistan access in supported regions and use plain local English. That means privacy terms, payment references and support routes are described in a way you can act on.
Security alignment
Privacy controls are connected with password handling, session checks and unusual activity alerts. We limit internal access so staff see only the data needed for their assigned task.
Payment references
JazzCash, Easypaisa, SadaPay and Raast records are treated as transaction data, not public profile content. We use them for routing, reconciliation, support tracing and required account checks.
Document handling
When identity documents are needed, we request them through controlled support routes. Files are used for verification, stored with restricted access and kept only as long as required.
Clear change log
When the Privacy Policy changes, we refresh the visible date and adjust related page wording. You can return here before opening or continuing your account activity.
Consistency Across Our Privacy Pages
This page sits beside our account terms, cookie wording and contact routes. Each page has a separate role, but the privacy language remains aligned. When we explain data...
| Account terms | Our account terms explain your relationship with 7jjj, while this Privacy Policy explains how personal data supports that relationship. The two pages are checked for matching account and verification wording. |
|---|---|
| Cookie wording | Cookie language focuses on browser storage, analytics signals and session continuity. This Privacy Policy connects those technical signals to broader account privacy, security checks and support handling. |
| Support page | The support page tells you where to contact us. This policy explains what data support may request, why identity checks can be needed and how privacy requests are logged. |
| Payment screens | Payment screens collect transaction details for JazzCash, Easypaisa, SadaPay and Raast. This policy explains how those details are stored, verified and shared only with relevant service partners. |
| Security prompts | Login prompts and device checks help protect account privacy. This page explains the data behind those prompts, including IP signals, session records and unusual access checks. |
| Promo board | If the promo board uses account activity to decide what you can see, this policy covers that data use. We aim to keep any account-based display clearly explained. |
| Update banners | When policy wording changes, a visible update banner may point you back to this page. That keeps privacy changes easy to find before you continue account activity. |
Visible Cues In This Policy
We arrange this Privacy Policy so you can scan the parts that affect your account first. The layout separates collection, use, sharing, retention and contact routes...
Effective date
A visible date tells you when this Privacy Policy was last changed. If we update data handling, the date helps you decide whether to read the policy again.
Data categories
We separate account details, device records, transaction references and support messages. This makes it easier to see which privacy rules apply to each type of data.
Use purposes
Each main data use is tied to a reason, such as account access, security checks, payout processing or support replies. We avoid vague wording where a clearer reason exists.
Sharing limits
Partner sharing is described by purpose, not broad permission. Hosting, verification, payment routing and security monitoring are separated so you can see why data may leave 7jjj systems.
Retention markers
Retention wording explains that records are not kept forever by default. Time frames depend on account activity, legal duties, dispute handling and security needs.
Request routes
Contact routes are placed near the policy content so you do not need to search elsewhere. We state when identity checks may be required before privacy requests are completed.