Privacy Policy for Your 99xx Account
At 99xx, your privacy choices sit beside the casino, slot and sportsbook account flow, so you can see how data is handled before you open an account. This...
How We Handle Your Account Data
This policy sets out how 99xx handles account data for Pakistan access in supported regions. We collect details you enter, device and login records, support messages, and payment references connected with JazzCash, Easypaisa, SadaPay, and Raast. We use that data to open and protect your account, settle privacy requests, check withdrawals, and meet legal duties where local law permits. We do not
sell your data. When a service partner helps with hosting, verification, payments, or support tooling, we limit access to the task and keep records of that access.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Privacy Help When You Need It
Privacy requests need careful checks, not canned replies. Use the routes below when you want to ask about access, correction, deletion, cookies, account security records, or payment references on 99xx. We keep the conversation linked to your account, verify before sharing private details, and escalate complex requests to the team that maintains this policy.
Live chat
Use live chat when you want a fast privacy answer about account records, login alerts, or payment references. We ask simple checks before discussing private details with you on the thread.
Email channel
Send us an email if you need a privacy request in writing, such as a correction, access question, or deletion query. Include your account email so we can locate the right record.
Account centre
Inside your account centre, you can check profile fields, saved contact details, login alerts, and communication choices. These screens help you keep privacy settings current without waiting for a reply.
Checks Behind This Privacy Policy
We treat this Privacy Policy as an operating page, not a decoration. The wording is checked against the screens you actually use, including account opening fields, login alerts...
Named policy owner
Our privacy text is maintained by a named internal owner, not left as static filler. That owner checks wording against...
Local language fit
We write this policy in clear Pakistani English so you can understand account, device, and payment data terms without legal...
Payment record checks
When JazzCash, Easypaisa, SadaPay, or Raast fields change, we update the policy wording so receipt data, account names, and verification...
Security wording
We describe encryption, access controls, and staff permissions in plain terms. The policy avoids vague claims and focuses on what...
Change logging
Policy changes are dated in the page layout, and major privacy changes are called out in account messages where practical...
Support feedback
Questions sent to support are grouped by privacy topic, then used to clarify unclear wording. We do not publish your...
Consistent Privacy Across 99xx Pages
Your privacy position should not change from page to page. The items below show how this Privacy Policy connects with related 99xx pages without repeating them. Each linked...
| Terms page | Our Terms page explains account rules, while this Privacy Policy explains data handling. Links between them help you see which clauses affect records, access checks, and account contact details. |
|---|---|
| Cookie page | The cookie page focuses on browser signals, device IDs, and preference tools. This policy connects those signals to account security, session records, and your choices about optional tracking. |
| Offer page | Offer pages may request contact permission, but this policy states how those choices are stored. We separate campaign consent from core account notices so privacy settings stay readable. |
| Payments page | Payment pages show JazzCash, Easypaisa, SadaPay, and Raast steps. This policy explains the related privacy layer: receipt references, verification checks, retention periods, and who may access records. |
| Security page | The security page describes account protection, while this policy covers the personal details involved in that protection. Login alerts, device records, and password reset checks are treated as privacy data. |
| Support page | Support pages list contact routes, but this policy explains how support messages are handled. We state when chat transcripts are stored, who can read them, and how requests are verified. |
| Account page | Account screens let you update profile details; this policy explains the privacy effect of those edits. It also explains why some records remain after closure for legal or security reasons. |
Policy Layout You Can Read Fast
The privacy page is built for quick reading on mobile screens in Pakistan as well as larger screens. Its layout keeps legal text, local payment context...
Plain headings
Each policy block uses short headings for collection, use, sharing, storage, and choices. You can scan the layout quickly, then open the section that affects your account concern.
Local chips
JazzCash, Easypaisa, SadaPay, and Raast appear as context chips where payment privacy is discussed. The chips do not ask you to transact; they identify data sources.
Action prompts
Where you can request access, correction, or deletion, the page points to the right contact route. The wording stays calm and does not mix privacy rights with sales copy.
Device labels
Mobile app, browser, and tablet references are labelled separately because each creates different logs. This helps you understand session privacy whether you access 99xx at home or outside.
Storage markers
Retention wording sits beside each data category instead of being hidden at the end. You can see why we keep a record and what may trigger removal later.
Change date
The change date stays visible near the policy header. When privacy wording moves, we aim to keep the meaning clear and avoid quiet edits that affect your choices.