How cb77 Handles Your Data
cb77 brings live casino, slots and sportsbook access into one account, and this Privacy Policy explains the account data we collect, why we use it, and how we...
Our Privacy Position In Pakistan
This Privacy Policy applies when you access cb77 from supported regions in Pakistan, create or manage your account, contact our team, or use account funding channels that appear inside your cashier. We collect only the details needed to run your account flow, keep sessions secure, process identity and transaction checks, respond to your requests, and maintain records required for service integrity. That
may include your name, contact details, login activity, device signals, account preferences, support messages and transaction references. We do not sell your personal data. Where we work with payment, security, hosting or support partners, we share only what is needed for that task and require them to handle it with care. You can ask us to correct account details, clarify how a
record is used, or explain the retention period linked to your account.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
How We Keep Policy Checks Clear
Our privacy process is built around traceable account actions rather than broad claims. We record when data is collected, why it is needed, which team can access it...
Purpose mapping
Each data field is linked to a purpose such as login security, account verification, cashier reconciliation or support. We avoid...
Role-based access
Support staff see only the account records needed for their work. Wider access is restricted, and sensitive changes require checks...
Session protection
We use device and session signals to detect unusual access. These records help protect your cb77 account without exposing your...
Payment matching
Cashier records are matched through references from JazzCash, Easypaisa, SadaPay or Raast. We keep enough transaction data to trace account...
Retention checks
We keep records for service, security and legal needs, then remove or limit them when they are no longer required...
Request handling
When you ask about your data, we verify you first. That protects your account from unauthorised requests and helps us...
How This Notice Stays Consistent
This Privacy Policy sits beside our other legal pages, but it has its own job: explaining data handling. We keep wording aligned across account terms, cookie use, cashier...
| Account terms | Our account terms explain service rules, while this page explains personal data handling. Where the same account action appears, we keep the privacy wording consistent and specific. |
|---|---|
| Cookie notice | Cookie wording focuses on browser storage, analytics and session tools. This Privacy Policy explains how those signals may connect to account security and service improvement. |
| Cashier records | Cashier pages show supported Pakistan rails, while this page explains what transaction references we keep, why we keep them, and how you can ask about them. |
| Support scripts | Support replies follow privacy wording used here, especially when identity checks, contact changes or transaction records are involved. That keeps your service conversation aligned with policy language. |
| Security procedures | Security steps protect access to your profile, but the privacy notice explains the data behind those checks. We keep both areas connected without merging their purposes. |
| Update labels | When wording changes, we aim to make the change visible through clear page text rather than hidden edits. Material privacy changes may also be signalled inside account areas. |
| Plain wording | We avoid legal wording that blocks understanding. If a phrase needs to be precise, we keep the surrounding text practical so you can see how it affects your account. |
Visible Elements In This Policy
This section points out the parts of the Privacy Policy that help you read it quickly without turning it into a general product page. Each marker...
Data categories
We describe account, contact, device, session, support and transaction records separately. That helps you understand which data belongs to which part of your cb77 account activity.
Use reasons
Each main data group is tied to a reason, such as account access, security checks, cashier reconciliation or customer care. We do not rely on vague collection language.
Sharing limits
Where partners help us run hosting, payments, fraud checks or support tools, we explain the purpose of sharing and keep it tied to the service they perform.
Your choices
You can ask us to correct account details, explain stored records or consider deletion where retention is no longer needed. We verify requests before acting.
Security language
We explain security in practical terms, including access control, session monitoring and identity checks. The aim is to show how privacy and account protection work together.
Regional wording
Because cb77 serves supported regions, this policy uses Pakistan context and local payment references while noting that access depends on where local law permits.