Privacy Policy for Your 966pak Account
966pak explains how we collect, use and protect your personal data when you open an account, enter the lobby or request account help where local law permits. This...
How We Handle Your Data
This Privacy Policy applies to 966pak services on 966pak.app in supported regions of Pakistan, where local law permits access. We collect details you give us, such as your name, mobile number, account credentials and support messages, plus technical data such as device type, IP address, session timing and security logs. When you use JazzCash, Easypaisa, SadaPay or Raast, we keep transaction references,
status updates and verification records needed to process account requests and resolve queries. We use this data for account access, fraud checks, service security, transaction tracing, support replies and legal record keeping. We do not sell your personal data. Access is limited to trained teams and service partners who need it for the specific privacy purposes described here.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
How We Keep This Policy Current
We maintain this Privacy Policy as an active page, not a static legal block. Each change is checked against how our account flow, payment records, support tools and security logs actually work...
Account flow checks
We compare the policy against the account fields you see during joining, profile editing and login recovery. If a new field is added, we record why it is needed before collecting it.
Payment record mapping
For JazzCash, Easypaisa, SadaPay and Raast, we map which reference numbers, timestamps and status messages are stored. The policy reflects those records instead of using vague payment wording.
Security log reading
Our security team checks login records, device markers and failed access attempts when privacy wording changes. This helps us explain monitoring in plain language without exposing sensitive defence rules.
Support script alignment
We align support replies with this policy so you receive the same privacy wording through chat and email. Staff are told not to request passwords or unnecessary wallet details.
Retention checks
We keep data only for account service, dispute handling, legal record duties and security needs. Retention periods are checked by record type, including chat logs, transaction references and login history.
Plain English wording
We write privacy terms in direct Pakistani English so you can understand what happens to your data. When technical wording is needed, we pair it with account examples from 966pak.
Consistent Privacy Across Legal Pages
Our privacy wording works with nearby legal pages rather than repeating them. This section shows how the Privacy Policy connects with account rules, security terms and support processes...
| Privacy Policy | This page explains what personal data we collect, why we use it, how we protect it and which choices you have when asking 966pak about your records. |
|---|---|
| Terms page | The Terms page sets account rules and service conditions. When those rules require identity checks or transaction records, this Privacy Policy explains the related data handling. |
| Cookie page | Cookie wording deals with browser storage, analytics signals and session markers. This Privacy Policy connects those signals to account security, device recognition and site performance. |
| Security wording | Security content explains how we reduce account misuse. This Privacy Policy covers the personal data used in that work, such as login timing, device type and access alerts. |
| Support terms | Support pages explain how to reach us. This Privacy Policy explains how support messages, attachments and identity checks are handled when you ask for account assistance. |
| Payment records | Payment wording covers transaction actions. This Privacy Policy covers reference IDs, wallet names, status updates and verification records linked to JazzCash, Easypaisa, SadaPay and Raast. |
| Account closure | If you ask to close an account, service access may end before every record is erased. Some records stay for dispute handling, security checks and legal duties. |
Privacy Cues Built Into the Page
This page is designed to help you read privacy terms without hunting through long blocks. The layout separates collection, use, storage and contact points so you...
Short badges
The badges near the hero show the main privacy areas before the full text begins. They help you spot account data, device checks, transaction records and support privacy quickly.
Context chips
Payment chips are used only as privacy context. JazzCash, Easypaisa, SadaPay and Raast appear because transaction references can form part of your account record.
Contact prompts
Contact blocks explain which channel suits each privacy request. That helps you avoid sending sensitive details to the wrong place and lets us route your request properly.
Plain categories
Data categories are named in practical account language, such as login records, support messages and transaction references. We avoid legal clutter where direct wording can do the job.
Record reasons
Each section links data use to a reason, including access control, fraud checks, dispute handling or legal duties. This keeps the policy tied to real account activity.
Update clarity
When this policy changes, we adjust the page wording to match the current account flow. You can return here to see how privacy handling is described.