Privacy Policy for your q44 account
q44 keeps your privacy choices, account checks and Pakistan payment data in one clear policy so you know what we collect before you open your account. We explain...
How we handle your personal data
Our Privacy Policy sets out how q44 collects the details you give us, the device and session signals we record, and the payment references needed to connect your account with supported Pakistan rails. We use this data to create and protect your account, confirm transactions, answer privacy requests, check for misuse, meet legal duties, and keep records that auditors or service partners
may need. We do not sell your personal data. Where local law permits, we share limited fields with payment processors, identity checks, hosting providers, analytics tools and customer care systems under contractual controls. You can ask us to correct, access or erase eligible data, and we will explain when retention rules mean some records must stay in place.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
How we keep this policy accurate
We keep this policy close to the systems it describes. When a payment rail, identity check or support tool changes, our privacy text is checked against the live...
Data map checks
Each policy change is matched against our data map, covering account fields, session logs, device signals and transaction references. If...
Rail checks
JazzCash, Easypaisa, SadaPay and Raast flows create different reference data. We name those rails in privacy work so your request...
Local wording
We write the policy in Pakistani English and avoid legal fog where a direct word works. That helps you understand...
Security alignment
Our privacy wording reflects account controls such as password resets, device flags and withdrawal verification. These events can create logs...
Retention checks
We set retention periods by record type, not one blanket timeline. Fraud checks, transaction logs and customer messages may need...
Partner controls
Vendors that process q44 data must work under written terms on confidentiality, access control and deletion. We limit what they...
Consistent privacy terms across q44 pages
q44 keeps the Privacy Policy aligned with related legal pages, but this page has its own job: personal data. The terms page explains account rules, the cookie page...
| Terms alignment | When the terms mention account verification, this policy explains which personal data may be checked and why. We keep the wording consistent so rule enforcement does not hide separate data uses. |
|---|---|
| Cookie page link | Browser storage can remember sessions, settings and fraud signals. The cookie page handles those tools in detail, while this policy explains how any personal data from them is used. |
| Security page link | Security text covers how we protect access. This policy explains the privacy side of the same logs, including device markers, failed login records and password reset events. |
| Cashier wording | Where our cashier mentions JazzCash, Easypaisa, SadaPay or Raast, the privacy wording explains which reference fields may be stored, who sees them and how long records may remain. |
| Support records | Support pages explain how to contact us. This policy adds what happens to chat transcripts, email messages, identity checks and attachments when you send a privacy or account request. |
| Message choices | If you choose to receive campaign messages, the privacy text explains consent, delivery partners and opt-out handling. It stays separate from any offer terms shown inside your account. |
| Update labels | When a related legal page changes, we check whether the privacy wording also needs a date change. That prevents old data language from sitting beside newer account rules. |
Policy page signals you can verify
This page is built so your privacy choices are visible before you share more data with q44. The layout separates collection, use, sharing, retention and rights...
Clear date stamp
The page shows when the Privacy Policy was last changed, so you can tell whether the text reflects recent account, support or rail updates before you rely on it.
Rights in plain words
Access, correction and erasure are described as actions you can request, not abstract legal labels. We also explain when record-keeping duties may limit what can be removed.
Local rail context
JazzCash, Easypaisa, SadaPay and Raast are named where payment-reference data matters. This helps you understand why transaction IDs, mobile numbers or bank references may appear in privacy records.
Short data categories
We group data into account details, session records, device signals, financial references and messages. Short categories make it easier to ask precise questions when you contact us.
Sharing boundaries
The policy separates q44 teams from external processors, then explains why each category may receive data. That structure helps you see when sharing supports security, payments or customer care.
Request proof
We explain why identity proof may be needed before we release or change personal data. The same rule protects you if another person tries to access your records.