Terms
The terms page carries the main account contract, while this Legal page explains the posture behind it. Together they define eligibility, account duties, and rule acceptance before use.
5yyy places the Legal page beside your account journey: eligibility wording, access rules where local law permits, verification duties, and payout-rule context for JazzCash, Easypaisa, SadaPay and Raast...
Our legal wording is written for account use in supported regions of Pakistan, while access remains subject to where local law permits. We describe what you accept when you create an account, how we may verify identity, how account activity can be checked, and when payout requests may be held for compliance checks. This page is not legal advice, and it does
not replace local rules that may apply to you. Payment channels are named only as account-flow context, because JazzCash, Easypaisa, SadaPay and Raast can carry records that help us match transactions, resolve disputes, and keep account balances tied to the correct person.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Policy edits are handled with version control, plain wording checks, and operational sign-off before publication. We look at whether a clause matches account handling, payout verification, support routing, and access wording for...
Each legal page carries a current version date so you can see when wording changed. We keep older internal copies to help support compare a dispute against the clause in force.
We avoid hiding account duties behind heavy legal phrasing. Where a clause affects access, verification, or payouts, we explain the practical effect in direct Pakistani English.
Before a policy update goes live, account, payments, and support teams check that the wording matches how cases are actually handled inside 5yyy.
Pakistan access statements use supported-region language and refer to where local law permits. We avoid broad promises that could conflict with different local rules.
Legal clauses about account control connect with our security process, including login checks, device flags, and document requests when account ownership needs confirmation.
When a legal update affects your account duties, we aim to place the wording where you can see it before continuing with account actions.
The Legal page works with our sibling policy pages rather than repeating every clause in one place. We align wording across terms, privacy, cookies, promotions, verification, and account closure so one page...
The terms page carries the main account contract, while this Legal page explains the posture behind it. Together they define eligibility, account duties, and rule acceptance before use.
Privacy wording explains how data is collected and used. The Legal page connects that data handling to verification, dispute checks, account safety, and lawful record keeping.
Cookie wording covers device identifiers and session tools. Legal wording explains why those records may matter when account access, fraud checks, or support evidence is questioned.
Verification clauses explain when we may ask for documents or transaction proof. Legal wording sets the account consequences if required checks are incomplete or inconsistent.
Payout wording explains timing and review steps for account withdrawals. The Legal page states why checks may be required before funds leave a 5yyy balance.
Promo wording sets conditions for offers visible on your account. Legal wording explains that published terms, eligibility rules, and abuse checks apply before any reward is credited.
Account closure wording covers how access ends and what records remain. Legal wording explains why some records may stay available for disputes, audits, or lawful requests.
The legal layout is built to help you spot binding wording quickly, not to bury clauses behind decorative content. We use short markers, dated sections, and direct labels...