Privacy Policy
This page explains personal data collection, storage, sharing and request choices tied to your cb99 account, including cookies, device checks and transaction records.
LEGAL REFERENCE
Privacy Policy for your cb99 account
cb99 keeps account data, device checks and Pakistan transaction records under one Privacy Policy, so you know what we collect before you open your account. Read this page...
Account dataCookie choicesDevice checksPakistan records
How our policy treats your data
Our Privacy Policy explains how cb99 collects, stores, uses and shares data connected with your account in supported regions of Pakistan. We collect details needed to create your profile, protect sign-ins, process identity checks and keep transaction records linked to channels such as JazzCash, Easypaisa, SadaPay and Raast. We also record device signals, cookie choices and support messages so we can keep
account access stable and answer privacy requests. We do not sell your personal data. When a legal request, fraud check or service partner requires limited access, we keep the sharing narrow and tied to the purpose described here.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
CHECKED WORDING
How we keep this policy current
We update this Privacy Policy when account forms, security checks, cookie tools, wallet record handling or service partners change. The policy is written by our operating team with input from support and...
Change tracking
Each policy edit is logged internally with the reason for change, such as a new cookie setting, account field or support process affecting your privacy choices.
Account-flow testing
Before wording is changed, we compare it with the live account journey so the policy matches what you see during sign-in, verification and profile updates.
Security input
Our technical team confirms how device checks, session records and login alerts work, so privacy wording reflects the controls used to protect your account.
Support feedback
Questions sent by you through email or chat help us clarify policy language, especially around access requests, cookie settings and record correction steps.
Partner checks
Where service partners process limited account or transaction records, we describe the purpose and keep the policy aligned with the data they actually receive.
Plain English
We write this policy in clear Pakistani English, avoiding legal clutter where possible while still explaining collection, storage, sharing and your privacy request paths.
SAME STANDARD
Consistency across our policy pages
Your privacy rights should not depend on which cb99 page you read first. We align this Privacy Policy with account terms, cookie text and security messages so the same data categories, request...
Cookie text
Cookie wording is kept consistent with this policy, so browser storage, analytics signals and preference choices are described in the same privacy language.
Account terms
Where account terms mention verification or security checks, this policy explains the related personal data use and the records we keep for that process.
Security messages
Login alerts and device prompts use wording that matches this policy, helping you understand why a session check or additional confirmation may appear.
Wallet records
Transaction privacy wording stays consistent across account pages, including references to JazzCash, Easypaisa, SadaPay and Raast record handling where relevant.
Support replies
When our team answers privacy requests, the response should mirror this policy, including the verification step, expected scope and available account actions.
Regional access
Where access is described, we use supported regions and where local law permits, keeping privacy wording careful for Pakistan-facing account activity.
Visible markers inside this policy
This page is structured so you can find privacy details without searching through unrelated account content. We place data categories, request contacts, cookie wording and update...
Date marker
The policy area shows when wording has changed, so you can tell whether the privacy terms you read are current for your account session.
Data categories
We group account details, device records, cookies and transaction references separately, helping you see why each data type is collected and used.
Choice cues
Where you can change cookies or update profile details, the policy points you toward the relevant account control instead of hiding the step.
Sharing labels
Any limited sharing is described by purpose, such as security, verification, support handling or legal response, so the wording stays specific.
Retention signals
We explain that records are kept only as long as needed for account operation, legal duties, fraud checks and privacy request handling.
Contact placement
Privacy contact routes are placed near the policy text, making it simple to ask about stored data, correction or available deletion steps.
Privacy questions before you join
We collect account details you provide, sign-in records, device signals, cookie choices, support messages and transaction references needed to operate your account and keep privacy records accurate.
Device and login records help us identify unusual access, keep sessions stable and confirm account ownership when you contact us about privacy, profile changes or security concerns.
Records linked to JazzCash, Easypaisa, SadaPay and Raast are handled as transaction data. We use them for account matching, verification, reconciliation and required record keeping.
Yes, you can ask us to check account details that appear wrong. We may verify ownership first, then correct eligible records or explain why a record must remain.
Yes, cookies and similar tools help remember preferences, protect sessions and understand site performance. Where choices are available, the policy points you to the relevant setting.
Support messages are limited to staff who need them to answer your request, verify your account or handle a privacy matter. We keep access restricted by role.
Use the account help area or email us from your registered address. Include the privacy request type, account identifier and the data you want us to check.