LEGAL REFERENCE

Privacy Policy For Your b99u Account

b99u keeps live casino, slots and sportsbook account data under one Privacy Policy for Pakistan, so you can open your account knowing what we collect and why. Read...

Pakistan privacy scopeJazzCash contextEasypaisa contextRaast account checks
b99u Privacy Policy For Your b99u Account

How We Handle Your Account Data

Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.

CONTACT PATHS

Ask Us About Privacy Choices

If your privacy question is tied to account access, payments, or live table history, contact us through the channel that matches the...

Privacy email Use the privacy email when your question needs...
Live chat privacy handoff Open live chat for quick routing if you...
Payment record query If a transaction reference appears wrong, send the...
CARE CHECKS

How We Keep This Policy Current

We write this Privacy Policy from the way b99u actually handles account flow in Pakistan. Each change is checked against support practice, payment reference handling, device security, and live casino access. We...

Version log

We record each policy edit with the reason for change, the date it went live, and the team area affected. That helps us explain older wording if you ask about a past privacy term.

Pakistan wording

The policy uses plain Pakistani English, including local wallet names you recognise. We explain how JazzCash, Easypaisa, SadaPay, and Raast references relate to b99u records without copying bank wording.

Access control

Only authorised staff can open privacy request records, and internal access is limited by role. Support can route a request, but deeper account data checks sit with trained operations staff.

Service partners

Where we use hosting, security, analytics, or payment-service partners, we share only the data needed for that service. Contracts require handling that matches our Privacy Policy duties.

Device safeguards

We use device, browser, and session signals to detect unusual access and protect your account. The policy explains why these checks exist and how they connect with login history.

Data minimising

We aim to keep data collection tied to a clear purpose, such as account access, verification, support, payment tracing, or security. Extra data is not requested when a smaller check works.

Consistent Terms Across Our Policy Pages

This page should read together with our Terms, Cookie Policy, and account rules. We keep the wording aligned so privacy rights, security duties, and data-sharing reasons do not...

Terms alignment
Our Terms explain account use, while this Privacy Policy explains data handling behind that use. We keep both pages aligned so identity checks, suspension records, and access history are described consistently.
Cookie policy link
Cookie wording covers browser storage, analytics tags, and session tools. This Privacy Policy points to those details when they affect account access, fraud checks, or your choices on repeat visits.
Account rules
Account rules may require accurate details and secure login behaviour. The Privacy Policy explains why those details are collected, who checks them, and how correction requests are handled.
Promotions records
If you join an offer, we may keep eligibility, opt-in, and reward records. This page explains the privacy side of those records, separate from offer rules and expiry terms.
Security wording
Security pages describe safeguards such as password resets and unusual-login checks. This policy explains the related data signals, including device markers and support verification steps.
Payment references
Payment pages focus on movement of funds, while this page focuses on related personal data. We separate wallet references from unnecessary wallet content whenever the privacy task allows.
Lawful access
Access is described as available in supported regions where local law permits. The same wording is used across policy pages so your account status and privacy rights stay clear.

What This Policy Shows Clearly

We shape the privacy page around quick reading, not legal fog. The visible layout shows what data we collect, why we use it, when we share...

Purpose blocks

Each main block connects a data type with a reason, such as login security, account support, transaction tracing, or service improvement. That makes the policy easier to scan before you join.

Local chip row

Short chips show Pakistan-facing context, including JazzCash, Easypaisa, SadaPay, and Raast. They are reminders of where privacy records may connect with wallet or transfer references.

Choice language

The page explains access, correction, deletion, and objection requests in direct wording. We also state when a request may need identity checks before account data is changed.

Sharing map

You can see the categories of partners that may receive limited data, including hosting, security, analytics, verification, and payment-service partners. We explain the purpose instead of hiding it.

Retention cues

Retention wording tells you why some records stay after account closure, such as dispute handling, fraud prevention, tax duties, or legal requests. It also separates active account data from archived records.

Action prompts

Privacy contact prompts sit near the relevant wording, so you can ask for help without searching across the site. We include what to send and what not to send.

Privacy Policy Questions For Pakistan

We collect account details, contact data, login records, device signals, support messages, and transaction references needed for access, verification, security, payments, and help requests. We do not ask for wallet PINs or full banking secrets.

Payment references help us match JazzCash, Easypaisa, SadaPay, or Raast activity to your account, confirm status, and resolve disputes. We keep the reference trail separate from extra wallet content that we do not need.

Yes, you can ask us to correct account details where your request is lawful and verified. We may ask for proof of ownership before making changes, especially if the update affects withdrawals or login recovery.

We share limited data with partners that help us run hosting, security, analytics, verification, support tools, and payment services. They receive only what is needed for that task under privacy and security duties.

We use session records, device signals, password controls, and unusual-access checks to help protect your account. These privacy records support security decisions without asking you to share private wallet codes.

Retention depends on the record type and legal need. Account access data, payment references, and support records may remain while needed for disputes, fraud prevention, accounting, or lawful requests, then move toward deletion.

Send your privacy request through email or live chat routing, using the mobile number linked to your account. Do not share wallet PINs; send only the details needed to verify and handle your request.