Account opening terms
The sign-up page lists the same identity documents you will later ask us about here, so nothing arrives as a surprise.
Your account holds personal details, and this page explains exactly how we handle them. We set out what we record when you register with a Pakistani mobile number...
Where local law permits, we collect only what an account needs: your name, contact details, date of birth, device and sign-in records, and the transaction references our Pakistani payment partners return to us. We keep that data to run your account, confirm withdrawals, answer support tickets, and meet the record-keeping duties that apply in the supported regions we serve. We do not
sell your personal details to outside advertisers. Retention follows the rules of the region you register from, and if you close your account we erase what we no longer need while archiving the rest for the period local authorities require. You can ask what we hold, request a copy, or ask for a correction at any time.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
This notice is published under our own name because the rules around personal data keep shifting and you deserve wording that tracks them. Our compliance and platform teams read every clause together...
A single data protection lead signs off every revision, so you always know which desk answers for how your records are handled across Pakistan.
Each amendment carries a revision date at the foot of the page, so you can compare last month's text with today's wording.
Legal clauses sit beside everyday explanations, so you can grasp how long a record is stored without needing a lawyer to translate the sentence.
JazzCash, Easypaisa, SadaPay and Raast processing runs behind contracts that restrict what those partners may do with the references they receive about your transfers.
Ask and we will show the record types we hold for your account, listed by category rather than buried in legal phrasing you cannot act on.
Privacy requests are answered daily from 9am to 1am Pakistan time, and anything sent overnight is queued for the morning shift rather than left unread.
This page has to agree with the wording you find elsewhere on our site, so we treat it as one document set rather than seven loose pages. Terms, account opening, withdrawals and...
The sign-up page lists the same identity documents you will later ask us about here, so nothing arrives as a surprise.
Timelines quoted on our cashier pages match the retention wording in this notice, because both describe the same transaction trail.
Device and session records described in our cookie notice use the identical definitions you find in the section above.
Every legal page is written for Pakistani readers in English, matching the language our chat desk uses when you raise a data question.
Wherever this page mentions supported regions, our sibling pages carry the same qualifier, so you get one consistent answer.
Chat, email and account tools listed here are the same routes named in our terms, so one request reaches one team.
A single publishing calendar governs every legal page, keeping the revision date at the foot of each one aligned.
Nothing here hides behind a tab or a dropdown, and that is deliberate. You get the same policy text on a phone, a tablet or a...
A short card above condenses the notice into the handful of points that matter to you before the numbered clauses begin.
Each heading names the record type it covers, so you can jump straight to device logs, identity checks or transaction history.
Chip labels show which Pakistani rails this notice refers to, so JazzCash, Easypaisa, SadaPay and Raast references are visible at a glance.
One short block explains how to raise a request and what happens next, including the reply window our desk works to.
Text reflows to fit a phone screen with readable type and tap targets, because most of you read pages like this while travelling.
The footer states when this wording last changed and links to the previous draft, so you can track what moved between versions.