Your Privacy Policy, Stated Plainly
q789 com sets out what we collect when you open an account, how payment records from JazzCash, Easypaisa, SadaPay, NayaPay and Raast are handled, and the choices you...
What Our Policy Holds And Why
When you register on q789 com, we collect the details needed to run your account: your name, contact number, region and the payment references your JazzCash, Easypaisa, SadaPay, NayaPay or Raast transactions create. We hold that data while your profile stays open and for the retention period our accountants and any relevant regulator require. Only the payments, security and support teams can
open those records, and every access is logged. Some processing is necessary to deliver the service you asked for; product messages go out only where local law permits and where you have opted in. Limited records reach payment processors and fraud-prevention services so transactions stay safe. Close your account and we delete or anonymise what we no longer need.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Who Writes And Maintains This Text
The policy you are reading is written and kept current by the same people who run our payment rails and account systems, so the wording follows how the platform genuinely behaves rather...
Clear Ownership
Each clause carries an internal owner in our payments, security or support teams, so one group stays accountable for updating the wording you are reading on this page.
Dated Change History
Every amendment is stamped with the date it took effect and a short line explaining what moved, so you can trace how this privacy position has changed over time.
Plain English Drafting
We write clauses as direct statements rather than legal padding, because a policy nobody finishes reading protects nobody and our desk would rather answer fewer confused questions.
Payments Team Input
Colleagues who settle JazzCash, Easypaisa, SadaPay, NayaPay and Raast transactions check every clause touching payment records, so the retention periods described match what our systems really do.
Security Sign-Off
Before a privacy clause goes live, our security lead confirms the storage, access and encryption described are the ones running on the account systems you use daily.
Scheduled Clause Audits
We walk through the whole text twice a year, check each statement against current practice, correct anything that has drifted and publish the revised version with a fresh date.
How This Page Sits With Others
Privacy sits beside our other policy pages and each one answers a different question. Cookie text deals with what your browser stores, account rules deal with how you...
How This Policy Page Is Laid Out
Every privacy page we publish follows the same layout, so you can find a clause without reading from the start. A short summary sits above the...
Summary Panel First
A short panel sits above the numbered clauses and states the three things people ask about most: what we collect, who sees it and how to request a copy.
Anchored Clause Numbers
Every clause carries a fixed anchor, so a link in the chip row drops you onto the exact paragraph you need rather than leaving you to scroll the full text.
Date Stamp Under Headline
The day this text last changed sits directly beneath the headline, and older versions are held internally, so you always know what is current on the page you are reading.
Regional Rail Labels
Clauses that touch money name the rails involved, so JazzCash, Easypaisa, SadaPay, NayaPay and Raast each appear against the paragraph describing how their records are handled.
Contact Block At Close
The final block repeats our live chat and email routes alongside the hours our privacy desk keeps, so nobody has to hunt through earlier sections to reach us.
Data Terms Glossary
A short glossary near the end defines the handful of technical terms we cannot avoid, such as retention window and processor, in one line each and in plain English.