Shared Definitions
Words like account, wallet and record mean the same thing on every legal page here, so a term you pick up in one document still holds on the next one.
This page sets out what we collect when you open an account, why we hold it, and the choices you keep over your own details where local law...
When you open an account we collect the details you type in yourself, your name, contact number, email address and the wallet number tied to JazzCash, Easypaisa, SadaPay, NayaPay or Raast. Transaction entries, device type, browser language and login timestamps sit alongside that so we can confirm it is really you signing in. We keep these records only as long as the
rules covering your region require, then delete or anonymise them. Where local law permits, you can ask us to show you what we hold, correct anything wrong, or close the account and have your profile removed. Some retention duties stay with us even after closure because financial record-keeping rules in supported regions need them. If a feature is not open to your
area, we say so rather than quietly gathering data we cannot lawfully use.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Privacy questions reach a real person, not a queue that never moves. Write in from the email address on your account so we can match the request to your profile, and we confirm what happens next.
Write from the email you joined with and our team matches your request to the right profile before anyone opens or changes a stored record, usually within a few working days.
Open the chat panel inside your account and ask about cookies, wallet entries or stored details; the same colleague team answers there through Pakistan working hours, every day of the week.
When something we hold is wrong, send the change through the form in your settings so we can log it, verify it against your account and update your file with a fresh timestamp.
Anyone can publish a policy; we would rather show you the habits behind ours. Every change to this page is dated, every request is logged, and every colleague...
Every edit to this page carries the date it went live, so you can see when wording on collected records...
We ask for a name, a contact number, an email and one wallet reference, nothing beyond what is needed to...
Colleagues see only the fields their job needs, so the person answering your chat cannot browse wallet histories they have...
Details travelling between your device and our servers move over encrypted connections, and stored records sit behind the same protection...
Each record type has a written lifespan, so contact details, login history and wallet entries leave our systems on a...
We inspect our own access logs on a regular cycle, checking who opened account records and why, then tighten permissions...
Terms, cookie wording and this privacy page are written as one set, so what you read here should match what sits beside it. If two pages ever appear to disagree, the stricter...
Words like account, wallet and record mean the same thing on every legal page here, so a term you pick up in one document still holds on the next one.
Terms, cookie text and this privacy page move on the same schedule, so a change touching your records shows up in every document on the same day.
The data desk handles requests that land through any legal page, so you never have to work out which document your question belongs to before writing in.
Cookie labels you meet on the home page match the labels listed here, letting you connect a setting you changed with the section explaining it plainly.
JazzCash, Easypaisa, SadaPay, NayaPay and Raast are spelled the same way on every page, so a wallet entry on your statement matches the wording in a clause here.
Where one document mentions how long a record stays, the others agree, so you are not left holding two different answers about the same transaction history.
If a paragraph here ever contradicts a sibling page, tell us and we correct both, treating the tighter reading as the one governing your account meanwhile.
A policy only works if you can actually read it. So this page gives you plain headings, short paragraphs, dated change markers and a summary block...
Headings say what the paragraph actually covers, so you can jump straight to wallet handling, cookie choices or deletion steps without reading everything above them at all.
A small dated label sits beside revised wording, letting you tell at a glance whether the clause you read last month has moved since then, quietly or otherwise.
No paragraph runs long enough to hide a condition, so anything limiting what we do with your records stays visible before you reach the heading underneath it.
JazzCash, Easypaisa, SadaPay, NayaPay and Raast appear exactly as they are written on your own wallet statements, so this page stays readable beside the app you use.
A side panel stays on screen as you scroll, letting you hop between the summary at the top and a detailed clause further down without losing your place.
The whole page prints cleanly if you want a paper copy for your own records, with headings intact and nothing trapped behind a menu that will not open.