How We Handle Your Data
This page sets out what account details we collect when you open an account with us, why we hold them, and the choices you keep over your own...
Where This Policy Applies
This policy applies to your account wherever you reach us from, and it sits alongside the rules that apply in your own supported region. We follow Pakistani law where it governs the data we hold, and we adapt our practices where local law permits a different approach, so read the wording here together with any notice we send you directly. When you
move money through JazzCash, Easypaisa, SadaPay, NayaPay or Raast, the partner handling that rail receives what it needs to complete the transfer, and we receive the confirmation we need to credit your account. We do not sell your details to advertisers. If a rule in your region differs from something written here, the local rule wins for you.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Reaching Our Data Team
Questions about this policy go to a small team that handles data requests and nothing else, so you are not passed around a general queue. Write to [email protected] from the email address on your account and you will get a reference number. Live chat inside your account reaches the same team during Pakistan hours, and mentioning a JazzCash or Easypaisa transaction reference helps us trace a payment record faster.
Policy Email
Send the question to [email protected] from the address on your account. Every message is logged, given a reference, and answered with the outcome rather than a holding note.
In-Account Chat
Open the chat panel once you are signed in and choose the data request option. The agent already sees your account history, so you do not repeat what you have told us.
Record Requests
Ask for a copy, a correction or a deletion and we tell you exactly which document we still need. Your request stays open until a written answer reaches your inbox.
How This Policy Is Kept Current
Every line here is written and checked by the people who run account operations, then read by our compliance lead before it goes live. We date each change and keep earlier wording...
Written In-House
The policy is drafted by the team that handles account data daily rather than an outside agency, so the description of how records move matches what actually happens on the platform.
Dated Revisions
Each version carries a date and a short summary of what changed. Ask for any earlier version and we send it to the email address registered on your account.
Two-Person Check
No change goes live until a second person has read it against current practice. If the two readings disagree, the page stays as it is until the gap is closed.
Plain Language
Anything that reads like legal filler gets rewritten. If a sentence needs a second pass to make sense, it is replaced with wording that says the same thing in fewer words.
Limited System Access
Only staff whose role needs your details can open them, and every lookup is recorded, so we can answer questions about who viewed a record and when.
Answering Requests
You can ask what we hold, why we hold it and who it has gone to. We aim to reply within thirty days and say straight away if a request needs longer.
Same Rules Across Every Page
Our terms, cookies and privacy pages are built from one shared set of definitions, so a word like account or transaction means the same thing whichever page you...
| Shared Definitions | Terms, cookies and privacy pages draw on the same short list of definitions, so you never have to work out whether a word means something different on the page you just left. |
|---|---|
| Linked, Not Copied | Where a sibling page covers the same ground we point you to it rather than writing a second version, which leaves one description to keep accurate and no quiet divergence. |
| One Change Date | When a definition moves, every page that relies on it is updated in the same pass, so the revision dates change together instead of drifting apart. |
| Cookie Page Tie-In | The cookie page lists the tags that run in your browser, and everything it names is described here in terms of what we do with the data those tags produce. |
| Terms Overlap | Account suspension and closure sit in our terms page. This policy covers only which records we keep afterwards, for how long, and how to ask for a copy. |
| No Conflicting Wording | If two pages say different things about the same record, this page wins for data handling and the other page is corrected at its next revision. |
| Version History | Each sibling page keeps its own revision log under the same numbering, so comparing two dates tells you which wording was live on the day you need it. |
How This Page Is Laid Out
We keep the layout plain so you can reach a clause without scrolling through decoration. Headed blocks sit in a fixed order, the chips above the first heading...