Terms of Use
This page — the primary terms governing account creation, use, and closure
388 games operates under a clear policy structure so you know exactly what governs your account, your transactions, and your activity on our platform. These terms apply to...
By opening an account with 388 games, you agree to the terms set out on this page, which apply to all activity conducted where local law permits. Our policy covers how your personal data is stored, how transactions processed through JazzCash, Easypaisa, SadaPay and Raast are recorded, and how disputes are handled. Account access is limited to individuals who meet the eligibility
criteria applicable in their supported region. We update these terms periodically; continued use of your account following any update constitutes acceptance of the revised policy. If you disagree with any part of these terms, the appropriate step is to contact our support team before continuing to use the platform.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
If any section of our terms raises a question or you need clarification on how a specific policy applies to your account, our support team is the right starting point. We aim to respond to policy-related queries within one business day.
Our live chat channel is open around the clock. Send a message describing your policy question and an agent will walk you through the relevant terms section that applies to your account situation.
Write to our support address for formal policy queries or to request a copy of the terms applicable to your account region. We keep written records of all policy correspondence for your reference.
Our help centre carries a dedicated legal section where you can read the current version of each policy document, including our privacy notice, cookie policy, and account-use conditions.
Our legal documents are written by people who operate this platform day to day, which means the terms reflect how the system actually works rather than how a generic template describes it.
We write our terms in plain English so you can read them without a legal background. Where technical language is unavoidable, we include a short explanation alongside the formal clause so nothing is left ambiguous.
Our policy team reviews all legal documents on a scheduled basis. Any change that materially affects your account rights is communicated directly before it takes effect, not buried in a footer update.
Our terms account for the payment landscape in Pakistan. References to JazzCash, Easypaisa, SadaPay and Raast are built into the transaction clauses rather than added as footnotes to a generic template.
We specify exactly which data categories we collect, how long we retain them, and under what circumstances we would share them. You can request a copy of your account data at any time through the support channel.
Two-step verification and session-timeout policies are documented in the security section of our terms. These are not optional features — they are platform-wide standards applied to every account we operate.
Our dispute process has defined timelines: acknowledgement within 48 hours, initial assessment within five working days, and a final written response within 21 days. These timelines are binding on our team.
Our legal section is structured so each policy document covers a distinct area without overlap. This page covers the main terms of use; sibling pages address privacy, cookies, and payments separately so...
This page — the primary terms governing account creation, use, and closure
How we collect, store, and process personal data tied to your account
Which cookies we place, why we place them, and how you manage your preferences
Transaction rules specific to JazzCash, Easypaisa, SadaPay and Raast processing
Eligibility, verification, and the conditions under which accounts may be reviewed
Timelines and identity checks that apply when funds leave your account
A dated record of material changes made to any policy document in the current year
The structure of our legal section reflects how we actually run the platform — each document maps to a real operational area rather than serving as a catch-all...