Shared Clause Numbering
Clause numbers here match the numbering on our privacy and account pages, so you can cross-reference one rule without reading the same text twice over.
Our terms, account rules and jurisdiction wording sit on this page so you know exactly what applies where local law permits. Read it once, open your account, and...
This notice explains which terms apply to you depending on where your account is opened and used. Access is offered in supported regions, and where local law permits, one consistent rule set governs your sign-in, your lobby activity and every withdrawal you request. If a single clause cannot operate in your jurisdiction, the remainder of the notice stays in force and we
set out which part changes. You accept these terms by using your account, and we publish updates on this page under a revised date so older wording stays comparable. Nothing here overrides rights you hold under the rules of your own jurisdiction. Anything unclear about the rails in the chips below belongs with the policy desk.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Terms pages earn their place only when you can verify them yourself. We date every revision, keep previous wording reachable behind a link, and write obligations in short...
Every update carries a revision date near the heading, so you can see what changed and when without reading the...
Obligations are written in short sentences instead of dense legal phrasing, so you can read a clause once and know...
These clauses are drafted and maintained by the same people who run account access, verification and withdrawal handling for Pakistan...
JazzCash, Easypaisa, SadaPay, NayaPay and Raast are described using the same terminology our operational teams use when they process requests...
The notice says which regions we serve and how wording shifts where local law permits, so you know what applies...
Sign-in checks, device verification and account recovery are described the way they are actually enforced, so nothing here surprises you...
Policy pages sit inside one system, not seven separate documents. Clause numbering, version headers and the policy inbox address are shared with our privacy and account pages, so cross-checking a rule takes...
Clause numbers here match the numbering on our privacy and account pages, so you can cross-reference one rule without reading the same text twice over.
Every policy page opens with the same version header and revision date, which tells you at a glance whether two documents were updated in the same pass.
The policy inbox printed here is the same address shown on our other policy pages, so you never have to chase a different channel for a terms question.
Eligibility, verification steps and device rules are worded identically wherever they appear, so the page you read first stays true on the ones you open later.
Mentions of JazzCash, Easypaisa, SadaPay, NayaPay and Raast keep one phrasing across policy pages, which keeps withdrawal wording unambiguous for Pakistani accounts.
Where we serve Pakistani accounts, each policy page carries the same supported-regions clause, so access rules never contradict each other across documents.
When a clause changes, the change is logged on every affected policy page at the same time, and the revision date moves with it rather than drifting apart.
This layout is deliberately familiar if you have read any other policy page of ours. Clause blocks sit under dated headers, a chip row names the local rails...