LEGAL REFERENCE

How s98 Protects Your Data

s98 keeps your Privacy Policy clear: we collect the details needed to open your account, protect access, process local payments, and keep your activity records accurate. Read this...

Pakistan account dataJazzCash recordsEasypaisa checksSadaPay and Raast
Explore Lobby Read FAQ
s98 How s98 Protects Your Data

Our Data Handling Position

This Privacy Policy explains how s98 collects, uses, stores, and protects personal data connected with your account, identity checks, device access, live casino activity, sportsbook slips, wallet movement, and service messages in supported regions. We ask only for details that help us run the account flow, confirm your requests, keep payment records aligned with Pakistani rails, and respond when you contact us.

Some data is supplied by you, some is created when you use the lobby, and some is received from payment or security partners. We do not sell your personal data. We share limited records only when needed for account operation, fraud checks, payment handling, technical hosting, legal duties, or support follow-up. If a section affects your choices, we write it in plain

language so you can decide whether to open an account with s98.

Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.

PRIVACY HELP

Contact Paths For Privacy Requests

If you want to ask about access, correction, retention, or account data use, contact us through the same s98 channels you use...

Live chat privacy route Open chat from your account area and ask...
Email record requests Use email when your request needs a written...
Payment data questions For JazzCash, Easypaisa, SadaPay, NayaPay, or Raast privacy...
DATA CONTROLS

Signals Behind This Policy

We write the policy around how s98 actually operates: account creation, local wallet checks, device security, session logs, game records, and support handling. The aim is simple wording backed by practical controls...

Plain collection reasons

Each data category is tied to a practical purpose, such as account access, wallet matching, security checks, or support replies. We avoid broad wording where a clear operational reason can be stated.

Local payment mapping

Payment records are described with Pakistan rails in mind, including JazzCash, Easypaisa, SadaPay, NayaPay, and Raast. We explain why references, timestamps, and status labels may be stored.

Session protection

Login records, device signals, and browser data help us spot account access issues. We use these details to secure your session, investigate disputes, and reduce misuse of account credentials.

Limited sharing

Where service partners are involved, the policy explains the narrow reasons for sharing, such as hosting, analytics, payment routing, verification, security tooling, or legal response requirements in supported regions.

Retention boundaries

We keep records only for account operation, dispute handling, payment reconciliation, legal duties, and safety checks. When records no longer serve those needs, we restrict, remove, or anonymise them where practical.

Request handling

Privacy requests are handled after identity confirmation so your records are not released to the wrong person. We may need account email, phone match, or transaction context before acting.

How This Page Stays Consistent

This Privacy Policy sits beside our account terms, cookie wording, security text, and help pages. When one page mentions data use, we align the meaning here so your...

Account terms
Our account terms explain acceptable use and access rules, while this page explains the personal data behind those checks. Together they show why identity, login, and wallet records may be needed.
Cookie wording
Cookie wording focuses on browser storage, device signals, and preference tools. This Privacy Policy connects those signals to security, session continuity, analytics limits, and your choices where settings allow.
Payment help
Payment help explains transaction status and rail timing. This page explains the related privacy side, including references, wallet labels, timestamps, and why support may ask for partial transaction details.
Security page
Security text covers account protection steps. This Privacy Policy explains the records behind them, such as login time, device type, failed access attempts, and alerts linked to unusual activity.
Support scripts
Our support scripts are written to avoid exposing private records inside open chat. Agents ask targeted questions so they can help without requesting data that is not needed.
Promo wording
When s98 shows offers, this page explains how preference records, account eligibility, and message delivery may be handled. You can ask us to check communication choices linked to your account.
Legal updates
When wording changes, we keep the privacy meaning aligned across linked pages. If a major change affects your data choices, we make the change visible before you continue.
PAGE MARKERS

Visible Privacy Layout Elements

We design this policy page so you can scan it quickly before you open an account. Headings, chips, contact routes, and question blocks separate legal points from practical...

Account data chips Short chips call out common data areas, such as Pakistan...
Purpose-led sections Each section is arranged around a privacy purpose, not a...
Contact prompts Support cards explain which route fits each privacy request. This...
Local wording Pakistan-specific terms are used where they matter, including JazzCash, Easypaisa...
Rights language Where rights or choices apply, we describe them in direct...
Update cues Policy changes are marked through dated wording or visible page...

Common Privacy Policy Questions

We collect account details you provide, login records, device signals, payment references, support messages, and activity records linked to casino or sportsbook use. The exact data depends on how you access s98 and which services you use.

Payment references help us match JazzCash, Easypaisa, SadaPay, NayaPay, or Raast activity to your account. They also help support trace a delayed or disputed transaction without exposing unrelated wallet details.

No. We do not sell your personal data. Limited sharing may happen only for account operation, payment processing, hosting, security checks, analytics controls, legal duties, or support handling connected to your s98 account.

Contact us through account chat or email and explain which record needs correction. We will verify your identity first, then check whether the record can be updated under our operational and legal requirements.

Retention depends on the record type. Payment, security, dispute, and legal records may need to stay longer than simple preference data, while records no longer needed may be removed, restricted, or anonymised.

Support access is limited by role and request type. Agents see the details needed to answer your query, such as account status or transaction reference, while sensitive records require stricter handling.

Yes, it may change when our account flow, security tools, payment handling, or legal duties change. We keep the wording visible on this page so you can check the current privacy position before continuing.