Terms page
The main terms page holds the account rules, and this legal page repeats the same definitions so a phrase means one thing wherever you meet it.
Every rule that shapes your ace778 game account sits on this page, from the details you give when you join to the way we close an account. We...
Access to ace778 game is offered only where local law permits, and the terms on this page apply whenever you use our lobby from a supported region. Where a rule in your jurisdiction differs from what we publish, the local requirement takes priority for your account. Our policy sets out four things: who may hold an account, how your details are stored,
how disputes are handled, and how we close an account when terms are breached. The payment names below appear as context chips so you can see which rails our wording references; they are not an invitation to deposit from a region where a rail is unavailable to you. If one clause is later found unenforceable, the rest stay in force, and we
flag any material change inside your account before it applies.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Questions about a clause, a closure decision or a data request come straight to our policy desk through the in-app thread, email or a scheduled call-back. We answer in English and keep every exchange logged against your account, so you can point back to it later.
Open the help tab inside your account and choose Terms, so your message lands with the team that drafts our policy wording rather than a general chat queue.
Write to our published policy address and you get a written answer, usually the same working day, covering the clause number and the effect on your account.
Pick a slot in the app and a policy advisor rings your Pakistani number to talk through closures, data requests or wording you think is unclear.
Every clause here is checked against the flow you actually go through when you join, move money or close an account. We revise the wording when a payment rail or a supported...
We rewrite any clause that needs a second read, and we test each version with readers in Pakistan before it goes live, so the wording matches how you speak.
Every published version carries the date it took effect and a short list of what moved, so you can compare this page against the copy you saved earlier.
Our terms sit with named team members who answer for the wording, and their contact route is listed here rather than buried inside a general help queue.
We publish the full text on this page instead of splitting obligations across separate documents, so nothing you agreed to sits outside the screen you are reading.
When material wording changes, a message reaches your account before the new version applies, and you can close the account if you disagree with it.
Before a section goes live we test how it interacts with the rules of each supported region, and we set out where a local requirement takes priority over our own text.
The wording you read here should not change meaning when you move to our privacy, cookies, withdrawal or fair-play pages. One drafting standard runs across all of them, and the same definitions...
The main terms page holds the account rules, and this legal page repeats the same definitions so a phrase means one thing wherever you meet it.
Data handling is described in the same sentence shape as our account clauses, so you can track how a detail you give us travels through the platform.
Cookie wording uses identical definitions for account, session and device, which keeps the two documents comparable side by side on a phone screen.
Cash-out timing, verification steps and bank-rail wording match the clauses here, so nothing about JazzCash, Easypaisa, SadaPay or Raast shifts meaning between pages.
Rules covering in-play conduct, account suspension and market settlement follow the same clause numbering, which makes any cross-reference easy to follow.
Our complaints route ties back to the dispute clause on this page, and both screens list the same response windows so your expectations stay steady.
Each update is logged once and linked from every policy screen, so a reader arriving from search sees the same revision history as someone already signed in.
The layout on this side of the site follows a single pattern. A short index sits at the top, the effective-date marker follows, and each clause opens with...