Privacy Policy for q98 Accounts
q98 keeps your account data, transaction records, and device access signals under one Privacy Policy, so you know what we collect before you open an account. Open your...
How We Handle Your Data
This Privacy Policy explains how q98 collects, uses, stores, and shares data connected with your account where local law permits. We record details you provide during account setup, security checks, transaction requests, support chats, and device sessions. For Pakistan access, wallet or bank rail names may appear in your account history so we can match your request, confirm status, and answer later
privacy queries. We do not sell your personal data. We use limited partners for hosting, fraud screening, payment routing, analytics, and support tooling, and each partner receives only the data needed for that purpose. If a legal request reaches us, we assess it before any disclosure.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
How We Keep Policy Accurate
We treat the Privacy Policy as an operating document, not a page left untouched. Product, support, security, and finance teams flag data-flow changes before wording is adjusted. When tools change, we check...
Data-flow mapping
We map where account, device, session, and transaction data moves inside q98. That map helps us describe collection points clearly instead of using vague phrases that do not match the account flow.
Security input
Our security team checks policy wording against login controls, device alerts, password resets, and fraud screening. If a control uses personal data, the Privacy Policy must explain the reason in plain language.
Finance alignment
Transaction wording is checked against how JazzCash, Easypaisa, SadaPay, and Raast requests appear in our records. The aim is to describe record keeping without exposing wallet numbers unnecessarily.
Support feedback
Support teams tell us which privacy questions keep coming back. We use that feedback to make access requests, correction steps, and account-closure data handling easier to understand.
Change log discipline
When we update the Privacy Policy, we keep an internal change log showing what changed and why. This helps our team answer later questions without relying on memory.
Plain English check
Before new wording goes live, we remove legal clutter where possible. You should be able to understand what data q98 collects, why it is used, and how to contact us.
Consistent Privacy Across q98 Pages
Privacy wording should not change depending on where you read it. We align this page with account screens, cookie settings, cashier prompts, and help messages so your expectations...
| Account screen | The account screen asks for identity and contact details only where needed for profile setup, security, and service messages. This policy explains why those fields exist and how we store them. |
|---|---|
| Cookie settings | Cookie choices connect with this policy because device signals support login safety, session continuity, and site measurement. We separate necessary functions from optional analytics wherever the interface allows. |
| Cashier prompts | Cashier prompts may show JazzCash, Easypaisa, SadaPay, or Raast labels to help you recognise a request. This policy explains how those transaction references are retained and protected. |
| Support scripts | Support scripts mirror the Privacy Policy by asking for limited verification before discussing account records. Agents should not request full wallet access or unrelated personal documents. |
| Security messages | Login alerts, password reset emails, and device checks use personal data for account protection. This policy explains those security uses so the messages do not feel unexpected. |
| Promo board privacy | If you check the promo board, q98 may use account status and location signals to show eligible items. The Privacy Policy explains that personalisation without turning it into hidden sharing. |
| Closure requests | When you ask to close an account, some records may still be kept for legal, fraud, or transaction reasons. This policy sets out why retention can continue after access ends. |
Privacy Cues You Can See
We place privacy signals where decisions happen, not only at the foot of the page. Short labels near forms, session prompts, and support routes help you...
Field labels
Account forms use short labels beside sensitive fields, so you can see whether a detail supports identity checks, contact recovery, transaction matching, or account security before you submit it.
Consent prompts
Where optional tracking or tailored messages are used, we place consent prompts close to the action. The wording links back to this Privacy Policy for fuller detail.
Session reminders
If a session times out or a new device appears, q98 may show a security reminder. Those notices explain that device signals are used to protect account access.
Document warnings
When a verification document is requested, we tell you what to send and what to hide. This keeps unnecessary personal data out of our storage wherever practical.
Transaction tags
Wallet and bank rail names may appear as simple tags in your history. They help you recognise JazzCash, Easypaisa, SadaPay, or Raast requests without displaying excessive account detail.
Contact reminders
Support pages remind you not to share passwords, full wallet access, or unrelated personal documents. Privacy support can still locate your case through controlled verification steps.