Privacy Policy for your account
At 98 games, your account data, privacy choices and Pakistan payment records sit under one Privacy Policy, so you can see what we collect before you open your...
How this privacy notice applies
This Privacy Policy describes how 98 games handles personal data connected with your account, identity checks, login activity, gameplay records, support messages and Pakistan payment references. We write it for you, not for third parties, so the wording stays close to the way your account works in practice. When you use JazzCash, Easypaisa, SadaPay or Raast, we may receive reference data needed
to match a transaction to your account, confirm status and keep account records accurate. We do not treat this page as permission for access in every location; account access depends on supported regions and where local law permits. We update this policy when our data handling, security controls, service partners or contact paths change.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
How we keep this policy accurate
Our privacy wording is maintained by the same teams that handle account operations, support routing and security checks. That matters because policy language should match what actually happens...
Operational input
We align policy wording with the teams handling account records, wallet references and support queues. If a process changes, the...
Security alignment
Our security checks cover login signals, device details and unusual account access patterns. The policy explains these categories so you...
Local payment context
Pakistan rails can create reference numbers, status messages and wallet identifiers. We describe these records as privacy data because they...
Support records
When you contact us, your messages may be stored with timestamps and agent responses. The policy explains this so account...
Data minimising
We aim to collect only what is needed for account access, identity checks, transaction matching and service support. Extra sensitive...
Change tracking
Material policy changes are reflected on this page through revised wording and visible dates where used. You can return here...
How our privacy pages stay aligned
This page works beside our other account terms, cookie wording and service notices, but it keeps one job: explaining privacy. Where another page mentions account access or promotions...
What you see on this policy
The Privacy Policy is built to be read quickly without hiding key points. We use clear labels for data types, purposes, sharing, retention and your contact...
Clear data labels
Each major data category is described in plain account language, such as login records, payment references and support messages. This helps you connect the policy wording to actions you take on 98 games.
Purpose blocks
We separate collection reasons from storage reasons, so you can see why data is used. Account access, verification, transaction matching and support handling are described as distinct privacy purposes.
Sharing cues
Where service partners may process records for us, the policy explains the role in practical terms. Examples include payment status handling, security tooling and customer support systems tied to your account.
Retention wording
Retention language explains why some records remain after a session ends. Account security, transaction reconciliation, dispute handling and legal duties can require data to be kept for defined periods.
Choice language
Your privacy choices are written as account actions, not abstract legal phrases. You can ask about access, correction or deletion, and we explain when verification is needed first.
Contact placement
Privacy contact routes are kept close to the policy sections that mention your rights. This reduces searching when you need to ask us about stored records or account-linked payment references.