Privacy Policy for Your Account
we 999c keeps live casino, slots and sportsbook access in one account, and this Privacy Policy explains what data we collect before you open, verify or use that...
How We Handle Your Data
This Privacy Policy describes how we 999c collects, uses, stores and shares personal data when you access our casino gambling and sportsbook services where local law permits. We collect account details you provide, verification records, device signals, session logs, wallet references and messages sent to our support team. We use those records to run your account, protect access, process local payment requests,
detect misuse, answer your questions and meet legal duties that apply to us. We do not sell your personal data. Where service partners help with verification, hosting, payment routing or fraud checks, they receive only the data needed for that task. You can ask us to correct, access or erase eligible records, subject to security, payment and legal retention needs.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Privacy Help from Our Team
If you have a privacy request, contact us from inside your account where possible, because logged-in messages help us match the request to the correct profile. You can also reach our support inbox for access, correction or deletion questions, and we may ask for verification before acting.
Account privacy inbox
Use the account help area to ask for a copy, correction or deletion of eligible personal data. We match your message with login records before changing sensitive account details.
Payment record queries
For JazzCash, Easypaisa, SadaPay or Raast privacy questions, include the masked wallet reference and request date. We check internal payment logs without asking for your full wallet access credentials.
Security access checks
If you think your account data was viewed without permission, contact us quickly. We can inspect login history, device signals and recent profile changes before advising next steps.
Controls Behind This Policy
Our Privacy Policy is written around the systems we operate: account creation, identity checks, local payment handling, lobby sessions and customer support. We keep the language practical so you can see why...
Purpose mapping
Each data category is linked to a clear use, such as account access, payment routing, security checks or support replies. This keeps collection tied to what we need to operate your account.
Limited partner sharing
Service partners may help with hosting, verification, fraud screening or payment routing. We share only the records needed for their task, and we require handling aligned with our privacy terms.
Access protection
We use passwords, device checks and session monitoring to reduce unauthorised account access. Security logs may be retained when needed to investigate disputes, suspicious login activity or profile changes.
Local payment context
JazzCash, Easypaisa, SadaPay and Raast references are handled as transaction records, not as open access to your wallet. We use masked references for support whenever practical.
Retention checks
Some records must be kept for legal, payment, tax, dispute or security reasons. When those reasons no longer apply, we remove, anonymise or reduce records according to internal retention rules.
Policy maintenance
We check this Privacy Policy when account flows, payment routing or support processes change. If material handling changes, we update the page so your rights and our practices stay clear.
How Our Privacy Pages Match
This page sits beside our terms, cookie wording and support notices. The Privacy Policy explains personal data handling, while the other pages cover account rules, browser storage or...
| Privacy Policy | This page explains personal data collection, use, sharing, retention and your rights. It applies when you create an account, verify details, use the lobby or speak with support. |
|---|---|
| Terms page | Our terms set account rules and service conditions, while this policy focuses on data handling. If both pages mention verification, the Privacy Policy explains what records are processed. |
| Cookie wording | Cookie wording covers browser storage, session tools and similar device signals. This Privacy Policy connects those signals to account security, preferences, analytics and fraud checks where applicable. |
| Support notices | Support notices explain how to contact us and what we may ask for. This policy explains why we request verification details before disclosing or changing personal records. |
| Payment help | Payment help may show how a request is submitted, while this policy explains how wallet references, status logs and dispute messages are stored and used. |
| Security messages | Security messages may warn you about access risks. This Privacy Policy explains how login records, device checks and alerts help protect your account from unauthorised use. |
| Update records | When we change privacy wording, we keep the current version on this page. Major changes may also be flagged in account areas or support messages. |
Visible Privacy Layout Elements
We structure this Privacy Policy so you can scan it before joining and return later when you need a specific privacy answer. The layout separates account...
Clear section labels
Each block names the privacy area it covers, such as collection, use, sharing or retention. This helps you find the part linked to your account question without reading unrelated terms.
Local account context
Examples mention Pakistan access, JazzCash, Easypaisa, SadaPay and Raast because those are part of your account flow. Local references make the privacy wording easier to apply.
Plain data categories
We name data types in everyday language: profile details, verification records, payment references, device signals and support messages. You can see what each category means before sharing details.
Rights explained
The policy explains how you can request access, correction or deletion where available. We also explain why some records may remain for legal, security or payment dispute reasons.
Partner boundaries
When partners process data for us, the page states the service purpose instead of using vague wording. Hosting, verification, fraud checks and payment routing are treated as separate tasks.
Change visibility
Policy updates are reflected on this page, so you can return to check current wording. If processing changes in a material way, we aim to make that change noticeable.