Terms page
The Terms page explains account use; this Privacy Policy explains the personal data attached to those account actions, including login checks, profile details, wallet references, and support history.
LEGAL REFERENCE
How bb98 protects your privacy
bb98 keeps your account privacy plain: we explain what data we collect, why we need it, and how it connects to your casino, slots, sportsbook, and payment activity...
Pakistan privacy wordingAccount data rulesWallet record handlingSecurity access checks
Policy posture for Pakistan accounts
This Privacy Policy explains how bb98 handles personal data connected with your account, lobby access, identity checks, wallet activity, support contact, device signals, and security logs. Access to bb98 is offered in supported regions where local law permits, so our data handling may include checks needed to keep account use consistent with local rules. We collect only the data needed to operate
your account, process payment records, respond to your requests, and protect the lobby from misuse. We do not sell your personal data. We share data only with service partners who help us run account access, payments, fraud checks, hosting, analytics, and support, and only under controlled terms.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
DATA CHECKS
How we keep this policy current
We treat the Privacy Policy as an active bb98 control, not a static page. When account flows, payment partners, security checks, or support routing changes, we check whether the wording still matches...
Change checks
Before a new account field appears, we check why it is needed, where it is stored, and whether the Privacy Policy should explain that collection in clearer wording.
Payment partner mapping
JazzCash, Easypaisa, SadaPay and Raast records are mapped against wallet screens, support tickets, and reconciliation logs so our policy reflects the payment data you may see on account pages.
Security log limits
Device, IP, session, and login signals are kept for account protection and misuse checks. We limit access to staff who need those records for security or privacy requests.
Support training
Our support team is trained to avoid asking for full wallet secrets, card credentials, or private codes. Privacy cases are escalated when the request concerns stored account data.
Supplier controls
Hosting, analytics, payment, and fraud-check partners receive only the data needed for their assigned work. We assess whether each partner still needs access when flows change.
Policy date care
When wording changes in a material way, we update the page date and keep the new text focused on practical account, payment, support, and security handling.
LEGAL ALIGNMENT
Consistency across our legal pages
Our Privacy Policy works with the other bb98 legal pages, but it has its own job. It explains data handling only. Where another page speaks about account rules, offers, or service use...
Cookie page
The cookie page explains browser storage; this Privacy Policy connects that storage to wider account data, analytics signals, security checks, and choices you can raise with support.
Promotions page
Offer pages may ask you to meet stated rules; this Privacy Policy explains what account and activity data may be checked when bb98 confirms offer eligibility.
Payment terms
Payment wording explains wallet flow; this Privacy Policy explains how JazzCash, Easypaisa, SadaPay and Raast references are used for reconciliation, checks, support, and record keeping.
Security wording
Security pages explain access protection; this Privacy Policy explains the device, session, IP, and verification data we use to detect account access that looks unusual.
Support terms
Support wording explains how to contact us; this Privacy Policy explains how chat transcripts, email messages, screenshots, and account identifiers are stored and used to answer you.
Account closure
Closure wording explains how an account can end; this Privacy Policy explains which records may remain afterward for legal, payment, security, or dispute handling needs.
Privacy layout you can scan
This page is arranged so you can find the privacy point you came for without reading unrelated material. We use short labels, local payment examples, and...
Plain section labels
Each section names the privacy issue first, then explains the bb98 account flow behind it, so you can connect policy wording with real screens you may use.
Local wallet context
Where payment data is discussed, we name JazzCash, Easypaisa, SadaPay and Raast because those references make the policy clearer for your Pakistan account records.
Account-first wording
We describe data by account action, such as opening an account, logging in, using support, or requesting a wallet check, rather than using vague legal language.
Retention cues
When records may be kept after an account action, we explain the reason in practical terms, such as payment reconciliation, security checks, support history, or legal requirements.
Sharing boundaries
The policy separates bb98 use from service-partner use, so you can see when data stays with us and when limited data helps hosting, payments, analytics, or security.
Request prompts
Where you can ask us about data, we state what to include in the message, helping us locate the right account record without asking for sensitive wallet secrets.
Privacy questions before you join
We collect account details, login signals, device data, support messages, payment references, and activity records needed to operate your bb98 account, protect access, answer requests, and manage services in supported regions.
Payment references help match JazzCash, Easypaisa, SadaPay and Raast activity with your account. We use them for reconciliation, support checks, fraud prevention, and record keeping, not for selling your personal data.
Yes. Contact support from your registered email and explain what should be corrected. We may ask for account checks first, especially if the change affects wallet records or account security.
We share limited data with partners who provide hosting, payments, security checks, analytics, or support tools. They receive only what is needed for that task and must handle it under agreed controls.
Retention depends on the record type. Some support chats can be shorter, while payment, security, dispute, or legal records may be kept longer where needed for account protection and compliance.
We use access controls, session checks, device signals, and staff permissions to reduce unnecessary exposure. If a login looks unusual, we may use those records to protect your account.
Use email or chat and include your account email, the request type, and any relevant payment reference. Do not send wallet passwords, private codes, or screenshots showing sensitive credentials.