LEGAL REFERENCE

How 22bets handles your data

22bets puts live casino, slots and sportsbook access behind an account flow that also explains what data we collect, why we need it and how we protect it...

Pakistan privacy wordingAccount data useTransaction record careSecurity checks
22bets How 22bets handles your data

Privacy posture for Pakistan accounts

Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.

PRIVACY HELP

Where to ask privacy questions

Privacy requests should reach the team through channels that can confirm you are speaking about your own account. We may ask you to verify a phone number, email or recent transaction reference before we discuss stored records. This helps prevent another person from asking about your profile.

Team online

Privacy inbox

Email [email protected] when you want to ask how account data is stored, corrected or removed. Include your account email or phone so we can match the request safely.

Chat handoff

Start with live chat if you are already logged in and need a privacy ticket raised. Chat staff collect the request, then pass sensitive data questions to the privacy queue.

Payment record query

For JazzCash, Easypaisa, SadaPay or Raast record questions, send the transaction reference and date. We only compare records needed to locate the account event.

DATA CHECKS

How we keep the policy accurate

Our Privacy Policy is maintained by the teams that operate account access, payments, verification and support. When a process changes, the wording is checked against what you actually...

Operations signoff

Account, support and payments staff check policy changes before publication, so the wording reflects actual handling of login records, identity...

Local wording

We write for Pakistan in clear English, using JazzCash, Easypaisa, SadaPay and Raast examples only where they explain how transaction...

Access controls

Internal tools limit who can open personal records. Staff access is tied to work duties, and sensitive views are logged...

Verification practice

Before changing account details or discussing stored records, we check ownership through login status, phone, email or a transaction reference...

Retention checks

We keep records for business, security and legal reasons, then reduce or remove data when it is no longer needed...

Change tracking

Policy edits are dated internally and compared with current account flows, so privacy wording stays aligned with the way 22bets...

Consistency across our legal pages

This page should be read with the rest of our legal wording, but it has its own role. The Privacy Policy explains personal data handling. Other pages may...

Terms wordingOur Terms describe account conduct, while this Privacy Policy explains the data behind account checks, login security, transaction history and support contact handling.
Cookie pageCookie wording covers browser storage and similar tools. This page connects those signals to account security, session handling, preference storage and fraud prevention.
Promotion rulesIf a promotion needs account checks, the privacy wording here explains why related records may be used and how access to them is limited.
Verification wordingIdentity checks may appear in separate account rules, but this page explains what verification files may contain and why they are retained.
Payment recordsTransaction pages show amounts and status. This Privacy Policy explains how JazzCash, Easypaisa, SadaPay and Raast references become account records.
Support recordsSupport pages explain contact choices. This page states how messages, screenshots and ticket history are stored when they contain personal data.
Security wordingSecurity text may mention login protection. This policy adds how device signals, IP region and session records help protect your account.
PAGE MARKERS

Privacy layout built for clarity

We structure this Privacy Policy so you can scan the parts that matter before you create or use an account. Each marker points to a visible privacy element...

Collection summary The policy separates account details, device signals, transaction references and...
Purpose labels Each major use is tied to a purpose such as...
Sharing section We name the kinds of partners that may handle data...
Retention marker Retention wording explains why some records stay longer than others...
Rights pathway The contact section tells you how to ask for access...
Update signal When privacy wording changes, we keep the page aligned with...

Common questions about privacy

We collect account details, login records, device signals, IP region, transaction references, support messages and verification files when needed. The exact data depends on how you use the account.

JazzCash, Easypaisa, SadaPay and Raast references help us match transactions to your account, resolve status questions and check withdrawal requests. We use only the records needed for that task.

No. We do not sell your personal data. Limited sharing may happen with processors, security tools, verification services or support systems when they help us operate the account service.

Contact [email protected] from your account email or include your registered phone. We may ask for verification before changing details so another person cannot alter your profile.

Retention depends on the record type and reason for storage. Transaction history, security logs and verification files may stay while needed for legal, security or account purposes.

Yes, we may collect device type, browser data, session activity and IP region. These signals help protect access, detect misuse and apply availability rules for supported regions.

We update this page when data practices change. If a change affects your account privacy in a meaningful way, we aim to make the wording clear before you continue.