LEGAL REFERENCE

Privacy Policy For Your cb88 Account

cb88 keeps the privacy rules for your account, casino lobby activity, and support chats in one clear place before you open an account. Read how we handle data...

Pakistan account privacyJazzCash contextEasypaisa contextConsent choices
cb88 Privacy Policy For Your cb88 Account

How cb88 Handles Personal Data

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

HELP CHANNELS

Contact Us About Privacy

You can ask us about this Privacy Policy through the same service routes used for account help. Please include your registered mobile...

Live chat Use chat from your signed-in account when you...
Email desk Send detailed privacy requests by email when you...
Account centre Open your account centre to check profile details...
POLICY CHECKS

How We Check This Policy

We keep this Privacy Policy close to the way cb88 actually runs. The wording is checked against account forms, login flows, support tools, and Pakistan payment context before...

Account form match

We compare the policy against the fields requested during account creation, including mobile number and profile details. Any new field...

Access record checks

Login time, device type, and security signals are covered because they help protect your account. We explain these records without...

Support script alignment

Our support team uses the same privacy wording you see here. That keeps chat replies consistent when you ask about...

Payment context check

References from JazzCash, Easypaisa, SadaPay, and Raast may appear in account records. The policy explains that context without exposing full...

Partner access control

Service partners may help with hosting, security, or messaging. We restrict shared fields to the work being performed and keep...

Update log discipline

Policy edits are checked before release, with attention to changed wording, new data categories, and local access wording. We avoid...

How This Policy Connects With Other Pages

Your privacy rights do not sit alone. This page is read beside our terms, cookie text, account rules, and support procedures so each page carries a clear role...

Terms page
The terms explain account use, while this Privacy Policy explains data handling. We keep the split clear so you know whether a paragraph is about conduct or personal data.
Cookie page
Cookie wording covers browser storage and tracking choices. This policy connects those tools to account security, session handling, and service analytics in plain Pakistan-focused English.
Account rules
Account rules may require accurate details. The privacy page explains why those details are collected, how corrections can be requested, and how identity checks are protected.
Promotion terms
Promotional rules may mention eligibility checks. This page explains the data side of those checks, including account status, region signals, and contact preferences where they apply.
Support records
Support procedures explain response handling. This Privacy Policy explains how chat transcripts, email threads, and request history may be stored for service quality and dispute handling.
Security notices
Security notices tell you about account protection steps. This page explains related data such as login alerts, device markers, and verification records used to manage access.
Regional wording
Where access depends on supported regions, the same wording is kept across related pages. That avoids mixed messages about availability and privacy handling for Pakistan accounts.

What This Page Makes Clear

This Privacy Policy is designed so you can scan the parts that affect your account before opening or updating it. The layout separates collection, use, sharing...

Plain labels

Each policy area uses a short label, so you can jump from collection to retention without reading unrelated sections first. The aim is faster privacy reading, not vague legal phrasing.

Local examples

Pakistan examples appear where they matter, such as mobile numbers and wallet references. They help you understand real account records without changing the legal meaning of the policy.

Data purpose links

We connect each data category to a purpose, such as access security or support handling. That way you can see why cb88 asks for a detail.

Choice markers

Where a choice is available, we say how to use it and what may change afterward. Some records must stay while an account or dispute remains active.

Retention cues

Retention wording explains that records are kept only as long as needed for service, legal, security, or dispute reasons. We avoid open-ended language where a period can be described.

Request route

Privacy contact options sit close to the policy text, so you do not have to search another page. Use them for access, correction, or deletion questions.

Privacy Policy Questions Answered

We collect details needed to run your account, such as name, mobile number, login records, device signals, support messages, and transaction references. Some fields are collected only when a feature requires them.

Login and device records help us identify unusual access, protect your account, and resolve disputes. They also help support check whether a privacy request is coming from the right account holder.

They add local context to transaction records, but we do not need full wallet credentials for routine support. References may be stored to reconcile account activity and answer your payment-related privacy questions.

Yes. Contact us with the field that looks wrong and the correct detail. We may verify your identity before making changes, especially where the update affects account access or transaction records.

We keep records for the period needed to provide service, manage security, meet legal duties, and handle disputes. When a record is no longer needed, we remove it or reduce identifying detail.

We may share limited data with service partners that help with hosting, security, analytics, messaging, or support tools. They receive only what is needed for their task and must protect it.