Privacy Policy for your 90x game account
90x game keeps your privacy choices, account checks and payment records in one place so you know what we collect before you open an account. This Privacy Policy...
How we handle your personal data
This Privacy Policy applies when you use 90x game in supported regions, contact us, verify your account, or request account-related changes. We collect only the data needed to run your account, protect access, process activity records, and respond to privacy questions. That can include your name, mobile number, email address, device signals, login history, game-session logs, CNIC details where verification is required,
and transaction references tied to Pakistani rails. We use this data to confirm identity, prevent account misuse, maintain accurate records, and meet duties that apply where local law permits. We do not sell your personal data. When service partners help us with security, hosting, support, or payment reconciliation, they receive only the data needed for that task.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Controls behind this privacy wording
We keep this Privacy Policy tied to how 90x game actually operates. Our privacy wording is checked against account screens, support flows, wallet reconciliation, and security logs. When our process changes, we...
Account data mapping
We map each account field to a clear purpose, such as sign-in, verification, support handling or record accuracy. Fields without a live purpose are removed from collection flows.
Wallet record separation
Payment references from JazzCash, Easypaisa, SadaPay and Raast are stored as account records, not public profile details. Only teams handling reconciliation or privacy queries may access them.
Security access controls
Staff access is limited by role, so support can answer account questions without seeing data unrelated to the request. Sensitive changes require traceable internal approval.
Provider data scope
Game studios and stream providers may send session logs, round IDs and technical markers. We use those records to handle account history and disputes, not to expose your identity.
Retention schedule
We keep records for account service, dispute handling, security and legal needs. When a record is no longer required, we remove it or reduce it to non-identifying form.
Change tracking
Material privacy changes are dated on the page, and older wording is kept internally for comparison. This helps us answer what applied when your account data was handled.
How our legal pages stay aligned
Our Privacy Policy sits beside account terms, cookie wording, and support rules, but it has one job: explaining personal data. We keep cross-page language consistent so you do...
| Account terms link | Terms explain account use, while this Privacy Policy explains data handling. Where both pages mention verification, we keep the same meaning and avoid hidden extra collection. |
|---|---|
| Cookie wording link | Cookie text covers browser storage and measurement tools. This Privacy Policy explains how those signals connect to your account, security checks, and privacy choices. |
| Support wording link | Support scripts follow the same privacy limits shown here. Agents should ask only for details needed to answer your account question or verify your identity. |
| Payment record wording | Wallet and bank references are described consistently across help pages. The privacy rule remains the same: transaction records are used for account service and reconciliation. |
| Security wording link | Security pages may describe login protection, while this policy explains the data behind those checks, including device signals, session markers and failed sign-in records. |
| Promotion wording link | If a promo message uses account data, this policy explains the data category and purpose. You can ask us to check marketing contact settings tied to your account. |
| Update wording link | When one legal page changes, we check related pages for matching language. That reduces confusion and keeps your privacy rights described in one clear voice. |
Privacy page elements you can scan
This page is arranged so you can spot privacy details without reading every legal paragraph at once. The visible elements explain what data we collect, who...
Data category blocks
Short blocks group account, device, payment-reference and support data separately. This helps you see which details belong to identity checks and which belong to normal account service.
Purpose labels
Each privacy purpose is written in plain Pakistani English, such as verification, security, reconciliation or support. We avoid vague wording that leaves you guessing why data is needed.
Local rail chips
JazzCash, Easypaisa, SadaPay and Raast appear as context chips where wallet records are discussed. They show the records we may need when resolving account queries.
Rights section
Your access, correction and deletion request paths are separated from general support text. This makes privacy actions easier to find when you want a direct account response.
Update marker
The policy date shows when wording last changed. If we change a collection purpose or sharing practice, the updated page explains the shift in direct language.
Contact panel
Privacy contact options stay near the policy text instead of hidden in a footer. You can raise account data questions through support without searching across unrelated pages.