LEGAL REFERENCE

How 98 game handles your data

98 game uses this Privacy Policy to explain what account data we collect, why we collect it, and how we protect it when you access our casino, sportsbook...

Account data useDevice log checksPakistan wallet contextSupport contact routes
98 game How 98 game handles your data

Privacy posture for Pakistan access

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

PRIVACY CONTACTS

Reach us about privacy requests

If you want to ask what data we hold, correct account details, query a wallet reference, or raise a concern about account...

Account privacy inbox Send privacy requests from the email linked to...
Live chat privacy routing Use chat for quick routing when you cannot...
Wallet record checks For privacy questions tied to deposits or withdrawals...
POLICY CHECKS

How we keep the policy accurate

We maintain this Privacy Policy as an operating document, not a decoration. The policy is checked when account flows change, when wallet routing changes, or when support handling needs a clearer data...

Operator-written wording

The policy is written from our own account flow, including login, verification, wallet matching and support handling. That keeps the wording tied to what you actually encounter inside 98 game.

Local wallet context

We name JazzCash, Easypaisa, SadaPay and Raast because those rails create transaction references we may need to process. The policy explains that context without asking for private wallet passwords.

Access control checks

Account records are limited to teams and service partners that need them for security, payment matching or support work. We monitor access so private data is not handled casually.

Session data clarity

The policy covers device and session logs because they help us spot suspicious access, repeated failed logins and unusual account movement. We explain this so you know why such logs exist.

Retention limits

We keep account and transaction records only for operational, legal, security and accounting needs. When a record is no longer needed, we remove it or reduce it where practical.

Plain privacy language

We avoid vague legal filler where a clearer sentence works. If a term affects your account data, the policy connects it to sign-in, wallet checks, security alerts or support requests.

POLICY ALIGNMENT

Consistency across related policy pages

Our Privacy Policy works alongside the terms, cookie wording and account rules without repeating every clause. Each page has a different role. This page focuses on personal data, while related pages explain...

01

Privacy Policy

This page explains what personal data we collect, why we use it, who may process it for us, and how you can contact us about access, correction or privacy concerns.

02

Terms page

The terms page sets the account agreement, but it does not replace this Privacy Policy. When a term involves data handling, this policy explains the privacy side in more detail.

03

Cookie wording

Cookie wording deals with browser storage, analytics tags and session tools. This Privacy Policy connects those tools to broader account security, preference handling and device recognition.

04

Wallet rules

Wallet rules explain transaction handling, while this policy explains the related data trail. That includes references, timestamps, status checks and support records linked to Pakistani wallet routes.

05

Security procedures

Security procedures describe how we react to risky account activity. This policy explains the data used for those checks, including device signals, login attempts and account access history.

06

Support records

Support rules explain response flow, while this policy explains how tickets, chat content and verification details are stored, accessed and used to solve privacy or account issues.

07

Regional access wording

Regional wording explains access only where local law permits. This policy adds how we process the account and device data created when you access 98 game from supported regions.

PAGE SIGNALS

Visible cues inside this policy

This page is arranged so you can scan the privacy points before creating or using an account. The headings separate collection, purpose, sharing, security, retention and contact routes...

Short privacy badges The badges near the hero show the data areas covered...
Context chips The local wallet chips are included only to show where...
Direct section titles Each title names the privacy issue before the paragraph explains...
Card based answers Cards break longer privacy points into small blocks. We use...
Mobile friendly layout The policy is built for a small screen, with compact...
FAQ closeout The final questions cover practical privacy requests, such as correction...

Common privacy questions answered

We collect data you provide during account creation, verification, wallet use and support contact. We also collect device, session and security logs that help us protect account access and maintain accurate records.

Transaction references help us match deposits, withdrawals, reversals and support queries with your 98 game account. For Pakistan routes such as JazzCash, Easypaisa, SadaPay and Raast, we use references rather than wallet passwords.

Yes. Contact us from the email linked to your account and explain what needs correction. We may verify your identity first, then update data where the change is valid and lawful.

We share limited data with service partners that help with hosting, payment reconciliation, fraud checks, support handling and security logging. These partners receive only what is needed for the assigned purpose.

Retention depends on the record type. Account, transaction, security and support records may be kept for operational, legal or accounting needs, then removed or reduced when those needs end.

Cookies and similar tools help with sign-in sessions, preferences, analytics and security checks. This policy explains how those browser signals connect with your wider account privacy at 98 game.