Shared definitions
Words such as account, personal data and payment reference carry one meaning across every policy page, so nothing changes when you move from here to another page.
Opening an account with us means handing over a few personal details, so we keep this page updated with what happens to each one. You will see what...
Data rules differ from province to province, so this policy is written the way you expect us to work in Pakistan. When you register we ask for your name, date of birth, mobile number and email address. When you move money, a JazzCash, Easypaisa, SadaPay, NayaPay or Raast transfer returns a reference code to us rather than your wallet PIN. We also
record sign-in attempts and device details so a login that does not match your usual pattern can be flagged. Where local law permits, we hold account records while the account is open and for a set period afterwards, then delete or anonymise them. If a regional rule asks for something different, that rule takes priority over this page and we will tell
you when it applies.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
This page is maintained by the same team that runs accounts, payments and support, not by an outside writer. When a payment rail changes, a new identity check goes live, or a...
Every edit carries a date at the foot of the page, so you can tell at a glance whether you are reading a newer version than the one you saved or printed earlier.
A short summary of what shifted sits beside the date, written in everyday language rather than legal shorthand, so a change in how we handle your details is easy to spot.
Before anything goes live, our accounts and payments teams read the draft against what the platform actually does, and they flag any line that reads like a promise we cannot keep.
Where a province or region requires something different, we mark it inside the section it affects instead of burying it in small print, so you never guess which rule applies.
We avoid legal shorthand where an ordinary sentence works just as well, because a policy only helps you if you can read it once and understand what we do with your details.
You can question any line on this page at any time, and we will explain how that rule works for your account rather than pointing you back to the same paragraph.
Our policy pages share one set of definitions, so you are not reading a different story depending on which tab you open. A term used here means the same thing in our...
Words such as account, personal data and payment reference carry one meaning across every policy page, so nothing changes when you move from here to another page.
The rules you accept when you open an account sit beside this policy and point back to the same definitions, which keeps the two documents from drifting apart over time.
Our cookie notice explains the small files stored on your device, and it uses the same wording for tracking that appears in the sign-in records section of this policy.
Any promotion you accept comes with its own conditions, and where those touch your personal details they follow the wording set out here rather than inventing fresh rules.
The verification steps across our pages are the same, whether you meet them at sign-up, at withdrawal, or when you update the mobile number saved on your profile.
If you disagree with a decision about your data, our complaints page uses the same escalation steps and timeframes, and the same team picks up the case from there.
The English and Urdu versions of our policy pages are updated together, and if a sentence ever reads differently, the English wording on this page is the one we stand behind.
We set this policy out so you can find an answer without scrolling through walls of text. A short summary opens the page, the detail follows...
A few lines at the start give you the shape of the policy, so you can tell within seconds whether the section you need sits further down the page.
Each heading names the exact subject underneath, from the details we collect when you join to the way sign-in records and device data are handled.
Where a list works better than a paragraph, we set the facts out in a table, so you can run your eye down a column instead of reading the same things twice.
A short timeline shows how long records stay with us after an account closes, with each period written out plainly rather than as a legal formula you have to decode.
One block explains the switches inside your account, including the marketing preferences you can turn off without losing access to the lobby or your balance.
Every route to our team sits together near the foot of the page, so you can send a message, email the privacy desk or request a callback without searching.