99 games Privacy Policy
Live casino tables, slots and account access all create data trails, so this Privacy Policy explains how 99 games collects, uses, stores and protects your details. Open your...
How We Treat Your Data
This Privacy Policy applies when you use 99games.bid from supported regions in Pakistan, open an account, contact our team, or use local rails connected with your account. We collect only the data needed to run account access, identity checks, payment verification, security monitoring, service messages and dispute handling. Your details may include name, phone number, login records, device signals, wallet references and
support chat content. We keep those records for operational, legal and security purposes, then remove or anonymise them when they are no longer needed. We do not sell your personal data. Where service partners help us process payments, host systems or verify activity, they receive only the data needed for that task.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
How We Keep Policy Accurate
Our privacy text is checked against the way 99 games actually runs account access, payments, live tables and support. When a process changes, we update the wording instead of leaving stale promises...
Payment mapping
We map each JazzCash, Easypaisa, SadaPay and Raast data field to its purpose, such as receipt matching, withdrawal verification, fraud checks or customer support history.
Security wording
Our policy describes encryption, access controls and login monitoring in plain language. We avoid vague claims and explain which account events may create security records.
Partner checks
When a vendor helps with hosting, analytics, messaging or payments, we check what data is shared, why it is shared, and how long the partner keeps it.
Change log
Policy changes are dated so you can see when privacy wording has moved. Material changes are reflected in account-facing messages where that is required.
Access handling
Requests for data access or correction are handled after identity checks. This protects your account from someone asking for private records without permission.
Local context
We write for Pakistan account flows, including local wallet references and mobile-first use. That keeps the policy tied to how you actually use 99 games.
How This Page Fits Others
Our privacy page sits beside other legal pages, but it has a narrower job. It explains personal data handling only. When another page talks about account rules, cookies...
| Terms page | The Terms page explains account rules and service use. This Privacy Policy explains the personal data created by those rules, including identity checks and access logs. |
|---|---|
| Cookie page | Cookie wording covers browser storage and tracking choices. This page connects those signals with wider account privacy, device security and service performance records. |
| Payments page | Payment content explains transaction flow. This policy explains why wallet references, bank transfer IDs and withdrawal checks may be stored with your account. |
| Promotions page | Promo terms may describe eligibility. This policy explains the data checks behind eligibility, account history, contact preferences and messages sent to your registered details. |
| Security page | Security content may describe passwords and alerts. This privacy page explains what login records we keep and how those records help protect account access. |
| Support page | Support content shows how to reach us. This policy explains how chat transcripts, email threads and identity checks are stored and used. |
| Account page | Account content helps you manage profile details. This policy explains correction requests, data access, retention periods and the checks required before changes. |
Privacy Layout You Can Scan
We designed this Privacy Policy to be read quickly on mobile without hiding important points. The page separates collection, use, sharing, storage and your choices. Each...
Summary chips
Short chips call out Pakistan account scope, wallet context and security records. They help you spot the data areas that may apply before reading longer clauses.
Clear sections
Each section covers one privacy subject, such as collection, sharing or retention. This layout keeps legal text from mixing unrelated account matters together.
Plain wording
We use direct language for account data, payment references and support records. Where a legal term is needed, we tie it to a practical account action.
Rights panel
Your access, correction and deletion requests are grouped together so you can see the available path, required verification and expected follow-up steps.
Retention cues
Storage wording explains why certain records remain after a transaction or support case, including dispute handling, security checks and legal recordkeeping needs.
Update marker
The policy date shows when wording last changed. If our data handling changes in a meaningful way, we refresh the page and account-facing messages.