Terms connection
Account terms explain how you may use s99, while this Privacy Policy explains what data supports that use. We keep the split clear so privacy questions stay easy to locate.
s99 keeps live casino, slots and sportsbook access in one account, and this Privacy Policy explains how your account data is collected, used, stored and shared where local...
This Privacy Policy sets out how s99 handles details linked to your account, device, login sessions, identity checks, payment records and support messages in supported regions. We collect only the data needed to open and protect your account, process requests, keep wallet records accurate, detect misuse and answer privacy questions. When you use JazzCash, Easypaisa, SadaPay or Raast, we receive transaction references
and status updates rather than full wallet access. We may keep records for security, audit and dispute handling, then remove or anonymise data when it is no longer needed. Access may depend on local law, service availability and verification checks.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
If you want to ask about your Privacy Policy rights, we keep contact routes focused on account ownership, verification and data handling. Our support team may ask for limited details before discussing private records, so your account is not exposed through a casual message.
Use chat when you need a quick privacy response about login records, payment references or account access. We verify basic account details first, then keep the conversation tied to your request.
Contact security support if your phone, email or wallet reference looks wrong. We check recent sessions, lock risky changes when needed and explain what personal data was involved.
For correction, access or deletion requests, use the document request path inside your account area. We may need identity proof before releasing or changing private records.
We write this Privacy Policy from the way s99 actually runs account privacy in Pakistan. The wording is checked against payment flows, support handling, login security and data retention practice, then adjusted...
The policy reflects real account steps, including login checks, wallet references and support tickets. We avoid vague privacy promises and state what data is used in each account stage.
JazzCash, Easypaisa, SadaPay and Raast references are treated as privacy-relevant records. We describe status checks, receipt matching and dispute handling without asking for full wallet access.
Our privacy wording explains device checks, password resets and session records because these affect account protection. You can see why certain data is kept after a login event.
Support staff can discuss only the records needed for your request. We keep internal access controlled, log account actions and avoid sharing private details through open channels.
We keep privacy records only while they serve account security, wallet reconciliation, dispute handling or legal needs. Older data is removed, masked or separated from daily account use.
This page uses direct Pakistani English so you can understand what happens to your data. If wording changes, we update the policy date and account-facing text together.
Our Privacy Policy connects with other legal pages without repeating them word for word. Each page has its own job: this one explains data handling, while linked terms handle account rules, cookies...
Account terms explain how you may use s99, while this Privacy Policy explains what data supports that use. We keep the split clear so privacy questions stay easy to locate.
Cookie text deals with browser storage, device signals and preference tools. This policy links that activity back to account privacy, security monitoring and session accuracy.
Payment pages describe wallet steps, while this policy explains the privacy side of JazzCash, Easypaisa, SadaPay and Raast references, receipt checks and status matching.
Support pages show how to contact us, while this policy explains what we store from support conversations, why we may verify identity and how requests are handled.
Security text focuses on protecting your account. This policy explains related personal data, such as login time, device signals, password reset records and unusual access checks.
Where access depends on supported regions, related pages use matching phrasing. This policy adds privacy meaning by explaining local handling, retention and account verification.
When we adjust legal pages, we check privacy language at the same time. That helps account screens, help replies and policy wording stay aligned.
We place privacy cues where they matter: account creation, wallet checks, support requests and security prompts. These layout elements help you understand why a detail is...
When you open an account, field labels explain why details are needed. We keep required fields separate from optional contact preferences so your privacy choice is clearer.
Login and device prompts are written in plain terms. If a session looks unusual, we explain what record triggered the check and how it protects your account.
Payment screens show reference status without exposing unnecessary wallet detail. You see enough to match JazzCash, Easypaisa, SadaPay or Raast activity to your account.
Support forms ask for the minimum detail needed to identify your account issue. We discourage sending card images, unrelated documents or personal data not requested.
Account preference screens help you manage contact choices linked to service messages. Changes are recorded so we can respect your selection across future account interactions.
The Privacy Policy remains reachable from account and footer areas. We keep it close to sign-in, wallet and support pages because those flows involve personal data.