Account terms
Our account terms handle eligibility, login rules and what follows if you break them. This policy deals only with data, so the two pages sit side by side.
This privacy policy sets out what we collect when you open an s99 game account, why we keep it, and the choices you hold over it. Read it...
This privacy policy covers s99 game accounts held by people we can serve where local law permits. Open your account from Pakistan and we record the minimum needed to run it: your name, contact details, a date of birth check, and the payment reference that ties a JazzCash, Easypaisa, SadaPay or Raast transfer to your profile. We keep those records while your
account is open and for the retention period our banking partners and local rules require afterwards, then delete or anonymise them. You can ask to see what we hold, ask us to correct anything wrong, and ask us to close the account and end marketing messages. Some data we must keep even after closure because payment reconciliation and dispute rules apply, and
we tell you which parts fall into that category. Where local law differs from this page, the law of your supported region decides, and we update this policy when that happens.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Your privacy questions reach a real team rather than a queue that never answers. Chat is staffed during published hours and email is checked daily, and every request about your account record gets a written reply with a reference you can follow up on. The same channels handle corrections, marketing opt-outs and closure requests, and we confirm in writing once each one is done.
Sign in and use the chat window whenever a privacy question comes up. Our agents pull your account record, explain what we hold, and log a correction request while you wait.
Write from the email address registered on your s99 game account so we can match the request safely. We reply with a written summary of what we hold and the steps that follow.
Request a file listing your profile, login history and payment references. We confirm your identity first, then send the export in a readable format you can keep at no charge.
This page is not drafted once and forgotten. Our operations team writes the clauses, tests each claim against the systems we run daily, and has a lawyer read...
The people who handle onboarding, payments and chat support write these clauses, so each line reflects how the platform behaves...
Before anything is published we walk the claims against the real dashboard, the payment ledger and the chat tool, correcting...
We write for readers here, naming JazzCash, Easypaisa, SadaPay and Raast where those rails matter instead of vague global wording...
Every change carries a date and a short summary of what moved, so you can see whether an edit affects...
A lawyer versed in Pakistani data rules reads each version, flags clauses that need tightening, and sends comments that are...
When you tell support a clause is unclear we log it, and our team rewrites that part in the next...
Sibling pages on this site cover different ground, and we keep the boundaries clean. Account terms, cookies, promotions, sportsbook rules and security each carry their own clause set, while this policy stays...
Our account terms handle eligibility, login rules and what follows if you break them. This policy deals only with data, so the two pages sit side by side.
Deposit and withdrawal conditions live on their own page, including the reference formats JazzCash, Easypaisa and SadaPay send us. Here we cover how those records are stored.
The cookie page lists the tags we set, what each one does and how to switch them off. This policy explains why we keep the resulting data and how long it stays.
Promotional conditions describe what a reward requires. We do not repeat them here; we describe what account activity a promotion records and how long that record stays visible.
Bet settlement, market suspension and void rules have their own wording. This page covers the personal data attached to a bet slip, such as account ID, stake and timestamp.
Password handling, two-step login and device approvals sit on a separate page. Here we explain what a login record contains, who can see it, and the retention window.
If a privacy request is refused, our complaints clause sets out the escalation path and reply window. Both pages carry the same case reference.
The layout here is built for scanning on a small screen. Clause headings are numbered, long paragraphs open with a bold one-line summary, and the sections...
A slim rail lists every clause so you can jump to retention, sharing or your rights without scrolling the full page on a phone.
Each long clause opens with a short bold line saying what the rule means for your account, then the fuller wording follows for anyone who wants detail.
The head of the page carries the date of the last edit plus a link to a short list of what moved, so returning readers spot a shift in seconds.
A compact table sets out which data category we hold, why, and how long it stays, readable across three columns or as stacked cards on mobile.
Chat, email and data-copy links sit together near the close of the page, each labelled with the reply window you should expect, so you never hunt for a way to reach us.
A print view strips navigation and colour so you can save the policy as a clean file for your own records, with clause numbering left in place.