Terms of Use Page
Our terms and this policy share the same definitions of account holder and account activity, so a phrase you read here carries the same meaning there.
This page is where we set out what we collect when you open an account, how your Pakistani transfer records sit in our systems, and the choices you...
Your privacy is your business, and this policy explains how we handle it. We collect only what we need to run your account: your name, contact details, date of birth, and the payment references behind JazzCash, Easypaisa, SadaPay and Raast transfers. Where local law permits, we also log device and session data so we can spot an unusual sign-in before it costs
you money. We keep records for the periods Pakistani rules require, then delete or anonymise them. You can ask what we hold, correct anything inaccurate, or withdraw consent for marketing messages whenever you like by writing to our privacy desk. Because data rules differ between regions, some options vary depending on where you open your account and which payment rail you use.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
We would rather be held to something checkable than ask you to take our word for it. The habits below decide how this policy gets written, dated and stored, and each one...
One accountable person signs off every change to this policy, so a question has an owner instead of a queue. Ask for them by name at the privacy desk.
Each amendment carries a date and a short reason, and we email account holders before a material change takes effect. Older wording stays readable so you can compare.
Account and transfer data sits in encrypted storage, and access is limited to staff who need it for support or payment checks. Idle sessions time out on their own.
Our audit team samples consent records and deletion jobs every quarter, then reports to the privacy contact. Findings shape the wording of the next policy update.
Clauses are written for readers rather than lawyers and checked by Pakistan-based staff before publishing. If a sentence needs two reads, we rewrite it.
We name the processors who see your data, such as payment partners and hosting providers, and say what each one does. The list changes whenever a partner does.
This policy does not stand alone. It shares definitions, retention periods and contact routes with the other pages that govern your account, so you never have to guess which document wins when...
Our terms and this policy share the same definitions of account holder and account activity, so a phrase you read here carries the same meaning there.
The cookie categories listed there match the consent switches described here. Turn a category off there and the record of your choices here updates too.
Payout timing depends on the rail you used, whether JazzCash, Easypaisa, SadaPay or Raast, and the data we must retain matches the periods stated here.
Restrictions on holding multiple accounts lean on the same identity checks set out in this policy, so the two pages never disagree about what we verify.
Escalation steps end with the same privacy contact named here, which means a data complaint and a service complaint reach one desk in the same order.
Sign-in alerts, device records and session limits are described in both places, and this policy explains what data those protections generate and store.
Where we publish translations of sister pages, this policy is translated alongside them, and the English wording at this address remains the copy we stand behind.
How a policy page is laid out decides whether anyone actually reads it. These are the pieces we build in so you can find consent, retention and access...