99ar Privacy Policy for Pakistan
99ar gives you casino, slots and sportsbook access through an account flow where privacy matters from the first form field. This Privacy Policy explains what data we collect...
How We Handle Your Data
Our Privacy Policy is written for your 99ar account journey, from registration details to login security, payment checks and support messages. We collect only the data needed to run your account, verify access, process transactions, protect the lobby from misuse and answer your privacy requests. Where local law permits, we may use Pakistani payment context such as JazzCash, Easypaisa, SadaPay and Raast
receipts to match deposits or withdrawals with your account record. We do not sell your personal data. Access to internal records is limited to staff roles that need it for account operations, fraud checks, technical fixes or legal duties. When data is no longer needed, we either delete it or keep it only for required record periods tied to finance, security or
dispute handling.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
How Our Policy Stays Accurate
We keep this Privacy Policy tied to the way 99ar actually operates in Pakistan. When our account forms, verification steps, support tools or transaction checks change, the policy...
Operational ownership
The policy is maintained by people who work with account flows, transaction checks and support records. That keeps the wording...
Local payment context
JazzCash, Easypaisa, SadaPay and Raast records can create receipts, timestamps and reference numbers. Our policy explains how those details help...
Access controls
Your personal records are not open to every internal tool. Staff access is role-based, logged where suitable, and used for...
Device and login checks
We may process device type, IP region, session time and login events to protect account access. The policy separates these...
Retention checks
We keep records for operational, finance, security and legal reasons, then remove or restrict them when those reasons end. Retention...
Clear request handling
When you ask to access, correct or question your data, we first confirm account ownership. That step protects you from...
Aligned Privacy Pages Across 99ar
Privacy wording should not feel different from one 99ar page to another. We keep account, cookie, security and contact language aligned so you are not left guessing which...
| Account page consistency | The same privacy meaning applies when you create your account, edit your profile or pass a verification check. Short form labels may differ, but the policy basis remains the same. |
|---|---|
| Cookie page consistency | Cookie and device wording connects back to this Privacy Policy. If a cookie helps login security, performance measurement or session continuity, the related data purpose is described in matching language. |
| Security page consistency | Security messages on 99ar refer to the same login traces, device checks and account alerts explained here. We avoid separate wording that would make one security purpose sound like another. |
| Transaction page consistency | Payment screens may show JazzCash, Easypaisa, SadaPay or Raast references, but privacy handling stays under this policy. Transaction records are used for matching, verification and dispute handling. |
| Support page consistency | When support collects screenshots, phone numbers or chat text, the same privacy standards apply. Sensitive details should be shared only through the channel we provide for your account issue. |
| Promo page consistency | If you check a promotion area, we may record eligibility signals and account activity needed for that offer. The policy still controls how those records are stored and limited. |
| App page consistency | Mobile web and app-like access use the same privacy approach. Device permissions, session data and account checks are treated according to this policy, not a separate hidden standard. |
Visible Privacy Touchpoints Across 99ar
You will see privacy signals at the points where data is entered, checked or shared with us. These layout markers help you understand why a field exists before...