Terms and conditions
Defines your account relationship while this policy handles the data side of it. Both pages use the same words for account, balance and closure.
This page sets out what we collect when you open an account, how your JazzCash, Easypaisa, SadaPay and Raast details are treated, and what you can ask us...
Think of this page as the agreement behind your account. We collect only what running it needs — your name, contact details and a record of which payment rail you used — and we explain each reason in plain words. Where local law permits, some processing happens because a payment partner or a regulator asks for it. Where it does not, we
say so rather than burying the point in a footnote.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Questions about your data do not need a ticket number. Open live chat from inside your account and the privacy desk picks it up during support hours, seven days a week. If you would rather write it out, email works just as well — either route reaches the same small team.
Open chat from your account and the privacy desk picks up your question during our daily support window. Most account-data requests get a same-day reply.
Write to our support address with your registered number and a short description of what you need. We confirm receipt, then come back with the answer in writing.
Request a copy of your account data straight from the settings area. The request lands with the privacy team, and you can follow its progress without sending a second message.
We wrote this ourselves and we keep it current. Payment rails are named exactly as you see them in the cashier, support hours match the hours we staff...
Our own team drafts and maintains this policy, working from the same operating documents that our support and payments staff...
JazzCash, Easypaisa, SadaPay and Raast appear by name so you can match each line of the policy to the option...
Every update carries the date it took effect and a short summary of what moved, so you can trace older...
The response windows described here match the hours our chat and email desks are staffed, so nothing on this page...
Where a rule applies only in supported regions, we name the region instead of stating it as a blanket condition.
Account access runs over encrypted connections, and staff data views are limited to the account they are handling at the...
One account, one set of rules. The wording here uses the same terms you meet on our terms page, our account rules and our contact page, so a phrase means the same...
Defines your account relationship while this policy handles the data side of it. Both pages use the same words for account, balance and closure.
Describes how access works. The security wording matches this page, so nothing contradicts when you move between the two.
Lists JazzCash, Easypaisa, SadaPay and Raast timing. Data-retention wording for those records stays identical here.
Shows the same chat, email and in-app routes you send data requests through, with matching support hours.
Records each amendment by date. Policy updates carry the same dates, so you can cross-check the two in one glance.
Explains how to correct your account details. The process described is the one this page refers to for data changes.
Confirms the reading options we support, including text scaling and screen-reader structure, applied to this policy too.
The layout is built for skimming first, reading second. The opening summary panel sits above the fold, jump links run down the side, and a dated...
The opening block condenses the whole policy into a few lines, so you can decide in seconds whether you need to read further.
Section links let you move straight to data we hold, retention, your choices or contact routes without scrolling through everything between.
A dated stamp sits beside the headline and changes whenever the wording does, so you always know which version you are reading.
Chat, email and in-app request routes repeat near the foot of the page, with the hours we are staffed listed alongside them.
Points that depend on where you are appear as short labelled blocks, so Pakistani readers see the rules that apply to them first.
A print view strips the navigation and keeps the text, letting you save a clean copy of the version that applied on the day you read it.