Your Privacy Policy, Written for Your Account
Open an account here and you get one clear deal on data: we tell you what we hold, why we hold it, and how to have it removed...
How We Treat Your Data Where Local Law Permits
Your account data is handled under the rules that apply in the regions we serve, and where local law permits, that means Pakistan's own framework. We store what you give us at registration, plus the transaction trail behind a JazzCash, Easypaisa, SadaPay or Raast transfer, so a withdrawal can be matched to the right account. We keep that record only while it
is needed for fraud checks, dispute handling and any legal duty we carry. Access is limited to staff who need it for those tasks, and we log who opened what. You can ask us to correct, export or close the file we hold on you, and we will explain anything unclear in plain language.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Who Checks What We Publish Here
A policy page is only worth reading if real people stand behind it. The wording here is maintained by the team that runs our accounts, payments and support desks, not by a...
Operating Team Authors
Every paragraph is drafted by staff who run the account, verification and payout flows you use, so the wording matches what actually happens when you open an account.
Payments Lead Sign-Off
Our payments lead signs off any line describing how JazzCash, Easypaisa, SadaPay, NayaPay or Raast records are stored, corrected or shared with a settlement partner.
Security Desk Input
The security desk checks our description of stored device data, login logs and session controls, and flags anything that has shifted since the last update went out.
Support Desk Feedback
Questions you raise through chat and email about your data feed straight back into this page, which is how gaps get closed instead of sitting open for months.
Dated Revisions
We date each revision so you can see when a passage last changed, and older wording is kept internally for reference rather than quietly dropped from the file.
Plain Language Pass
A final read-through strips out legal padding so a reader in Pakistan can follow what we do with your data without needing a lawyer at hand.
The Same Line on Every Policy Page
Our policy pages share one voice and one set of terms, so what you agree to here holds across your account. Read the payment and cookie passages beside...
| Shared Definitions | Terms like account data, stored record and transfer trail mean the same thing on every page we publish, so a phrase you learn here still reads correctly elsewhere on the site. |
|---|---|
| Matching Revision Dates | When one page is revised, the matching change goes to its siblings in the same update, and the revision date on each page moves forward together rather than drifting apart. |
| One Contact Point | Privacy questions land with the same support desk described on our contact and terms pages, using one email address rather than a scatter of separate inboxes. |
| Same Retention Rules | How long we keep a payment record, a login log or a closed account file is stated the same way wherever retention comes up across the pages we run. |
| Payment Wording Aligned | Descriptions of how JazzCash, Easypaisa, SadaPay and Raast activity is recorded stay in step between this page and the sections covering your account balances. |
| Cookie Terms Mirrored | Cookie categories, consent choices and browser controls are written once and reused, so you do not meet a different cookie story on a second page you open. |
| Same Dispute Path | If a complaint about how we handled your data needs escalating, every page points to the same internal route and the same response window we promise. |
Layout Choices That Keep the Policy Readable
Long policy text loses readers, so we structure this page for scanning. Each block carries a short heading, the summary sits at the top where you...
Summary At Top
The paragraph you are reading sits under a plain summary, so you can pick up the main points before committing to the full wording that follows further down the page.
Named Payment Rails
Where we mention a transfer, we name JazzCash, Easypaisa, SadaPay, NayaPay or Raast instead of a vague wallet label, so you know which record is being described.
Short Paragraph Blocks
Clauses are broken into short blocks with breathing room between them, which keeps a long document readable on a small screen without pinching and zooming.
Handset-Friendly Tables
Retention and sharing tables are built to fit a handset, so you can check how long a record is held while you are away from a desktop or laptop.
Expandable Clauses
Secondary clauses open on tap rather than loading the page with text, which keeps the main reading path clean on a first visit from a mobile browser.
Matching Notices
Any message we send you follows the structure of this page, so a note about your data reads like the section it came from rather than a separate document.