Privacy Policy at ct66
ct66 keeps your account, identity checks, device data, and Pakistan payment records under one privacy policy. Open your account only after reading how we collect, use, store, and...
How We Handle Your Data
This Privacy Policy explains what ct66 collects when you create an account, verify access, browse the lobby, contact support, or use payment rails available in supported regions. We collect details you give us, records created by security checks, device signals, session logs, cookie data, and transaction references linked to JazzCash, Easypaisa, SadaPay, NayaPay, or Raast. We use those records to run your
account, confirm withdrawals, detect misuse, answer privacy requests, and meet legal duties where local law permits. We keep access limited to trained teams and service partners that need the data for account operation, fraud checks, hosting, payments, or customer care.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
How Our Policy Is Checked
We write this Privacy Policy from the way ct66 actually runs accounts for Pakistan. The wording is checked against login flows, payment verification, cookie behaviour, support scripts, and withdrawal checks before it...
Operational input
Our account, payment, and support teams share the data fields they actually collect. That keeps the Privacy Policy tied to working ct66 screens rather than abstract wording.
Security controls
Access to personal records is role based, logged, and limited to staff handling verification, support, withdrawals, or risk checks. Shared files use controlled folders rather than open links.
Cookie checks
We map cookies used for login continuity, fraud screening, language choice, and session health. Marketing preference cookies stay separate from cookies needed to keep your account session stable.
Payment mapping
JazzCash, Easypaisa, SadaPay, NayaPay, and Raast references are mapped to account ledgers. We store only what is needed to reconcile transfers and answer disputes.
Retention calendar
We keep records for account operation, legal duties, dispute handling, and fraud checks. When data is no longer needed, it is deleted, anonymised, or kept in restricted archives.
Policy audit
Privacy wording is checked when account forms, support scripts, cookies, or payment flows change. We record each change internally before the public page is refreshed.
Where This Policy Fits
This page should be read beside our terms, cookie wording, and contact rules, but it has one job: explaining privacy. If another page tells you how an account...
| Terms and privacy | Our terms describe account rules, while this Privacy Policy explains the personal data behind those rules. When an identity check is required, this page states the data purpose. |
|---|---|
| Cookies and privacy | Cookie wording covers browser storage in more detail, but this page explains why ct66 uses cookies for sessions, language settings, security checks, and account continuity. |
| Payments and privacy | Payment pages explain transaction steps, while this policy explains related data handling. JazzCash or Easypaisa references may be stored to match transfers and resolve disputes. |
| Support and privacy | Support pages explain contact paths, while this policy explains how chat logs, emails, screenshots, and verification files are stored, accessed, and linked to your account. |
| Security and privacy | Security wording explains account protection measures, while this policy explains related logs, device signals, location cues, and failed access records used to detect misuse. |
| Promotions and privacy | Promo pages explain campaign terms, while this policy explains preference data, eligibility checks, and message settings used when ct66 shows offers inside your account. |
| Legal requests | If a lawful request is received, this policy explains how ct66 assesses scope, records the request, and shares only data required under applicable local process. |
Privacy Signals You Can See
We place privacy cues where you actually interact with ct66, not only on this page. Account forms, verification prompts, cookie settings, support uploads, and transaction screens use short...