90 games Privacy Policy for Pakistan
90 games sets out how your account data, device signals and transaction records are handled when you use our casino online and sportsbook in supported regions of Pakistan...
How We Handle Your Data
This Privacy Policy explains our posture on personal data, account security and transaction records for 90 games where local law permits access. We collect only the details needed to create your account, keep access secure, process identity checks, manage wallet activity and respond to privacy requests. Device data, login records and payment references may be stored to prevent unauthorised access and resolve
disputes. We do not sell your personal data. Limited service partners may process records for hosting, fraud checks, support handling or payment reconciliation, and they are expected to handle those records under written controls. When laws, banking rules or security needs require retention, we keep the relevant records for the required period and then delete or anonymise them where practical.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Privacy Help Without Confusion
If you want to ask about access, correction, deletion or consent choices, contact us through the routes below. We verify the account first so that privacy requests are answered to you, not to anyone pretending to act for you.
Account inbox
Write to the privacy contact from the email linked to your 90 games account. Include your username, the request type and any relevant date range so we can locate records without asking for extra personal detail.
Live chat handover
Use live chat for a quick privacy request start, then our team may move the matter to email for identity checks. This keeps account records away from public devices or shared screens.
Document channel
If we ask for proof during a privacy request, send it only through the secure upload path we provide. Do not share CNIC images, wallet screenshots or bank files in open chat.
Checks Behind This Policy
Our policy text is maintained by the same team that handles account flows, payment reconciliation and support escalation. That connection matters because privacy wording should match what actually happens inside 90 games...
Operational ownership
The policy is tied to account opening, login, wallet activity and support handling. When one of those flows changes, the privacy wording is checked so your data path remains clearly described.
Local phrasing
We write for Pakistani account holders using plain English and familiar payment names. JazzCash, Easypaisa, SadaPay and Raast are referenced as context where payment records may connect with account checks.
Security alignment
Login records, device signals and password reset events are covered because they protect your account. The policy explains why those records are collected and how they support access control.
Retention discipline
Records are not kept forever by default. We apply retention periods based on legal needs, dispute handling, fraud prevention and technical logs, then remove or anonymise data where practical.
Partner controls
Where processors help with hosting, analytics, payment checks or support tools, we restrict their role to the service they provide. They should not use your personal data for unrelated purposes.
Change tracking
When policy wording changes, we adjust the visible date and keep internal records of what changed. If a material privacy change affects your choices, we aim to make it clear.
Aligned Across Legal Pages
Privacy touches more than one legal page, so our wording is kept consistent across related areas. This section explains how the Privacy Policy connects with nearby pages without...
| Terms connection | The Terms page explains account conduct, while this Privacy Policy explains the data used to operate that account. Where the two meet, privacy wording controls how personal records are handled. |
|---|---|
| Cookie connection | The cookie page deals with browser storage and similar tools. This Privacy Policy points to that area when device or session data is collected through cookies or comparable technology. |
| Security connection | Security wording explains protections around access, while this policy explains the personal data behind those protections. Login alerts, reset attempts and device checks are treated as privacy-relevant records. |
| Wallet connection | Wallet pages may describe transaction steps, but this policy covers the account data tied to those steps. References, timestamps and reconciliation records are handled for accuracy and dispute support. |
| KYC connection | Identity checks may require documents or matched details. This Privacy Policy explains why those records are requested, how they are used and why access is limited within our team. |
| Support connection | Support pages describe how to reach us, while this policy covers privacy around those conversations. Chat logs, email threads and verification replies may be stored to resolve your request. |
| Game log connection | Game and sportsbook records can include timestamps, session identifiers and settlement references. This policy treats those records as account activity used for accuracy, security checks and dispute handling. |
Privacy Layout You Can Read
This page is arranged so you can find privacy answers without scanning unrelated sales copy. Headings, short chips and contact cards show where your data is...
Layered headings
Each heading deals with one privacy theme, such as collection, sharing, retention or rights. The layout avoids mixing account promotions with data handling so your choices stay easy to locate.
Plain labels
Labels use direct wording like account data, payment records and support logs. We avoid legal fog where a shorter phrase can explain the same privacy point more clearly.
Local chips
Short chips show Pakistani context without turning the policy into a wallet page. JazzCash, Easypaisa, SadaPay and Raast appear only where transaction records affect privacy handling.
Rights panel
Rights-related wording sits close to contact paths so you can act after reading. Access, correction and deletion requests are explained with the verification step needed to protect your account.
Retention strip
Retention language is grouped so you can see why some records are kept longer than others. Legal needs, disputes, fraud checks and technical logs each have different privacy reasons.
Contact box
The contact area separates privacy requests from general account help. That separation helps us route sensitive records to staff who understand verification, disclosure control and data handling rules.