How b99 Handles Your Data
b99 keeps privacy terms for account records, lobby activity and Pakistan payment references in one clear policy, so you know what we collect before you open your account...
Privacy Policy Scope For Pakistan
This Privacy Policy explains how b99 handles personal data when you create an account, access casino or slot areas, contact support, or use Pakistan payment rails in supported regions. We collect details you give us, device and session data, payment references, verification records, and messages needed to run your account safely. We use this data for account access, fraud checks, transaction tracing,
service messages, dispute handling, and legal duties where local law permits. We limit access inside our team, keep records only as long as needed, and ask partners to protect any data they process for us. If you ask about your data, we check account ownership before replying.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Reach Us About Privacy
Privacy questions need a clear path, not a maze. Use the contact route that matches your account status, and include only the details needed to identify the issue. We may ask for account checks before discussing personal data, especially where payment references or access logs are involved.
Account inbox
Use the email linked to your b99 account when asking for access, correction or deletion checks. That helps us match your request without exposing data to a different contact address.
Live chat handoff
Chat can receive privacy requests, then move them to the correct team if records need deeper checks. We avoid sharing sensitive account details inside an open chat window.
Payment query path
For JazzCash, Easypaisa, SadaPay or Raast privacy questions, send the transaction reference and date only. We do not need wallet passwords or full banking access from you.
How We Keep This Current
We write this policy from the way b99 actually handles account records, not from template language. When product, support or payment flows change, we check whether the Privacy...
Operational wording
The policy reflects real account steps, including login checks, verification screens and support requests. We avoid vague privacy promises and...
Local payment context
Pakistan payment references can carry names, phone-linked wallet details and transaction IDs. Our policy explains why those records are stored...
Access control
Only staff roles that need a privacy record for support, security or payment tracing should see it. Internal access is...
Change checks
When we adjust account forms, verification steps or contact channels, the privacy wording is checked against those changes. That keeps...
Plain contact duties
Privacy requests are handled through account-matching steps before data is shared or changed. This reduces the chance of another person...
Retention focus
We keep account and payment records for service, security and legal needs, then remove or reduce them when they are...
How This Policy Fits Others
The Privacy Policy sits beside our other legal pages, but it has a different job. It explains personal data, not game rules or promotion terms. We keep wording...
Privacy Signals Across The Page
This page is designed so privacy points are easy to scan before you open or use an account. Headings separate collection, use, sharing, retention and contact...
Clear section labels
Each block names the privacy action it covers, such as data collection, sharing or retention. You should not need legal training to find the part that affects you.
Account context
Privacy wording stays tied to b99 account steps, including registration fields, login records and verification checks. That makes the policy easier to compare with your actual account journey.
Pakistan rails named
Where payment data is discussed, we name JazzCash, Easypaisa, SadaPay and Raast so you can see how local references may be used for matching and support.
Plain retention cues
Retention wording explains why records may remain after a transaction or support case. It also sets out that unnecessary data should be reduced or removed when purposes end.
Request prompts
The policy points you toward the right channel for access, correction and deletion questions. We ask you to verify control of the account before personal data is discussed.
Sharing boundaries
When partners help with hosting, payments or security, the policy explains why limited data may be shared. It also states that use should stay tied to those tasks.