Understanding the Details We Hold About You
Opening an account with us starts a record, and this page explains that record in plain terms. You will see which details we keep, why we keep them...
How We Collect, Store and Share Your Details
We collect only what an account needs to run: the identity details you type in, the mobile number you verify, and a record of every funding action you take through JazzCash, Easypaisa, SadaPay, NayaPay or Raast. That record keeps your balance, payout requests and support conversations matched up. We store it on encrypted systems and limit access to the teams handling accounts,
payments and security. We do not sell your profile, and we pass details to a payment partner only to complete the action you asked for. How long a record stays with us depends on the rules for your region, and some jurisdictions require transaction history to be held for a set period after an account closes. Where local law permits, you can
ask for a copy of your details, request a correction, or ask us to delete anything we are not required to keep. Local law takes priority wherever it differs from this page.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Reaching Us About Your Account Data
If you want a copy of your details, need something corrected, or want to know why a particular record exists, our account team answers those requests directly. Live chat is open around the clock, and email replies usually land within one working day.
Live Chat
Open chat from your signed-in account and an agent pulls up your profile while you talk. Most requests, from a copy of your record to a correction, get answered in that same session.
Privacy Email
Write to our privacy desk and we reply within one working day. Include the mobile number registered on your profile so we can match the request to the right account before releasing anything.
Profile Settings
Inside your account you can change your contact number, update your address and switch off optional messages without waiting on anyone. Anything you cannot change yourself, we handle through chat.
The Standards Behind This Policy
We wrote this page the way we would want to read one: short sentences, no buried clauses and no vague promises. Everything here matches what actually happens inside your account, and every...
Recognised Funding Routes
Every funding path named in this policy is one you already know, from JazzCash and Easypaisa to SadaPay, NayaPay and Raast. No anonymous processor sits between your wallet and your account record.
Plain-Language Drafting
Our clauses avoid legal padding. Anything that needs a second reading gets rewritten before it goes live, because a sentence you cannot follow is a sentence you cannot rely on.
Dated Revisions
Each revision carries the day it took effect, so you can tell which terms applied when you signed in and what changed afterwards without hunting through an archive.
Logged Internal Access
Only our account, funding and security teams can open a customer profile, and every look-up is recorded against a staff login name. Nobody browses records out of curiosity.
No Profile Selling
We do not trade your details with advertisers or data brokers. Your file leaves our systems only when a payment partner or verification step needs it to finish the request you made.
Regional Rule Watch
We follow the requirements that apply in each region we support, including Pakistan, and adjust retention and reporting whenever those requirements change. That work runs quietly in the background.
The Same Promises on Every Policy Page
Every policy page we publish uses the same definitions, the same retention language and the same contact routes. When one document changes, the others follow on the same...
| Account Terms | The definition of an account holder on our terms page matches the one used here, so the same rules apply whether you are reading about access or about data handling. |
|---|---|
| Cookie Notice | Tracking tools named in the cookie notice appear in this policy too, with the same explanation of what each one does and how you switch optional ones off. |
| Funding Rules | Payment clauses sit in one place and this page points to them rather than repeating them, so the two documents never drift apart after an update on either side. |
| Verification Steps | The documents you upload and the checks we run are described the same way on the verification page and in the collection section above, with matching retention rules. |
| Complaints Route | If something goes wrong, the escalation path printed on our complaints page is the same one that handles privacy requests, so you are never sent between two different desks. |
| Language Versions | Where a page is offered in more than one language, the English text you are reading now governs, and the other versions are updated from it at the same time. |
| Change Notices | When we revise a promise, the update lands on every related page on the same day, and the date stamp at the head of each one changes with it. |
Built to Be Read on Any Screen
We laid this page out so the section you need is never more than a tap away. Headings are numbered, key clauses sit in their own...
Jump Bar
The tab strip under the headline lets you move straight to retention, sharing or contact clauses without scrolling through the whole page on a handset screen.
Summary Cards
Each clause opens with a short panel in everyday English before the formal wording, so you can grasp the point before you read the detail underneath.
Date Stamp
The effective date sits at the head rather than in a footnote, which means you always know which version of the policy applied on the day you signed in.
Funding Rails Row
The chip row lists JazzCash, Easypaisa, SadaPay, NayaPay and Raast so you can see which Pakistani routes the data clauses actually refer to at a glance.
Expandable Clauses
Longer sections stay folded until you tap them, which keeps the page short on a phone while the full text remains one gesture away whenever you want it.
Save and Share
A print-friendly layout and a share link mean you can keep a copy of the policy in your own files or send it to someone who reads it with you.