What Our Privacy Policy Covers
This policy explains what we collect when you open an account with 999b game, why we hold it, and how long it stays on file. You will see...
How We Handle Account Data
We shape this policy around the rules that apply where you use the service, so some clauses read differently depending on your region. Where local law permits, we hold account data for as long as your relationship with us is active, then archive only what tax and settlement rules require. We collect your name, contact details and settlement references for JazzCash, Easypaisa,
SadaPay, NayaPay and Raast, and never more than your account obligations need.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Who Checks Our Data Practices
Policy text only matters if someone follows it. Our compliance lead signs off every change, engineers log each look-up of an account record, and support managers spot-check closed tickets each month. You...
Named Policy Owner
One compliance lead owns this document from end to end, approves every wording change and answers questions from our support managers whenever a request or a regional rule is unclear.
Access Logging
Each look-up of your account record is stamped with a staff ID, a timestamp and a reason. Engineers working on our systems cannot read full payment credentials from internal tools.
Ticket Sampling
Every month our support managers pull a random set of closed data requests and check that the reply matched what we promise on this page, with anything short returned to the agent.
Dated Revisions
When a clause is edited we update the effective date in the header of this page and keep the earlier wording on file, so anyone can compare the two versions side by side.
Regional Mapping
Provinces and payment partners carry different retention periods, so each clause is mapped to the region it applies to instead of being written as one blanket rule for every visitor.
Open Contact Route
You never need an account manager to reach our policy desk. The email address and chat route shown above work for any account holder who wants an answer in writing.
Consistency Across Our Policy Pages
You will meet the same promises in our terms, cookie notice and payout pages, because all of them are drawn from one data map. If two documents ever...
| Terms of Use | Sets the account rules you accept when you join. It uses identical wording for account data, so a phrase you read there carries the same meaning on this page. |
|---|---|
| Cookie Notice | Covers the small files your browser keeps so the lobby remembers your language and your session. The retention windows it lists match the ones published on this page. |
| Payout Terms | Explains how withdrawal checks work with JazzCash, Easypaisa, SadaPay, NayaPay and Raast. The identity steps it describes are the same ones summarised in our clause on verification and timelines. |
| Security Page | Describes sign-in protection, device checks and how we would handle a suspected breach. Notification timelines there match the wording our compliance lead has signed off for this policy. |
| Offer Terms | Explains how promotional credit is tracked, when it expires and what we record while it is live. Those records follow the same retention rules as ordinary lobby activity on your account. |
| Support Charter | Lists how quickly we answer through chat and email. The response windows quoted there are the same ones our policy desk is measured against each month in internal reporting. |
| App Notice | Covers the device permissions our mobile build asks for, such as notifications and local storage. Nothing listed there falls outside the data map described on this page for account holders. |
What You See Inside This Document
This document is laid out so you can reach the clause you need without reading every line. The blocks below are the visible parts of the...
Summary Strip
A short row of badges under the headline sets the scope at a glance: account data, plain wording, your rights and the date of the last revision to this document.
Clause Blocks
Each numbered block covers one subject, so retention sits apart from sharing, and sharing sits apart from device permissions instead of being buried in one long paragraph you have to decode.
Context Chips
Where your account touches a local rail, a chip names it, helping you match a settlement record in your own wallet to the clause that explains how long we keep it.
Support Box
A fixed block repeats the email address and chat route for data requests, so you do not have to scroll back to the opening block once you reach the end of the page.
Revision Log
A dated list at the bottom records what changed and when, letting you confirm whether the paragraph you copied last year still reads the same way today for your region.
Plain-Language Panel
Short explanations sit beside the formal clause wherever the legal wording is dense, turning a rule into a sentence you can act on without a second opinion from anyone else.