Privacy Policy for your cd77 account
cd77 keeps account, device and payment data in one privacy framework, including records linked to JazzCash, Easypaisa, SadaPay and Raast. Read this policy before you open an account...
How this policy applies
This Privacy Policy explains how we collect, use, store, share and protect data when you access cd77 from Pakistan or supported regions where local law permits. The policy covers account creation, identity checks, login activity, game-session records, payment references, customer-care chats and security monitoring. We only ask for data that helps us run your account, process requests, meet legal duties, detect misuse
and keep our service stable. Some records are handled by payment, verification, hosting, analytics or support partners acting on our instructions. We do not sell your personal data. If a law, regulator, court order or payment partner requires a record, we may retain or disclose the exact data needed for that purpose.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
How we keep the policy current
Our privacy text is checked whenever account flows, payment rails, verification steps or support tooling change. We write the policy in plain en-PK wording, avoid legal padding where possible and connect each...
Flow-based drafting
We map the policy against real account screens, including registration, login, cashier records and support forms, so the words match what you see when sharing data with cd77.
Payment data scope
JazzCash, Easypaisa, SadaPay, NayaPay and Raast references are treated as financial records. We keep only the fields needed for reconciliation, verification, dispute handling and audit duties.
Security checks
Login device signals, IP patterns and failed access attempts help us detect account misuse. These records are handled with restricted access and are not used to profile unrelated behaviour.
Partner controls
When processors support hosting, verification, analytics or care systems, we limit their role by contract and instruction. They receive only the data needed for the service they provide.
Retention logic
We retain records for account operation, legal duties, dispute windows and security checks. When a record is no longer needed, we delete it or reduce it where systems allow.
Change tracking
Policy changes are logged with an update date and visible page wording. If a material change affects your account data, we may also notify you through account channels.
Consistency across legal pages
This Privacy Policy is written to work beside our Terms, cookie wording and account rules without conflict. When a page mentions personal data, we align its language with...
| Terms alignment | Our Terms describe account rules, while this policy explains data handling behind those rules. The two pages use matching labels for identity checks, security logs and account closure records. |
|---|---|
| Cookie wording | Cookie text deals with browser storage, analytics tags and session tools. This policy connects those signals to wider privacy purposes, including security, language preference and service stability. |
| Account notices | If an account screen asks for a phone number, name or payment reference, the purpose should reflect this policy. We aim to keep prompts short and accurate. |
| Cashier records | Cashier pages may show JazzCash, Easypaisa, SadaPay, NayaPay or Raast references. This policy explains why those transaction records may be stored and checked. |
| Support transcripts | Support pages collect chat text, timestamps and contact details needed to answer your request. This policy sets the privacy rules for storing and accessing those transcripts. |
| Security messages | Login alerts, password reset emails and verification prompts rely on account data. We align those messages with this policy so security handling remains clear. |
| Update wording | When legal pages change, we check cross-links, dates and data labels together. That keeps the privacy meaning consistent across the full cd77 account area. |
What you see on this page
We designed this privacy page so you can find practical data points without reading dense legal blocks first. The layout separates collection, use, sharing, retention and...
Clear section labels
Each privacy section uses a direct label, so you can move from account data to payment records or support history without guessing where a privacy answer might sit.
Short data badges
The badges near the hero flag the main record groups before the longer policy text. They help you spot whether account, device, payment or support data is involved.
Local record cues
Pakistan payment names appear only where they matter to privacy context. We use them to explain record types, not to turn a legal page into a cashier pitch.
Plain request routes
Contact options are written around what you need to ask for: access, correction, erasure or privacy clarification. Each route explains why we may verify you first.
Partner transparency
Where third parties process data for cd77, the page states their role in broad terms. We avoid naming extra partners unless their role must be clear.
Update visibility
Policy changes are handled with visible wording and date checks. If a change affects how your account data is handled, we can use account channels to reach you.