Shared Definitions
Terms, privacy notice and cookie page share one definitions block, so a phrase such as supported region carries the same meaning wherever you read it.
Every rule that shapes your account sits on this page. You can read the terms you accept when you join, the privacy wording that covers your details, and...
We draft this policy for supported regions and apply it where local law permits, so the terms you see can differ from one country to the next. If you are in Pakistan you get the version that matches the rules in force here, including how we handle your registration details, payment records from JazzCash, Easypaisa, SadaPay and Raast, and your account activity.
Where a clause cannot operate in your area we say so rather than leaving it to interpretation. You are responsible for confirming that using the platform is allowed where you are. Changes carry a dated version number, and continuing to use your account after a published update means you accept the revised wording.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Policy text is only useful if you can act on it, so we hold the drafting rules fixed. Clauses get a plain-word pass, a jurisdiction check and a dated version stamp before...
We write clauses in everyday English rather than copied legal boilerplate, so you can work out what a rule means for your account without hiring anyone to translate it.
Each policy page carries a version number and a change date. Older versions stay in the archive, so you can compare what applied when you joined with what applies today.
Before a policy goes live we check it against the rules applying in each region we serve, and we flag any clause that only operates in part of that footprint.
Records tied to your registration, including payment references from JazzCash, Easypaisa, SadaPay and Raast, are held under the retention and access terms printed on the privacy page.
Changes take effect on the date shown in the page header, never backwards for conduct that happened earlier, so you always know which rule covered which period.
If a first reply does not settle your point, ask for it to be escalated and a senior member of the policy desk picks it up within two working days.
The policy pages on this site are written and updated as one set rather than as documents that drift apart. Dates, definitions, contact routes and jurisdiction lines are checked together, so you...
Terms, privacy notice and cookie page share one definitions block, so a phrase such as supported region carries the same meaning wherever you read it.
Whenever one policy page is updated we check the sibling pages the same week, so effective dates never contradict each other or leave a gap in the record.
The support routes listed on each policy page are the same three you find here, so you never hunt for a different address depending on the page you landed on.
Every page repeats the same jurisdiction wording, so access rules, offer conditions and privacy clauses all point to one regional test rather than competing descriptions.
References to JazzCash, Easypaisa, SadaPay and Raast read identically across pages, avoiding the confusion that comes from one page calling a rail settled and another calling it pending.
A single change log records edits to all policy pages in order, letting you follow what moved, when it moved, and whether anything you agreed to was affected.
Sibling pages are drafted to the same reading level and paragraph length, so moving from the terms to the privacy notice does not feel like switching to a different site.
The policy pages share one layout so you can find a clause quickly on a phone or a desktop. Each page opens with a summary box, runs a...