Same definitions
The words we define on this legal page carry the same meaning on our privacy and payments pages, so account, wallet and session never shift between documents.
Every account here runs on one written set of terms, and the whole document sits on this page before you open anything. Read it once and you know...
This page states our legal posture rather than a promise of access. Whether you can hold an account depends on where you live and on the rules that apply there, so every clause that touches access is written as where local law permits or in supported regions. That wording is deliberate: it keeps the text accurate as regional rules move, and it
keeps our payment clauses tied to the rails you actually use. When a rule differs by province or by wallet, we say so inside the clause instead of hiding it in a footnote. Clauses are grouped so account, payment and complaint rules sit apart. If something here does not match how your account behaves, tell our terms desk and we will correct
the text and date the correction.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Legal text earns confidence by being checkable, not by being long. We name our payment rails, state our support hours in Pakistan Standard Time, and describe security steps exactly as they behave...
Every amendment to our terms carries a publication date and a short reason, so you can tell what changed, why it changed and when the new wording began to apply.
We write clauses in short sentences, define the words we rely on, and avoid phrasing that can be read two different ways in English or in Urdu translation.
Where a rule touches money, the clause names JazzCash, Easypaisa, SadaPay and Raast directly rather than referring to an unnamed wallet or a generic transfer.
Two-step login checks, session timeouts and device prompts are set out in the terms exactly as they behave inside your account, with no hidden conditions attached.
Contact windows, response targets and escalation steps appear alongside the hours we actually staff them, listed in Pakistan Standard Time rather than broad promises.
Our own team drafts each clause, a second reader tests it against how the platform really works, and corrections are published openly instead of being edited away quietly.
A rule scattered across pages is a rule you cannot rely on. Our sibling pages for privacy, payments and complaints reuse the same defined words, the same contact block and the same...
The words we define on this legal page carry the same meaning on our privacy and payments pages, so account, wallet and session never shift between documents.
JazzCash, Easypaisa, SadaPay, NayaPay and Raast are spelled identically in every policy, which keeps cross-referencing simple when one rule spans two pages.
Dates read day, month, year everywhere, and each amended clause shows the earlier and later publication date so nothing depends on your memory of the previous version.
One contact block serves all policy pages, so the address you use for a question about terms is the same address used for data or payments questions.
Phrases like where local law permits and supported regions are used identically across pages, never swapped for narrower or looser wording that would confuse access rules.
Verification and withdrawal windows are quoted in working days on every page that mentions them, so the legal text and the payments wording never disagree with each other.
Complaints move through one escalation path whichever policy page raised them, ending with a written answer from our compliance desk and a dated record of it.
The layout here is meant to be worked through, not skimmed once. A fixed index, numbered clauses, a defined-terms block and a visible effective date let you jump...