Terms page
Our terms describe account rules, while this policy explains the data behind those rules. If an account action needs identity, transaction, or session records, the privacy reason appears here.
n99 keeps your casino, sportsbook, account and Pakistan payment data inside a privacy policy written for everyday account use. Read how we collect, use, store and share data...
This Privacy Policy explains how n99 handles personal data when you create an account, access casino or sportsbook areas, use support, complete checks, or make transfers through supported Pakistan rails where local law permits. We collect details you provide, device and session data, payment references, security signals, and messages you send to us. We use that data to run your account, confirm
transactions, manage access, detect misuse, answer privacy requests, and meet record duties that apply to our operations. We do not sell your personal data. Sharing is limited to service providers that help with hosting, fraud checks, payment processing, analytics, account support, and legal requests that we must answer.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Use the privacy contact paths when your question is about data access, correction, deletion, account security, or how a transfer reference is stored. We route these messages separately from general account help so your request reaches the team that can check records and answer clearly.
Send privacy requests to [email protected] with your account email, phone number, and a short request summary. We may ask for extra verification before sharing account records or changing stored details.
If you contact chat from your account, ask for a privacy handoff. The agent can flag your request, confirm recent session details, and move it to the privacy queue without exposing sensitive data.
For suspected account access by another person, tell us which device, time, or transfer reference looks unfamiliar. We use that detail to check logs and restrict risky sessions while we respond.
Our privacy wording is maintained by the same operational teams that handle account flows, payment references, security alerts, and support records. That keeps the policy tied to what actually happens inside n99...
When account flows change, we check whether new data is collected, where it is stored, and which provider touches it. The policy is updated when those changes affect your privacy choices.
We write this policy in clear Pakistani English so you can understand what happens to account data, payment references, device signals, and support messages without legal phrasing hiding the meaning.
Internal access to account records is role based. Support, risk, finance, and technical teams see only the data needed for their work, with sensitive actions logged for later checking.
We map service providers that process hosting, security, analytics, and transfer references. This helps us keep sharing narrow and confirm that each provider has a clear purpose.
Retention periods are set around account operation, dispute handling, security checks, and legal duties. When data is no longer needed, we remove it or reduce it so it cannot identify you.
Material privacy changes are placed on this page before or when they take effect. If the change affects your account data in a major way, we may also contact you directly.
This policy sits beside our other legal and account pages. Each page has a different job, but the privacy meaning stays aligned: what data we collect, why we use it, how long...
Our terms describe account rules, while this policy explains the data behind those rules. If an account action needs identity, transaction, or session records, the privacy reason appears here.
Cookie wording deals with browser storage, device recognition, and analytics signals. This policy connects those signals to broader account use, including security checks and preference handling.
Security content explains protection measures, while this policy explains how related logs, device markers, and access events are collected and used to keep your account safer.
Account screens ask for details such as phone, email, and verification data. This policy sets out why those fields matter and how correction or deletion requests are handled.
Transfer screens may show JazzCash, Easypaisa, SadaPay, and Raast references. This policy explains how those references are stored, matched, and shared with processors when needed.
If an offer requires eligibility checks, we may use account status, region, device, and activity records. This policy explains those data uses without changing the offer terms.
Help conversations can include screenshots, transaction IDs, or device details. This policy explains how those messages are stored, accessed by support, and used to resolve your request.
We structure this page so you can find privacy topics quickly before you open an account or send a request. The layout separates collection, use, sharing, retention, security...