Account terms
The account terms explain acceptable use, while this policy explains personal data handling. We keep both aligned so identity checks, security holds and account messages use the same data wording.
LEGAL REFERENCE
Privacy Terms For Your c42 Account
c42 keeps your account, live casino, sportsbook and payment data rules in one plain privacy policy, so you know what we collect before you open an account. Read...
Account data scopePakistan privacy contextJazzCash and Easypaisa chipsSupport contact path
How We Handle Your Data
This Privacy Policy explains how c42 collects, uses, stores and protects data linked to your account on c42.app. It covers details you give during account setup, login records, device signals, live casino activity, sportsbook activity, slot room history, support messages and payment checks connected with Pakistani rails. We use this data to run your account, verify transactions, secure access, handle support requests
and meet duties that apply where local law permits. Access to c42 may depend on supported regions, identity checks and payment availability. When you use JazzCash, Easypaisa, SadaPay or Raast, we receive transaction references and status updates rather than full wallet credentials. We keep data only for practical account, security and legal purposes, then remove or anonymise it when it is no
longer needed.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
CONTACT PATHS
Privacy Contact Paths For You
Privacy questions should reach people who can act on them. Use these c42 contact paths when you want access to your data, a correction, a deletion request, a security query or a clearer explanation of how a payment reference was handled.
Team online
Privacy email
Send privacy requests through the address shown in your c42 account area. Include your registered mobile or email, the request type and any transaction reference so we can locate the right record.
Live chat privacy tag
When chat is open, choose the privacy tag before sending sensitive details. Our team can confirm receipt, ask for safe verification and move deeper requests to the privacy queue.
Account area request
Inside your account, you can ask for profile corrections or data access. We may request proof that you control the account before releasing records or changing stored details.
POLICY CHECKS
How We Keep This Policy Current
We write this policy from c42 operational practice, not from a generic template. The checks below explain how we keep wording aligned with account flows, live tables, sportsbook records, slot history, support...
Plain wording check
We test the policy against real account screens so each clause matches something you can see or request. If a term feels unclear, we rewrite it before publishing changes.
Payment data mapping
JazzCash, Easypaisa, SadaPay and Raast references are mapped separately from wallet credentials. The policy states what c42 receives, what stays with the provider and why status logs are retained.
Security alignment
Login records, device signals and session data are checked against our security controls. This helps the policy explain why we collect access data without asking you to guess the purpose.
Support handling
Privacy support replies use a shared request tracker, so access, correction and deletion requests do not get mixed with general chat. Sensitive account changes require safe verification first.
Change logging
When we update wording, we keep an internal change record covering the clause, reason and affected account flow. You can ask support what changed if the policy date moves.
Local context
Pakistan payment names, supported regions and access wording are checked before each update. We avoid claiming availability where a rail, feature or account step is not active.
PAGE ALIGNMENT
One Privacy Standard Across c42 Pages
Your privacy expectations should not change when you move between pages. We align this policy with account terms, cookie controls, support forms, payment screens and promotional displays so the same data principle...
Cookie controls
Cookie choices affect browser data, analytics and session comfort. The privacy policy connects those choices with account records so you understand where site data ends and profile data begins.
Payment screens
Wallet and bank screens show JazzCash, Easypaisa, SadaPay and Raast status labels. This policy explains how c42 stores transaction references, timing records and verification outcomes tied to those screens.
Live casino pages
Live table logs may record session times, table names and account actions. The policy keeps that data tied to account security, dispute handling and transaction checks, not unrelated profiling.
Sportsbook pages
Sportsbook activity may create stake records, market references and settlement status. This policy explains retention for account balance accuracy, support queries and checks required in supported regions.
Slot rooms
Slot room history may show titles opened, round references and balance movement. We connect those records to account statements and support requests, with access limited to authorised teams.
Support forms
Support forms ask only for details needed to answer your request. Privacy requests are tagged separately so account data access, correction or deletion is handled with extra verification.
Clear Policy Layout For Quick Reading
This page is arranged so you can scan c42 privacy rules before opening an account. The visible blocks separate what we collect, why we collect it...
Plain policy summary
The first section gives the privacy scope without legal clutter. You can see account data, activity data, device data and payment references before reading the longer clauses below.
Local rail chips
Short chips mention JazzCash, Easypaisa, SadaPay and Raast only as privacy context. They show which payment references may appear in account records without exposing wallet credentials.
Contact cards
Separate contact cards show where to ask for access, correction, deletion or clarification. This keeps privacy requests away from casual chat and helps you send the right detail first time.
Policy signals
The policy check cards explain how we validate wording against real c42 screens. You can judge whether a clause relates to account setup, security, support or transaction status.
Page alignment
Comparison cards show how privacy wording connects with cookies, account terms and game pages. This avoids mixed messages when you move from policy reading into the lobby.
Question block
The final question block answers common privacy concerns in direct language. It focuses on data access, storage, deletion, payments and security before you decide to join c42.
Privacy Questions Before You Join
We collect account details you provide, login records, device signals, gameplay references, support messages and payment status data. We use them to run your account, secure access and handle requests.
No. c42 records transaction references, amount status and timing details needed for account balance checks. Your wallet credentials stay with JazzCash, Easypaisa, SadaPay or the banking rail involved.
Live casino records help us confirm table sessions, balance movement and support queries. They may include table names, session times and account actions, but access is limited to authorised teams.
Yes. Contact us through the account area, email path or privacy-tagged chat. We may verify control of the account before changing profile details or releasing stored account records.
We keep data for account operation, security checks, support handling and legal duties in supported regions. When data is no longer needed, we remove it or anonymise it where practical.
We share only what is needed with payment processors, security tools, hosting services and support systems that help operate c42. We do not sell your personal data to advertisers.
Use the privacy email, account request option or chat privacy tag. Tell us what you want checked, add your account identifier and avoid sending unnecessary sensitive documents unless we ask.