LEGAL REFERENCE

th 7 Privacy Policy for Pakistan

th 7 explains exactly how we collect, use, store and protect the data tied to your account, device, wallet activity and support chats. Before you open your account...

Account data purposeWallet record handlingPakistan contact pathsClear retention rules
th 7 th 7 Privacy Policy for Pakistan

How we handle your data

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

PRIVACY CONTACTS

Ways to contact our privacy team

Privacy questions need a clear route, not a generic reply queue. We give you separate contact paths for access requests, correction requests, deletion requests and account-security concerns, then match your request to the account details you provide before taking action.

Team online

Privacy inbox

Use [email protected] when you want access, correction, or deletion help. Include your account email and phone number so we can match the request without asking for extra data.

Chat handoff

If you ask through chat, our team moves privacy matters to a secure ticket. We never ask for full wallet PINs, card secrets, or one-time codes there.

Account security

For login or device concerns, contact support and mention privacy in the subject. We check recent access records before changing data or closing a request.

DATA CARE

Signals behind this privacy policy

Our Privacy Policy is written from the way th 7 actually operates. We describe account checks, wallet references, security logging and support handling in practical terms, so you know what happens to...

Named purposes

Each data category is linked to a clear purpose, such as account access, wallet records, fraud checks, support replies or legal duties. We avoid collecting data without an operational need.

Access control

Only trained team roles can view sensitive account records. Support can see enough to help you, while wallet and verification details stay restricted to authorised operational queues.

Local wallet context

JazzCash, Easypaisa, SadaPay and Raast references are stored as transaction records, not open wallet access. We use them to trace requests and resolve mismatched account details.

Device protection

We log device and session signals to spot unusual access. These records help us secure your account, investigate disputes and reduce unauthorised activity across supported regions.

Identity checks

When privacy rights are requested, we verify that the request belongs to you. This protects your account from another person asking for changes or copies of data.

Retention control

We keep records only for operational, dispute, security and legal timelines. When a record is no longer needed, we remove it or separate it from direct account identity.

POLICY LINKS

How our policies stay aligned

This page connects with other th 7 legal pages, but it has one job: explain privacy. Where another page explains account use, cookies or payments, this page explains the personal data behind...

01

Terms page

Our Terms explain account rules, while this Privacy Policy explains the data used to run those rules. If a rule needs verification, we state the data purpose here.

02

Cookie page

Cookie wording covers browser storage and similar tools. This Privacy Policy connects those tools to session security, preferences and analytics that help us maintain account access.

03

Account rules

When you update your profile, we separate the account change from the privacy record. The policy explains what is kept, why it is kept and who can access it.

04

Wallet records

Wallet pages describe transaction steps. This policy explains how JazzCash, Easypaisa, SadaPay and Raast references are stored, matched and used for support or dispute checks.

05

Security page

Security wording explains protection controls. The Privacy Policy explains the personal data behind those controls, including login signals, device identifiers and unusual access checks.

06

Contact page

The contact page routes common questions. Privacy requests follow stricter identity checks, because access, correction and deletion actions can affect your account records.

07

Regional access

Where local law permits, we use regional signals to manage availability and compliance tasks. This policy explains what those signals are and how long we keep them.

PAGE MARKERS

Policy layout you can scan

We structure this Privacy Policy so you can find the part that affects your account without reading unrelated material first. Each visible marker points to a specific privacy...

Purpose labels Every major data category is paired with a purpose label...
Plain sections We avoid legal clutter where a direct sentence works. The...
Local examples Pakistan wallet names appear only where they explain data records...
Request routes Access, correction and deletion paths are separated from common support...
Security markers Security references explain login logs, device checks and restricted staff...
Update dates When this policy changes, we show the effective date near...

Privacy Policy questions answered

We may collect your name, phone number, email, account activity, device signals, wallet references and support messages. Each category is used for account access, security, wallet checks or support handling.

No. We do not sell your personal data. We share limited records only with service partners that help operate hosting, security, wallet processing, verification or support tasks for th 7.

We store transaction references, timing, status and account matching details. We do not store your full wallet PIN, and we use the record to trace requests, resolve disputes and meet legal duties.

Yes. Contact our privacy inbox with the account email and phone number you used. We verify the request belongs to you before correcting records that are incomplete or inaccurate.

You can ask for deletion, and we will assess the request against security, dispute and legal retention needs. Some records may be kept for required timelines before removal.

Retention depends on the record type. Account, wallet, support and security records are kept for operational, dispute or legal periods, then removed or separated from direct identity where appropriate.

We update the effective date on this page when the Privacy Policy changes. If a change materially affects how your data is used, we present the change in clear wording.