Terms link
Our terms explain account rules, while this policy explains the personal data behind those rules. If an account action creates a record, this page describes the privacy angle.
LEGAL REFERENCE
Privacy Policy for Your cb44 Account
cb44 places the privacy rules beside your account journey, so you can see how personal data supports login checks, lobby access and cashout verification where local law permits...
Pakistan privacy scopeAccount data useSecurity checksSupport contact paths
How We Handle Your Data
This Privacy Policy explains how cb44 collects, uses, stores and shares personal data connected with your account in supported regions of Pakistan. We collect data you provide during account creation, identity checks, support chats and transaction handling, plus technical records such as device signals, session activity and security logs. We use that data to operate your account, protect access, process withdrawals, answer
privacy requests and meet legal duties where local law permits. We do not sell your personal data. Limited sharing may happen with payment processors, security vendors, hosting providers and compliance partners, but only for the purpose tied to your cb44 account. We keep records for as long as needed for account, legal, security and dispute reasons, then delete or anonymise them when
retention no longer applies.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
POLICY CHECKS
Privacy Controls Behind This Page
We write this policy from how cb44 actually handles account data, not from a template alone. The wording is checked against support flows, payment records, login controls and vendor access so the...
Account access records
Login history, device signals and session checks help us spot unusual access. We use these records for security, account recovery and dispute handling, not for unrelated public profiling.
Local transaction context
JazzCash, Easypaisa, SadaPay and Raast references may appear in account records when you use those rails. We keep only the data needed to reconcile and verify the account event.
Limited vendor access
Service partners receive only the data needed for hosting, fraud checks, support handling or transaction processing. Access is role-based, logged and removed when the business need ends.
Policy ownership
Our operations and support teams flag privacy wording when account flows change. Updates are made so your choices, contact routes and retention details remain clear.
Request verification
Before we act on access, correction or deletion requests, we verify the person asking. This prevents another person from using a privacy request to reach your account data.
Retention discipline
We keep account records only for operational, legal, security and dispute needs. When those reasons end, we delete, mask or aggregate records so they no longer identify you.
PAGE ALIGNMENT
How Our Policies Stay Consistent
The Privacy Policy connects with our terms, cookies wording and support rules, but it has its own job. This page focuses on personal data: what we collect, why we use it, who...
Cookie wording
Cookie details cover browser storage and tracking choices. This Privacy Policy adds how those technical signals connect with login protection, session continuity and security monitoring.
Support records
Support pages tell you how to reach us. This policy explains how chat transcripts, ticket history and identity checks are handled after you contact cb44.
Payment records
Cashier pages may name local rails. This policy explains how related account records are stored, verified and shared only with parties needed to complete the account process.
Security pages
Security wording explains protection tools. This policy adds the data side, including device logs, access alerts and fraud-prevention checks linked to your cb44 profile.
Promo board
If you check the promo board, account eligibility may create records. This policy explains how those records are used for account display, checks and support follow-up.
Regional access
Where local law permits, regional checks may affect access. This page explains the privacy data used for location, device and account verification connected with that process.
Visible Privacy Cues Across cb44
We place privacy cues where they matter in the account flow, not only on this legal page. You will see short labels near forms, support tickets...
Form labels
Account forms explain why core details are requested. We keep labels short, then link back to this policy when the reason needs fuller privacy wording.
Verification prompts
When identity checks are needed, the screen explains the purpose before upload. The policy then covers retention, access controls and how verification files are protected.
Session notices
If a new device or unusual session appears, privacy-related security prompts may show. These prompts explain the data signal without exposing sensitive account details.
Chat reminders
Support chat reminds you not to share passwords or unrelated documents. Our privacy process keeps ticket records tied to the issue raised and the account involved.
Cashout checks
Withdrawal verification may require matching account and transaction records. This policy explains why those checks exist and how related data is kept under limited access.
Update markers
When we adjust the policy, the page date and wording changes show what moved. Material changes are written plainly so you can understand the effect.
Common Questions About cb44 Privacy
We collect account details you provide, verification records, support messages, transaction references and technical signals such as device, session and security logs. Each category supports account operation, protection or legal handling.
Payment-related records help us reconcile JazzCash, Easypaisa, SadaPay or Raast activity with your cb44 account. We use them for verification, dispute checks, cashout handling and required record keeping.
Yes. Contact us from your registered email or account support channel and explain what should be corrected. We verify the request first, then update eligible records or explain why a record must remain.
We share limited data with service partners only when needed for hosting, payments, security checks, customer support or legal duties. Partners receive role-based access connected to the task they perform.
Retention depends on the record type and the reason for keeping it. Account, payment, security and dispute records may be kept while operational or legal needs apply, then deleted or anonymised.
Use the contact path linked to your cb44 account and describe the request clearly. We may ask for verification before acting, because privacy changes can affect access, records and security.