Privacy Policy for cb888 Pakistan accounts
cb888 gives you a clear Privacy Policy for the account, device and payout data tied to casino access in supported regions of Pakistan. Before you open your account...
Our privacy posture in Pakistan
Our Privacy Policy explains what we collect when you create an account, move through the lobby, contact support or request a payout where local law permits. We collect only the details needed to run your account, verify access, process payment references and protect the service from misuse. That can include your name, mobile number, device signal, IP address, login history, game-session records,
KYC files and transaction references from Pakistan rails. JazzCash, Easypaisa, SadaPay and Raast details are used to match your account with cash-in and payout activity, not to sell your personal data. We keep records for legal, tax, fraud-control and account-service reasons, then reduce or remove them when retention is no longer needed.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
How we keep policy wording current
We write this Privacy Policy from the same account flows we operate every day. When login security, payment handling or support routing changes, our internal checks look at whether the wording still...
Account-flow checks
We compare policy wording with the current join form, login screen and KYC prompts. If a field is added or removed, the privacy text is checked for accuracy before release.
Payment rail mapping
JazzCash, Easypaisa, SadaPay and Raast references are mapped to the data we actually receive. We state the purpose clearly: account matching, reconciliation, payout checking and fraud-control activity.
Security wording
Security sections are aligned with real controls such as password resets, device checks, session logs and unusual-access flags. We avoid vague wording that hides what data is involved.
Support training
Support staff receive privacy scripts for identity checks, ticket escalation and data correction requests. This helps keep your request private while still giving you a clear next step.
Retention checks
Record-retention wording is checked against account, finance and security needs. We keep data only while there is a valid service, legal or risk-control reason to hold it.
Change logging
Policy edits are logged with dates and internal owners. This lets us trace why wording changed when payment rails, verification steps or support processes are adjusted.
Policy consistency across cb888 pages
Your privacy rights should read the same wherever you meet them on cb888. We align this page with cookie, terms, account and support pages so the same data...
| Cookie page | Cookie wording matches this Privacy Policy by naming device signals, session tools and preference storage. If you change cookie choices, the privacy page still explains the related account data. |
|---|---|
| Terms page | The Terms explain account rules, while this page explains personal data use behind those rules. We keep fraud checks, verification steps and payout matching consistent across both pages. |
| Account form | Fields requested during account creation are reflected here, including contact details and identity checks. We do not ask for data on the form without a matching privacy purpose. |
| Login screen | Login security text connects with our privacy wording on device signals, IP checks and session records. This helps you understand why access events may be stored. |
| Payout screen | The payout screen collects rail references and account-name checks. This Privacy Policy explains how those records support matching, reconciliation and risk-control work before funds are released. |
| Support centre | Support pages use the same request language for data correction, access questions and privacy concerns. If your case needs identity checks, the support wording matches this policy. |
| Promo board | If you choose to receive promo messages, the preference wording connects with this page. You can ask us to change contact choices without affecting required account security alerts. |
Privacy layout inside your account
We place privacy cues near the actions that create data, not only on this legal page. Account settings, payout checks, support tickets and message preferences each...
Short field labels
Forms use short privacy labels beside sensitive fields such as mobile number, identity file and payment reference. The aim is to explain the reason before you submit the detail.
Account settings
Your settings area groups contact details, security actions and message choices separately. That layout helps you change personal data without mixing it with login protection or payout checks.
Request status
Privacy tickets show a simple status so you know whether we need identity proof, have passed the request to a specialist, or have completed the action requested.
Security prompts
When a login looks unusual, security prompts explain why extra confirmation may be needed. The same section links back to this Privacy Policy for the data behind those checks.
Message choices
Contact preferences are shown apart from mandatory service alerts. You can adjust optional messages while still receiving account-security, payout and policy-change messages we need to send.
Plain change dates
When this policy changes, the date appears near the page heading. We also keep wording direct so you can compare what changed without decoding legal phrasing.