How We Handle Your Account Data
Your account data stays yours, and this page spells out exactly what we hold and why. From the moment you open an account to the day you ask...
Where Local Law Sets The Rules
We follow the rules that apply where you live, and where local law permits we take the stricter reading whenever two sets of rules disagree. That shapes what we keep, how long we keep it and which partners we share it with, even when the product looks identical on your screen. Register from Pakistan and our handling of JazzCash, Easypaisa, SadaPay, NayaPay
and Raast references follows that same regional approach: we record only what a payment trail needs and hold it as long as the applicable rule asks. Where your request and a legal duty collide, we tell you which duty applied and why. Ask us which regional rule set governs your account and we answer in plain English, not a clause number.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
How This Page Is Written
We write this page the same way we write everything else, from the desk that runs the account systems. Each claim maps to something you can check yourself: a payment record, a...
Written In-House
This page is drafted by the team that runs our account systems rather than copied from a template, so the wording matches what actually happens when you move money.
Records You Can Check
Every reference we describe lines up with what you see in JazzCash, Easypaisa, SadaPay, NayaPay and Raast. Open your own transaction history and compare it against these sentences.
Plain English Drafting
We rewrite clauses until they read like sentences a normal person would say out loud. If a line still needs a translator, it is not finished.
Change Log Kept
Whenever we edit this page we keep the earlier version on file and state what moved, so you can see what changed and when it took effect.
Regional Checkers
Colleagues working Pakistan hours read every draft before it goes live, checking that the wording fits how local rules and wallet habits work in daily practice.
Corrections Welcome
If a line here does not match your own experience, tell the support desk and we will look into it. Where we got it wrong, we correct the page.
Matching Our Sibling Pages
Our other policy pages share this same spine, so you never relearn the structure. Terms sit alongside this page, security wording sits beside both, and all of them...
| Same Opening Promise | The first paragraph across our policy pages makes the same commitment: we collect what the account needs and nothing beyond it. Nothing here contradicts the terms page. |
|---|---|
| Matching Retention Terms | How long we keep a record is described the same way here and on the terms page, so you never compare two timelines. Pakistan payment trails follow the longer period. |
| One Contact Route | The support desk, chat window and written request path listed here appear on every sibling page. Whichever door you use, the same people log and answer it. |
| Shared Security Wording | Session handling, device checks and password rules are described identically on both pages. If a detail changes, both pages move within the same week rather than months apart. |
| Identical Brand Chips | The JazzCash, Easypaisa, SadaPay and Raast references here also appear on our terms and account pages, so familiar local brands read the same wherever you land. |
| Terms Aligned Here | Where a term of service touches your data, the two pages say the same thing in different words rather than leaving a gap. Disagreements resolve in your favour. |
| Shared Update Rhythm | We refresh this page and its siblings on the same schedule, then flag what moved. That keeps the whole set consistent instead of one page drifting ahead. |
Layout You Will Notice
This page is built for reading rather than scrolling past. Jump links sit above the first block, every subject carries its own heading, and the plain...
Short Jump Links
The link row above the first block takes you straight to retention, sharing or contact without hunting. Blocks stay short so you land near the sentence you came for.
Summary Before Clauses
Every subject opens with one plain sentence before the detailed wording appears. Read those opening lines alone and you know where your account stands, without the clause text.
Mobile Stacked Columns
On a phone the blocks stack in a single column with larger text and wider tap targets. The same order applies as on desktop, so nothing jumps between screens.
Localised Wording
Sentences are written for readers in Pakistan rather than translated from elsewhere, so the examples used are ones you already recognise from the wallet apps you already use.
Version Date Shown
A date sits at the foot of the page showing when the wording last moved. If that date is recent, the change is summarised in one sentence above it.
Read Aloud Friendly
Paragraphs stay under five sentences so screen readers keep an easy rhythm and support calls stay simple. Long sub-clauses are split out rather than buried in brackets.