Shared definitions
Terms such as account, stored record and support ticket carry the same meaning here as on our terms of use, so you never hold two interpretations at once.
Every record we hold about your account is named on this page, in plain language rather than legal padding. You will see which details come from your registration...
Our commitments sit alongside the rules of the country you sign in from, so we apply them where local law permits and inside supported regions only. Where a regulator in your area requires a different retention period, that local rule takes priority over the paragraphs below. We refresh this page whenever our payment rails change, because JazzCash, Easypaisa, SadaPay and Raast each
return slightly different reference data with every transfer. Nothing here reduces a right you already hold. Where we cannot lawfully serve a region, we close access there rather than store records we have no basis to keep. You can ask which version applies to your account, at any time, and we will confirm it in writing.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Every request about your account records reaches a person, not a bot. Live chat inside your account is the quickest route for small corrections, while email suits anything needing documents attached. We answer in clear Pakistani English, seven days a week, between 10:00 and 23:00 PKT. Ask for a copy of your data and we reply with a reference number.
Open your account and use live chat for quick fixes such as a misspelled address or a changed phone number. Agents verify your identity, then update your profile while you wait.
Send written requests when you need a documented trail, like a copy of stored records or a correction confirmed on paper. We reply with a reference number for the same ticket.
For anything touching sign-in or transfer details, we answer through the secure message box inside your account, keeping bank references from JazzCash, Easypaisa, SadaPay or Raast protected.
Three people touch this page before you read it. A data steward maps which systems hold your records, a legal writer turns that map into plain English for...
Our data steward walks each storage system and confirms the records listed here match what we hold. Add, move or...
A legal writer converts every clause into language a reader in Pakistan can follow, explaining any term that has no...
Our security lead tests the encryption, session and access claims made here. Anything that cannot be shown in a live...
Because JazzCash, Easypaisa, SadaPay and Raast return different reference formats, we re-check the transfer paragraphs whenever a rail updates its...
Support agents log every privacy question they cannot answer from this page. Those logs reach the writing team monthly, and...
We keep an archive of earlier versions so you can compare what changed and when. If an update affects how...
Privacy sits beside our terms of use and cookie pages, and all three share the same definitions. Account means the same thing on each, as do stored record and support ticket. We...
Terms such as account, stored record and support ticket carry the same meaning here as on our terms of use, so you never hold two interpretations at once.
When one page in the set changes, we publish the matching pages in the same release wherever shared wording is affected, keeping version dates in the same week.
Our cookie page lists the browser storage we set, and the paragraphs here describe why each one exists. Both come from a single internal register rather than separate drafting.
If the terms page says we retain a record for a set period, this page states the same period in the same words. Contradictions are treated as errors.
Transfers through JazzCash, Easypaisa, SadaPay and Raast are described the same way wherever they appear, so the wording never shifts between policies. Reference names stay consistent across every page.
Whichever policy you read, requests route to the same support desk and produce the same ticket format, so you are never passed between teams by page.
Every sibling page is written to the same reading level and checked against the same jargon list, so moving between them feels continuous rather than like changing websites.
This page is built in short blocks so you can find your answer without scrolling through a wall of clauses. A summary strip near the start...
The opening strip names every record type we hold, from registration details to transfer logs, so you see the full scope in one glance before reading any paragraph.
Each card covers one record family and states why we hold it, how long we keep it and who can open it. Short paragraphs keep every card readable on a phone.
A date sits above the text and changes whenever the wording changes. If it matches what you saw last month, nothing on the page has moved.
Buttons beside the support block jump straight to live chat or the message box, so a correction request takes two taps instead of a hunt through the document.
A short note states which regions we serve and reminds you that access is offered only where local law permits, so you know where this policy applies.
Uncommon legal terms carry a brief explanation in the margin, written for readers in Pakistan. You should never need a second tab open to follow a single sentence.