Terms page
The terms page explains account rights, access conditions and conduct rules. This legal page points you there when a question depends on the main contract wording.
Clear account terms, regional access wording, privacy references and dispute routes sit here so you know the legal ground before you open your account. We explain how 4...
Our legal page sets out how 4 game presents account terms for Pakistan without making blanket access promises. Availability can depend on your location, identity checks, device signals, payment rail status and local rules, so we use phrases such as supported regions and where local law permits. The terms also explain what records we may keep when you create an account, request
a payout, ask support for help or raise a dispute. References to JazzCash, Easypaisa, SadaPay and Raast appear as account-context chips, not as a promise that every route is open at every moment. If a policy clause conflicts with a newer notice shown inside your account area, we treat the newer dated wording as the current version until the page is refreshed.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
We write legal pages from the operator side, not as generic copy. That means each clause links to a real account process: registration checks, payment rail records, session...
Each major clause has an internal owner, such as account security, finance operations or support. That owner confirms the wording...
We avoid copying broad international phrasing where a Pakistan detail matters. Local rail names, supported regions and account verification wording...
When a legal page changes, we keep the dated version internally. That helps us answer questions about what wording applied...
We use conditional access wording because laws and rail availability can differ by place. Phrases such as supported regions help...
Legal clauses mention identity checks, login controls and record keeping only where they affect your rights or our duties. We...
We keep clause wording direct so you can read it before joining. If a term must use legal language, we...
This legal page works with our other policy pages rather than replacing them. The terms set the contract frame, while privacy, cookies, offers and account rules add detail in their own areas...
The terms page explains account rights, access conditions and conduct rules. This legal page points you there when a question depends on the main contract wording.
Privacy wording covers personal data handling, identity checks and record retention. We align legal clauses with that page whenever account documents or transaction records are involved.
Cookie wording explains browser storage, analytics tags and session tools. Legal text refers to those tools only when they affect consent, access or account security.
Offer rules sit beside the main terms and may add conditions for rewards. We keep expiry wording, eligibility rules and account restrictions consistent across those pages.
Closure wording explains how account balances, open disputes and retained records are handled. Legal clauses direct you to the right contact route before action is taken.
Dispute wording sets out what evidence to send and how we respond. This page keeps the route visible so legal questions do not get lost in general chat.
Regional access wording explains supported regions and local law limits. We keep that language consistent across login notices, account terms and payment rail references.
The legal page layout is built to help you find binding wording quickly. We use visible markers for clause groups, dated updates, contact steps, regional wording...
Clause cards group related legal points, such as account access, verification and dispute handling. Each card keeps the binding idea close to the action it affects.
The date strip shows when the legal wording was last changed. If you contact us, quote that date so we can match your question to the right version.
Context chips mark whether a clause relates to access, records, transactions or support. They help you scan the page without turning the policy into a sales page.
The contact block keeps legal email, chat handoff and account message routes together. That reduces confusion when your question needs a written answer rather than quick chat.
The jurisdiction line reminds you that access is subject to supported regions and local law. We place it near account-opening wording to avoid unclear expectations.
The footer links sibling policy pages that may affect the same account action. It is there so you can move between terms, privacy and dispute wording easily.