Account terms
Account terms explain access rules, while this Privacy Policy explains the data behind those rules. We keep both pages aligned on identity checks, login records and account closure handling.
LEGAL REFERENCE
Privacy Policy for Your 92 game Account
92 game keeps your account privacy choices close to the lobby: we explain what we collect, why we use it, and how you can ask us about it...
Pakistan account dataJazzCash contextEasypaisa contextSadaPay contextRaast context
How We Handle Your Privacy
This Privacy Policy describes how 92 game handles the details you give us when you open an account, enter the lobby, contact support, or use Pakistani payment rails in supported regions. We may process your name, mobile number, login records, device signals, payment references, account balance events, location checks, and messages with our team. We use this data to run your account,
protect access, respond to privacy requests, meet record-keeping duties, and improve policy clarity. We do not sell your personal data. Some service partners help us with hosting, fraud checks, payment routing, analytics, and customer care, but they receive only what is needed for their role. Where local law permits access, you can ask us to check, correct, limit, or remove eligible account
data, subject to security and legal retention needs.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
POLICY CARE
How We Keep This Policy Accurate
We write this policy from the way our service actually handles account data. Each update is checked against login flow, wallet reference fields, support scripts, and security settings...
Product checks
Our product team checks new account screens against this policy so the data requested on 92 game matches the purpose...
Security input
Security staff check login, password reset, device and session records before policy edits are published. That helps us describe actual...
Payment rail matching
Wallet and bank references from JazzCash, Easypaisa, SadaPay and Raast are checked against the wording here, so you know why...
Support language
Support replies are aligned with this policy, including what we can confirm in chat and what must move to email...
Retention checks
We check retention wording against operational needs such as fraud prevention, account disputes, transaction reconciliation and lawful record duties before...
Change record
When privacy wording changes, we keep an internal change record showing what changed, why it changed, and which account or...
POLICY ALIGNMENT
Policy Pages Stay Consistent
Your privacy rights should not change from one legal page to another. We keep this Privacy Policy aligned with our account terms, cookie wording, promotion rules, and security notices. When one page...
Cookie wording
Cookie wording focuses on browser storage and device signals. This Privacy Policy connects those signals to account security, preference handling and service measurement across 92 game.
Promotion rules
Promotion rules may refer to eligibility records. This Privacy Policy explains how those records are stored, checked and limited to the account purpose that created them.
Payment terms
Payment terms describe wallet and bank flows. This Privacy Policy explains the privacy side: reference numbers, verification records, reconciliation logs and support messages tied to payment events.
Security notices
Security notices focus on account protection steps. This page explains related data processing, including device checks, session records, password reset logs and access alerts.
Support scripts
Support scripts follow this policy when asking for identity confirmation. We avoid requesting more data than needed, and sensitive files move through controlled channels.
Change timing
When related legal pages change, privacy wording is checked in the same update cycle. That keeps your rights, retention details and contact paths clear.
PAGE SIGNALS
Privacy Cues Across the Page
This page is designed to make privacy choices easy to find before you share details with us. The layout separates account data, payment references, contact paths and rights...
Short badges
The badges near the hero show the account and local...
Plain headings
Each heading names the privacy issue directly, such as data...
Action wording
Where you can ask us to check, correct or remove...
Local references
Pakistan payment names appear only where they help explain privacy...
Security markers
Icons beside security-related cards point to account protection themes, including...
FAQ anchors
Questions at the end cover the privacy points we are...
Privacy Policy Questions Answered
We collect details needed to run your account, such as mobile number, login records, device signals, wallet references, support messages and security events. We avoid asking for extra data that has no clear account purpose.
Payment references help us match JazzCash, Easypaisa, SadaPay and Raast activity to your account, handle disputes, check fraud signals and meet record duties. We use masked records where full detail is not needed.
No. We do not sell your personal data. Selected service partners may process limited data for hosting, security, analytics, payment routing or support, and they must use it only for the assigned service.
Yes. Contact support with your registered mobile number and the detail that needs correction. We may ask for identity confirmation before changing personal data, especially if the request affects wallet or access records.
We keep data for as long as needed to run your account, protect access, resolve disputes and meet legal record duties. Some records can be removed sooner when they are no longer required.
We use login records, session checks, password reset controls and device signals to protect your account. These security records help us spot unusual access and respond when you report a privacy concern.
Use our support email for formal privacy requests and chat for quick routing help. Include your registered mobile number, state the request clearly, and avoid sending sensitive files unless our team asks.