Privacy Policy for your q988 account
q988 keeps your account data, payment references, device records, and support messages under one clear Privacy Policy for Pakistan. Read how we collect, use, store, and share limited...
How q988 handles privacy records
q988 collects only the account, device, payment, and support data we need to run your account and protect access where local law permits. Our Privacy Policy explains why each record is used, how long it is kept, and when a payment partner may receive a limited reference. JazzCash, Easypaisa, SadaPay, NayaPay, and Raast appear here as context because payment records can contain
sender names, phone numbers, transaction references, and timing stamps. We do not sell your personal data, and we separate security checks from preference settings. If you ask us to correct or remove eligible records, we check account ownership first, then tell you what action was taken and what must stay for account integrity.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Reach us about privacy questions
Privacy requests need a clear path, not guesswork. Use the contact route linked to your q988 account so we can confirm ownership, protect your balance history, and answer with the exact privacy step available for your record.
Account help panel
Send a privacy request from the logged-in help panel. We match it to your q988 account email or phone, then reply with the data step we can take and any verification needed.
Email privacy desk
Email our privacy desk when you cannot reach the help panel. Include your registered contact detail, a short request summary, and no full payment wallet passwords or private PIN details.
Payment record check
For JazzCash, Easypaisa, SadaPay, NayaPay, or Raast references, send only the transaction ID and date. We use those details to locate the privacy record safely.
How we keep this policy current
We write this Privacy Policy from the way q988 actually handles account records. Each section is checked against our login flow, payment reference handling, support tools, cookie settings, and security process before...
Operational checks
Our privacy wording follows the account screens you see after login. If a field asks for your phone, email, or wallet reference, this policy explains why it is requested.
Local payment context
We describe Pakistani payment references plainly because wallet names, phone numbers, and Raast IDs may appear in support records when you ask us to trace a transaction.
Cookie clarity
Cookie wording is tied to real browser behaviour on q988. We separate essential session cookies from preference or analytics cookies so your privacy choice is easier to read.
Security alignment
Our data retention wording matches the checks used for password resets, device changes, and unusual access attempts. Privacy access is balanced with account protection.
Support training
Support replies follow privacy scripts that avoid asking for wallet PINs or full card-style secrets. We ask for only enough detail to confirm the correct account.
Change tracking
When privacy wording changes, we keep internal version records showing what changed and why. This helps us answer your questions without relying on vague memory.
Policy wording across q988 pages
Your privacy expectations should not change as you move through q988. We keep the Privacy Policy aligned with the account area, cookie banner, support replies, and payment reference...
Privacy cues you see on page
We place privacy cues where you make account decisions. Short labels, readable sections, and contact prompts help you understand what q988 records before you send details, adjust preferences...