Shared definitions
Terms such as account, wallet record, support message and session data mean the same thing across our legal pages. That avoids mixed wording when you read privacy and account terms together.
LEGAL REFERENCE
q66 Privacy Policy for Pakistan
This Privacy Policy explains how q66 collects, uses, stores and protects your account data when you access our platform where local law permits. Open your account with clear...
Pakistan account dataJazzCash referencesEasypaisa checksSadaPay recordsRaast IDs
How We Handle Your Data
We collect only the data needed to create your q66 account, secure access, process account activity and answer privacy requests. That can include your name, mobile number, login details, device signals, transaction references and messages sent to support. Where local law permits, we may verify payment records through Pakistani rails so account balances, withdrawals and refund checks match the person who owns
the account. We keep records for security, dispute handling and legal duties, then limit access inside our team. We do not sell your personal data, and we ask service partners to handle it only for the purpose agreed with q66.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
POLICY CHECKS
How We Check This Policy
Our privacy wording is checked against the account journey you actually use on q66. We compare each clause with data collected during sign-in, wallet matching, support messages and security logs. If a...
Account field mapping
We map each account field to a privacy purpose, such as login security, identity matching or support follow-up. That helps us avoid collecting data that does not serve the account.
Access control
Internal access is limited by role, so support, payments and security staff see only the records needed for their task. Activity logs help us check unusual access patterns.
Payment privacy
Wallet and bank references are stored as transaction records, not as wallet passwords. JazzCash, Easypaisa, SadaPay and Raast details are used for matching, reconciliation and dispute checks.
Device protection
We use device and session signals to spot account takeovers, repeated failed logins and unusual location patterns. These signals support account security without exposing private device content.
Retention checks
We keep different records for different periods based on fraud prevention, account queries and legal duties. When a record is no longer needed, we restrict or delete it.
Policy maintenance
When our account flow changes, we check whether the Privacy Policy needs an edit. Dates, purposes and contact routes are updated so the page matches current practice.
PAGE ALIGNMENT
How Our Policy Pages Align
Your privacy rights should read consistently across q66 legal pages. This page explains personal data handling, while related pages deal with terms of use, cookies and account rules. We align definitions, contact...
Cookie link
Cookie wording connects back to this Privacy Policy because cookies can store device or session data. You can see why a cookie exists before deciding how to manage it.
Account terms
Account rules explain what you must keep accurate, while this page explains how we handle the data you provide. The two pages are written to work together.
Security wording
Security clauses match our privacy position on login logs, device checks and suspicious access. We use those records to protect your account, not for unrelated profiling.
Regional wording
Pakistan references are kept consistent across legal pages, including supported regions language and local payment rails. That keeps privacy wording tied to your actual q66 account flow.
Support routes
Contact details are aligned so privacy, account and payment questions reach the right team. If your request crosses categories, we route it without asking you to repeat everything.
Update dates
When a legal page changes, we check whether related pages need the same date or wording update. That keeps our privacy promises aligned with current account handling.
LAYOUT SIGNALS
Privacy Page Layout Signals
We design this Privacy Policy so you can scan the parts that matter without losing the legal meaning. Headings separate data collection, use, storage, sharing and your choices...
Plain headings
Each heading names the privacy issue before the paragraph begins...
Local chips
Where payment references affect privacy, we name JazzCash, Easypaisa, SadaPay...
Short sections
Legal wording is split into compact sections that stay on...
Action wording
Privacy choices are written as actions, such as ask, correct...
Security markers
Security references are marked where they affect personal data, including...
Update marker
Policy changes are shown through date and wording updates, not...
Privacy Policy Questions Answered
We collect account details, login records, device signals, payment references and support messages needed to run and protect your account. We do not ask for wallet passwords or unrelated private files.
Payment references help us match JazzCash, Easypaisa, SadaPay and Raast activity with your account. They support balance checks, withdrawal verification, refund queries and dispute handling where local law permits.
Yes. Send the correction request through your signed-in help panel or privacy email route. We may ask for identity confirmation before changing mobile numbers, name details or payment-linked records.
We share limited data only when needed for hosting, security, payment matching, analytics or customer support. Partners must handle it for the agreed q66 purpose and not for unrelated use.
Retention depends on the record type. Security logs, transaction references, support messages and account details may follow different periods for fraud checks, disputes, legal duties and privacy request handling.
Use the signed-in help panel for faster identity checks, or email the privacy desk if you cannot access your account. Include the data issue, not wallet passwords.