Account Terms
What we say here about identity checks, sign-in records and closure requests repeats in the account terms with the same timelines, so the two pages never pull apart.
We hold only the account details a check or a payout actually needs, and you can read, correct or request a copy of all of it whenever you...
We write this policy to sit alongside the rules of the regions we serve, so some clauses take effect only where local law permits. If a requirement in your province differs from what you read here, that local requirement wins, and we tell you when it applies. What stays constant is this: your account records, sign-in history and payment references are handled
the same way whichever Pakistani rail you use, from JazzCash through to Raast. We revisit the wording whenever we change how data moves inside our systems, and we date every revision so you can see what shifted. Access is offered in supported regions only, and where a jurisdiction sets a different handling standard we follow that standard instead.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
If any clause is unclear, our privacy desk answers in plain English. Message us with your account reference and we point you to the exact section that applies, then walk you through the step you need. Requests are logged so nothing is lost.
Open live chat from any page during Pakistan working hours and a person on our privacy desk picks up your question, usually inside a few minutes. Weekend requests wait until the next working morning.
Write to our data desk with your account reference and we confirm receipt the same day, then reply with the section covering your request and the steps that follow.
Sign in and open settings to change your contact details, switch off non-essential cookies, or download a copy of the records we hold for your account. Changes save straight away.
Our compliance and platform teams write this text together, so the wording matches what our systems do. We skip legal padding and describe each practice the way we...
Our own compliance and platform staff write this page, so each clause reflects settings we can change ourselves rather than...
Every practice is described in everyday wording first, and the formal clause sits underneath only where a regulator or a...
Each revision carries the day it took effect, so you can tell whether the wording you agreed to when opening...
Before a clause goes live we walk through the matching screen or back-office setting ourselves, so the text matches what...
We do not sell your account records to brokers or advertising lists, and any partner handling a payment for you...
When a revision changes how your data is used, a notice appears inside your account and we email the address...
The clauses here line up with the account terms, cookie notice and payment pages sitting beside them, so you are not reading three versions of one promise. Spot a gap and we...
What we say here about identity checks, sign-in records and closure requests repeats in the account terms with the same timelines, so the two pages never pull apart.
The cookie page lists every tag we place on your browser, while this policy explains why each one exists and which can be switched off from settings.
JazzCash, Easypaisa, SadaPay, NayaPay and Raast carry the same meaning on every page, so a rail named here matches the rail you pick at checkout.
Our agents answer from the same wording you read, so a question about retention or deletion gets one reply rather than two conflicting ones. The desk never improvises policy.
Device checks, session timeouts and password rules in the security section line up with the settings you meet when you sign in from a new phone. Nothing appears that we cannot enforce.
The English text is the one we act on. Where a translated copy reads differently, the meaning stays fixed and we correct the translation rather than the rule.
Revisions are numbered and dated in one place, so you can trace how this policy moved from the version you first agreed to the one in force today.
The layout is built so you can find your answer without reading clauses that do not concern you. Short headings, dated versions and a jump line...
Each subject sits under its own heading with a jump line above it, so you can move straight to the clause on retention, cookies or closure.
Every version shows the day it took effect, which tells you whether the wording you accepted still stands or has shifted since you signed in last.
Where a clause covers transaction records, the chips name the Pakistani rails involved, so the example matches the way you actually move money. Nothing is left abstract.
A one-line summary opens each block before the formal wording, letting you decide in seconds whether the detailed clause deserves a closer look. The full text stays underneath.
Headings stay short and paragraphs stay narrow, so the text remains readable on a small screen, which is where most of our Pakistani readers open it. No zooming required.
The contact details sit at the foot of every block, so you can raise a question about a clause the moment it reads unclearly. You never hunt for the address.