Terms of use
The account terms set the contract, while this page explains how the data behind that account is handled. Read together, they stay consistent from sign-up to closure.
We keep this page plain: your account data stays with us unless a payment check or verification step genuinely needs it, and you can ask what we hold...
Where local law permits, we collect only what keeps an account running: your name, mobile number, date of birth, the wallet or bank reference behind each top-up, and basic device signals such as browser type and IP region. JazzCash, Easypaisa, SadaPay and Raast settle through licensed payment partners, so full instrument numbers never rest on our servers — we keep a transaction
reference, an amount, a timestamp and a status. Access sits with the teams that resolve payment queries and, where a regulator or court order requires disclosure, with the authority that asked. Supported regions follow their own rules, and if a local rule bars a practice we switch it off rather than ask you to accept it. You can request a copy or
deletion of your records through our privacy desk.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Privacy copy here is owned, not outsourced. A named policy owner walks every clause each quarter against how the platform actually behaves — payment flows, verification steps, support...
One named lead signs off every change to this page and answers for how the wording matches what our systems...
Four times a year we test each clause against live platform behaviour, then publish a revision stamp. Anything that no...
Payment partners handle settlement data under contract and we audit what they return to us. We never hand your contact...
Every internal view of your account leaves a trace with a name, a timestamp and a reason. Spot checks run...
Active accounts keep records for as long as the account lives. Closed accounts move to a shorter window, then get...
We track privacy and payment rules across the regions we support, so a change in one market updates the practice...
This page never argues with our other policy pages. Where a sibling page covers the same ground, the wording matches and only the level of detail changes. If you spot a clash...
The account terms set the contract, while this page explains how the data behind that account is handled. Read together, they stay consistent from sign-up to closure.
Promo conditions use the same definitions for eligibility, verification and record keeping, so a rule that applies to an entry also applies to the data we keep for it.
Verification pages list which documents we ask for; here we cover how those documents are stored, who can open them and when they leave our systems.
Cookie choices and the consent banner follow the retention logic described here, so switching a preference off in one place holds everywhere else on the platform.
Settlement pages describe timing and references, while this page explains the data trail those references create and how long we hold it for reconciliation and disputes.
The app pages list supported devices and updates; here we explain the device signals we read, such as browser type and region, and why we keep them short-lived.
Complaint handling shares the escalation ladder used for privacy requests, so a data concern needing a second look reaches the policy owner through the route described here.
We built this page to be read once and understood, not skimmed and forgotten. Short blocks, plain headings and a chip row for each settlement route mean you...