Cookie Page
Cookie wording explains browser storage, while this Privacy Policy explains account data. The two pages use the same consent language so your browser choice and account choice do not conflict.
LEGAL REFERENCE
Privacy Policy for Your Account
Our Privacy Policy gives you a clear account-data path: what we collect, why we collect it, and how you can ask us to correct or remove it. Before...
Pakistan privacy scopeAccount access logsJazzCash record contextData rights channel
How Our Privacy Policy Applies
This policy applies to the personal data you give us when you create an account, verify identity, contact support or use local rails where local law permits. We record account identifiers, device security signals, session activity and payment references needed to keep your profile accurate and to respond to privacy requests. JazzCash, Easypaisa, SadaPay and Raast entries are stored as reference records,
not as public lobby content. We share data only with service providers that help run security, verification and support, under handling rules that match this policy. In supported regions, you can ask for access, correction or deletion subject to fraud controls, unresolved disputes and records we must keep for legal reasons. We keep the request path clear before any account decision.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
POLICY CHECKS
How We Keep Policy Clear
We write this Privacy Policy from the way our account systems actually work. The wording is checked against login records, verification screens, support scripts and local transaction references before it appears here...
Plain English Drafting
We avoid dense legal wording where a direct sentence works. Each policy point explains the data involved, the reason we use it, and the channel you can use for a privacy request.
Pakistan Context
Our policy names local account signals such as Pakistan mobile numbers and transaction references from JazzCash, Easypaisa, SadaPay and Raast. That keeps privacy wording tied to your actual account flow.
Access Logging
Staff access to account records is logged so privacy cases can be checked later. We limit internal viewing to support, security or verification tasks linked to a clear business need.
Retention Calendar
We keep different records for different periods based on security, tax, dispute and support needs. The policy separates routine profile data from records we must hold for legal reasons.
Vendor Mapping
Where outside service providers handle hosting, security checks or messaging, we map the data they receive. The policy explains those categories without naming every system screen you cannot see.
Change Record
When the Privacy Policy changes, we keep an internal record of what moved and why. Material changes are shown on the page so you can decide whether to continue using the account.
PAGE ALIGNMENT
Consistency Across Policy Pages
Your privacy choices should not change meaning between our legal pages. This section explains how the Privacy Policy fits beside cookie wording, account terms, security screens and support contact routes. When another...
Account Terms
Account terms describe what you agree to when joining. This Privacy Policy explains the personal data used to apply those terms, including verification records and support history tied to your profile.
Security Page
Security wording focuses on passwords, device checks and unusual access. This policy explains the data behind those checks, including IP signals, device type and login timestamps connected to your account.
Promo Board
If a promo board uses eligibility rules, this Privacy Policy explains the account data that may support those rules. We separate promotional display from private verification and transaction records.
Contact Page
The contact page shows how to reach us, while this policy explains how messages are stored. Privacy requests get handled as account-data cases rather than ordinary service conversations.
Verification Screen
Verification screens ask for documents or mobile confirmation when needed. This policy explains why those records are collected, who can view them, and when they may be deleted.
Sportsbook Rules
Sportsbook rules cover market settlement, while this Privacy Policy covers the data trail linked to account activity. Settlement records may be retained when needed for disputes or legal duties.
Privacy Page Signals You See
We designed this legal page so privacy points are easy to scan before you open your account. The layout uses short labels, local context chips and...
Scope Bar
The scope bar tells you which account areas the Privacy Policy covers before you read deeper. It points to registration, identity checks, support messages, security logs and transaction references.
Data Table
Short data rows separate contact details, device signals, verification records and support messages. This helps you see why each category exists and which request route applies to it.
Consent Strip
Where consent is relevant, the strip explains what choice you are making and how it affects account use. It avoids vague wording and links the choice to a clear privacy purpose.
Access Panel
The access panel shows how to ask for a copy, correction or deletion of personal data. It also explains checks we may require before releasing records connected to your account.
Local Rail Labels
JazzCash, Easypaisa, SadaPay and Raast labels appear only where transaction references are discussed. They help you understand record context without suggesting that financial data is public.
Update Stamp
The update stamp shows when this Privacy Policy last changed. If wording changes in a material way, the stamp helps you decide whether to read the new sections again.
Privacy Policy Questions Answered
It covers account details, mobile number, login records, device signals, verification documents, support messages and transaction references. We use these records to manage your account, secure access and answer privacy requests.
Device and login data helps us spot unusual access, confirm account ownership and investigate support cases. We use it for security and account integrity, not for public display in the lobby.
We may receive or store transaction references connected to JazzCash or Easypaisa activity. Financial rails process their side separately; our policy covers the account records we hold after the transaction event.
Yes, you can ask us to correct inaccurate profile details or account records. We may verify identity first, especially where a change affects mobile access, transaction history or security settings.
You can request deletion where local law permits. Some records may be retained for fraud checks, disputes, accounting or legal duties, and we will explain any record we cannot remove yet.
We show an update stamp on the Privacy Policy page when wording changes. If a change affects how we collect, share or store account data, we make the new wording visible here.