Cookie Policy
Our Cookie Policy uses the same data categories as this Privacy Policy, so device identifiers, session tools, and consent choices are described with matching labels rather than mixed wording.
9oo99 keeps your account, wallet, device and lobby activity data inside one clear privacy workflow for Pakistan. Open your account in seconds, read how each data point is...
Our Privacy Policy explains what we collect when you create an account, verify access, add funds, request a cash-out, use live tables, open slots, or move through the sportsbook where local law permits. We collect only the data needed to run your account, secure your login, reconcile wallet records, meet lawful checks, and answer privacy requests. Payment references from JazzCash, Easypaisa, SadaPay
and Raast are kept as transaction records, not as open wallet access. We do not sell your personal data. If a service partner helps us with hosting, fraud checks, message delivery, or wallet reconciliation, we restrict the data shared to the purpose agreed with that partner. Access is limited inside our team, and sensitive requests require ownership checks before changes are made.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Privacy questions need a clear path, not a generic inbox. We separate account help from data requests so your concern reaches the right team. When you contact us, share only the details needed to identify your account and explain the privacy action you want, such as access, correction, deletion, or cookie choice help.
Send privacy requests through our email channel with your account phone or email, the data concern, and any wallet reference. We route these requests to staff trained on access, correction, and deletion handling.
Use chat when you need quick direction on cookies, login alerts, or payment receipt data. We may ask you to move sensitive details into email before a privacy action is completed.
Inside your account area, you can check saved profile fields and security prompts. If a field looks wrong, contact us so we can confirm ownership before changing stored data.
We treat this Privacy Policy as part of the 9oo99 account journey, not as a static legal file. Our internal checks look at new payment flows, support tools...
We map each data type to the account step that creates it, such as login, wallet reconciliation, verification, gameplay records...
We write privacy terms in direct Pakistani English so you can understand what we collect, why we use it, how...
Pakistan payment names are kept specific in our policy because JazzCash, Easypaisa, SadaPay and Raast records create different receipt references...
Team access is role based. Staff working on support, wallet checks, account security, or compliance tasks see only the data...
We check stored records against operational need, legal duties, dispute handling, and security reasons. Data that is no longer required...
When the policy changes in a meaningful way, we place the updated date and relevant wording where you can see...
Our legal pages are written to work together. This Privacy Policy explains data handling, while related pages explain cookies, account terms, security practices, and contact paths. We use consistent labels across those...
Our Cookie Policy uses the same data categories as this Privacy Policy, so device identifiers, session tools, and consent choices are described with matching labels rather than mixed wording.
Our account terms point back to this Privacy Policy whenever personal data is involved, including verification, restricted access, security checks, transaction records, and communication between you and our team.
Security wording stays aligned with the privacy text, especially around passwords, login alerts, device checks, encrypted transfer, role-based access, and the steps used before sensitive account changes.
Where wallet pages mention JazzCash, Easypaisa, SadaPay or Raast receipts, the same references appear here as privacy records used for reconciliation, dispute checks, and lawful accounting.
The contact page and this Privacy Policy use the same request categories, helping you choose whether your message is about account help, data access, correction, deletion, or cookie choices.
Verification wording matches this policy so identity checks are not presented as a separate data practice. We explain why evidence may be needed and how access to it is limited.
When legal wording changes, banners and date labels use the same update language across related pages, making it easier to spot fresh privacy terms before you continue.
The privacy page layout is built to make policy reading easier before you join. We keep the key actions visible: what data we collect, why we...
The badges near the hero show the privacy areas you are most likely to check first: account data, wallet records, cookies, security controls, and direct contact for action.
A clear data path shows how details move from account opening to verification, wallet checks, gameplay records, and support messages, keeping each privacy step visible in order.
Cookie wording is kept close to device and session sections, so you can connect browser storage, login continuity, fraud prevention signals, and preference choices without switching pages.
Privacy action prompts explain how to ask for access, correction, deletion, or restriction where available. We keep the request language direct and tied to your account ownership.
Pakistan access wording appears near account and wallet sections because privacy handling can depend on supported regions, local law, payment rails, and verification standards used for your account.
The contact panel repeats the right privacy channels so you do not send sensitive data into unrelated help flows. It also reminds you to share only necessary details.