LEGAL REFERENCE

Your Data And How We Guard It

Every account you open with us comes with clear promises about your data. This page sets out what we hold when you register, why we keep it, and...

Plain English WordingCookie ChoicesSupport In Pakistan Time
999p game Your Data And How We Guard It

Where This Policy Applies

Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.

REACHING OUR DESK

How To Contact Our Privacy Desk

Questions about your data should never sit unanswered. Our team reads every message sent through live chat inside your account, and mailbox...

Live Chat Open your account and start a chat whenever...
Policy Mailbox For anything you want in writing, such as...
Account Inbox Notices about changes to this policy arrive in...
WHY YOU CAN CHECK

Signals Behind Our Policy Wording

We keep our wording close to how our systems behave, name the regional partners that handle wallet traffic, and publish changes instead of slipping them past you. The staff who write and...

Stated Sources

Every data claim here traces to something we can point at, whether that is our account records, a regional payment partner rule, or a local requirement in Pakistan.

Plain Language

You should not need a lawyer to read a privacy page. Sentences stay short, headings explain what is coming, and unfamiliar terms are explained on first use.

Named Partners

Payment handling is not a mystery. Wallet traffic through JazzCash, Easypaisa, SadaPay, NayaPay and Raast moves under regional partner rules, and we say which entity touches your details.

Account Security

Access uses encrypted connections, session checks and optional two-step verification. We log each sign-in, so odd activity can be spotted and you can see where your account was opened.

Change Dates

Every revision carries a number and a date. Compare the page you are reading with one you saved earlier and the label tells you which wording was in force.

Support Hours

Our desk answers between 9am and 11pm Pakistan time, seven days a week, because questions about your own data rarely arrive at a convenient moment for the person asking.

SAME TERMS EVERYWHERE

One Standard Across Every Page

Whether you read this page, our account terms or the notice shown at registration, the same definitions apply and the same partners are named. Where a companion page covers a related subject...

01

Shared Definitions

Terms such as account data, payment detail and retention period mean the same thing on every page we publish, so you never guess which version covers your case.

02

Matching Contact Routes

The chat window, mailbox and account inbox listed here are the same routes named in our terms, which keeps support from sending you in circles between different teams.

03

Aligned Wallet Rules

JazzCash, Easypaisa, SadaPay, NayaPay and Raast references stay consistent wherever they appear, so the partner handling your transfer is the same one named elsewhere on our site.

04

No Hidden Additions

Nothing important about your data lives only in a footnote somewhere else. If a rule matters to you, it appears here in full, in the same plain wording used across the rest.

05

Version Labels

Each revision carries a number and a date. When you compare this page with an older copy you saved, the label tells you which of the two you are reading.

06

Linked Companions

Where a companion page covers a related subject in more depth, we send you there instead of stretching this page thin and repeating half of the same sentences twice.

07

Report A Clash

If two of our pages ever disagree, write to the privacy desk and flag the section. We treat that as a wording fault and correct the older text straight away.

Layout Choices Inside This Policy

This page is built to be skimmed before it is read. Quick summaries open each block, longer clauses sit inside expandable panels, and every heading answers...

Summary Blocks

Every section opens with a short recap you can read in seconds, so you get the gist of our data practice without working through the full clause beneath it.

Expandable Clauses

Tap a heading and the detailed wording unfolds in place. Nothing hides behind a download, and you can move between summaries and full clauses without losing your spot.

Colour Coding

Green labels mark data we collect directly, amber marks details shared with our regional partners, and grey covers retention. The scheme stays identical on every page you visit.

Deadline Flags

When a clause carries a cut-off, such as a window to object to a change, a small flag sits beside the heading so the timing does not slip past you.

Downloadable Copy

From account settings you can save the current wording as a file, which helps when you want to compare it later or keep a record of what applied.

Listen Instead

A built-in reader plays each section aloud in clear English, useful if you are on a small screen. It follows the same headings you see as you scroll down the page.

Questions We Hear Most Often

We hold the details you type at registration, your verified contact points, and records of how you use the lobby. Payment references from JazzCash, Easypaisa, SadaPay and Raast sit with regional partners.

Ask through live chat or the mailbox and we send a copy of your account record within the period our regional rules allow, once we confirm it is you asking.

Retention windows differ by record type. Account data lives while your account is open, transaction references follow the timelines our wallet partners set, and marketing preferences drop away once you opt out.

Only with parties who help us run the service, such as regional payment partners and the studios that supply our tables. Your record is never sold to outside list builders.

Send the correction through your account inbox or live chat. Once we verify the change, updated details flow to every system we hold, and you can check the result on your profile.

Your profile is deactivated straight away. Records that regional rules require us to keep, mainly transaction history, are stored securely for their set period and then deleted on schedule.