LEGAL REFERENCE

Privacy Policy for Your jjj7 Account

jjj7 keeps your privacy terms close to the account flow, so you can see how data is collected, used and protected before you open your account. Read this...

Pakistan account dataConsent controlsSecure access logsPayment record handling
Explore lobby Read FAQ
jjj7 Privacy Policy for Your jjj7 Account

How We Handle Your Account Data

This Privacy Policy explains how we handle data linked to your jjj7 account, including your profile details, sign-in activity, device signals, payment references and messages you send to us. We use this data to open and maintain your account, verify access, process transactions, protect sessions and answer privacy requests. Where access is available in supported regions and where local law permits, Pakistani

payment rails may create transaction references that we store with your account record. We do not ask for more than we need for account operation, security checks and legal record keeping. When another service provider helps us with hosting, verification or payment routing, we require it to handle your data only for the task we assign.

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

CONTACT ROUTES

Contact Us About Your Privacy

You can ask us about this Privacy Policy through the same account paths you use with jjj7. Keep your request clear and include the account email or phone number linked to your profile, so we can locate the record safely.

Team online

Privacy email

Send us your account email, request type and the country linked to access. We check identity before discussing data, so private account records are not exposed through an unverified message.

Live chat handoff

Start in chat when you are signed in and ask for privacy help. Our agent can create a case, confirm basic account markers and move sensitive follow-up to email.

Security escalation

If you think account access or payment references were exposed, contact us quickly. We can lock sessions, check recent sign-ins and explain what data we inspected during the case.

POLICY CHECKS

How We Keep This Policy Current

We treat the Privacy Policy as part of the account experience, not a hidden legal file. Our team checks wording against real jjj7 flows, including sign-in screens, wallet...

Account flow checks

When the account screen asks for a phone number, email or verification step, we align this policy with that request...

Payment record mapping

We map JazzCash, Easypaisa, SadaPay and Raast references to the privacy wording, so transaction IDs, receipts and verification markers are...

Session security checks

Access logs, device signals and failed sign-in attempts are covered because they help protect your account. We keep this wording...

Vendor task control

Hosting, chat and payment providers may process account data for us. We describe those tasks without giving them wider permission...

Retention review cycle

We check retention periods for account records, transaction references and support cases. If a record is no longer needed, we...

Plain English editing

We write the policy in direct Pakistani English and avoid vague legal phrasing where a clearer sentence works. If a...

Consistent Wording Across Our Policy Pages

Your privacy rights should not change from page to page. We align this Privacy Policy with our cookie, terms and account security pages, so the same data categories...

Cookie page alignment
Cookie wording explains browser storage, analytics signals and consent choices. This Privacy Policy connects those items to account privacy without repeating unrelated lobby or game descriptions.
Terms page alignment
Our terms describe account duties and access rules. This policy explains the related data handling, such as verification records, session logs and transaction history linked to your account.
Security page alignment
Security wording covers password care, session checks and suspicious access. This Privacy Policy explains which logs we keep when those controls are used to protect your account.
Support page alignment
Support content tells you where to contact us. This policy explains how your messages, attachments and case history are stored while we respond to privacy or account requests.
Wallet wording alignment
Wallet screens may show Pakistani transaction references. This policy explains how those references are used for reconciliation, fraud checks, record keeping and responses to your privacy questions.
Consent wording alignment
Where a consent prompt appears, we match its wording to this policy. You should see the same purpose, data category and choice language in both places.
Update wording alignment
When we change a privacy term, related pages are checked for matching language. This helps you follow policy changes without reading conflicting account wording.
SCAN FRIENDLY

Privacy Layout You Can Scan

This page is arranged for quick privacy decisions. We place account data, payment records, security logs, sharing rules and contact routes in separate blocks, so you can find...

Account data block The account data block explains profile fields, verification details and...
Transaction record block The transaction block explains how payment references are stored with...
Security log block The security block explains sign-in logs, device clues and session...
Sharing rules block The sharing block lists when service providers may handle account...
Choice controls block The choice block explains how you can ask for access...
Contact block The contact block gives privacy paths for account questions. It...

Privacy Questions Before You Join

We collect the details needed to create and protect your account, such as contact markers, profile fields, sign-in records and verification results. We also store preferences you set inside account controls.

We keep transaction references, receipts and matching records so payments can be reconciled with your account. We do not store more payment data than we need for account operation and checks.

Yes. Contact us from the email or phone linked to your account and explain what needs correction. We may ask for identity checks before changing private account records.

Some providers help us run hosting, chat, verification, security and payment routing. They receive only the data needed for that task and must not use it for unrelated purposes.

Retention depends on the record type. Account history, transaction references, security logs and support cases may have different timeframes due to operation, dispute handling and legal record duties.

We may check sign-in logs, device signals, location clues and recent activity to protect the account. If needed, we can restrict sessions while we verify access with you.