Terms Of Use
The terms page covers what you agree to as an account holder. This policy covers what we do with the data that account generates.
When you open an account with us, this page sets out what 977pak game collects, why we hold it and how you reach it at any time. Access...
We wrote this policy to match how the platform runs day to day, not to fill a template. It covers the account details you give us, the payment references we receive when you send funds through JazzCash, Easypaisa, SadaPay, NayaPay or Raast, the device and connection data our systems record, and the support conversations you start with our team. Where local law
grants you stronger rights than a clause here describes, those rights apply. Where local law restricts a practice, the restriction wins. Access runs in supported regions and only where local law permits. Every edit carries a date, because a policy that changes quietly is no policy at all.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Three people on our operations side own this text: one drafts, one checks it against how the platform actually behaves, and one signs off changes before they go live. We rewrite a...
A policy with no name behind it is hard to question. Ours lists the team responsible for data handling, so you know who to raise a concern with.
Every amendment carries the day it took effect and a short line about what moved, so you can tell whether an old clause still reads the same.
Clauses run in short sentences instead of legal padding. A policy you cannot follow is one you cannot agree to, so technical terms are explained in place.
Account access runs over encrypted connections, payment references sit masked on our systems, and staff who open customer records work from role-based permissions rather than unrestricted access.
You may hold an account from Pakistan or from a supported region beyond it, so we flag where a clause depends on local law instead of pretending one rule fits every market.
If a first reply does not settle your question, ask for the matter to be escalated. A senior team member takes it over and answers in writing, with the reasoning shown.
Our policy pages share one drafting standard, so a phrase you learn here means the same thing on the terms page, the cookie page and the account rules. Where a sibling page...
The terms page covers what you agree to as an account holder. This policy covers what we do with the data that account generates.
The cookie page lists each tag we set, its purpose and how long it stays on your device. Where a tag reaches our servers, the rule sits here.
Verification steps and access conditions are set out there in operational language. Retention rules for documents you upload sit in this policy, worded to match.
Payment pages explain how JazzCash, Easypaisa, SadaPay, NayaPay and Raast transfers reach us. This policy explains which references we keep and for how long.
The support page lists channels and hours. Contact routes for data requests repeat here so you are not sent hunting through a second page for the right inbox.
Promotion pages set out entry conditions. Personal details collected during an entry follow the same categories and retention periods described here, with no separate rulebook.
When a sibling page is updated we check whether this policy needs the same edit. Anyone who agreed to an older version sees what altered and when.
We laid this page out the way we lay out our lobby: the short version first, detail below in compact blocks, and nothing important hidden in a footnote...