LEGAL REFERENCE

Privacy Policy for your jazz 2 account

jazz 2 keeps privacy terms close to your account flow: data use, payment records, support access and retention are set out before you open your account. Read this...

Account dataDevice logsPayment recordsSupport access

Explore Lobby Read FAQ

How we handle personal data

This Privacy Policy explains how jazz 2 collects, uses, stores and shares personal data when you access our casino, live casino, slots or sportsbook pages from supported regions in Pakistan, where local law permits. We collect only what is needed to run your account, secure access, process payment checks, answer support requests and maintain records required for service integrity. Data may include

your name, contact details, account activity, device signals, IP address, payment reference data and messages you send us. We do not sell your personal data. When a processor helps us with payments, fraud checks, hosting or support tools, we require that processor to handle your data only for the agreed service purpose.

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

PRIVACY HELP

Contact paths for privacy requests

If you want to ask about your personal data, use the contact route that matches your request. We may ask for account...

DATA CHECKS

How we keep this policy reliable

Our privacy wording is maintained by the same teams that handle account security, payment reconciliation and support escalation. That keeps the policy connected to real account handling instead of a detached legal...

Account-flow checks

We compare this policy against the actual account screens where you enter contact data, confirm identity or update access details, so the wording stays aligned with what you see.

Payment rail mapping

JazzCash, Easypaisa, SadaPay and Raast records are mapped to privacy purposes, retention needs and support access rules, rather than being treated as loose transaction files.

Support training

Support staff receive privacy handling steps for identity checks, account messages and payment references, so your request is escalated without asking for secrets we do not need.

Security logging

Device type, login time, IP patterns and session events help us detect account misuse. These logs are limited to security, troubleshooting and record integrity purposes.

Change control

When a data practice changes, we update this page and the connected account wording. Material privacy changes are reflected here before the related process is treated as standard.

Access limits

Only staff roles that need a record for support, payment checks or security handling can view it. Access is logged so internal handling remains accountable.

Consistency across our legal pages

Privacy does not sit alone. We align this page with account terms, cookie wording and security practices, so the same data purpose is not described in conflicting ways...

Account terms

The account terms explain service access, while this Privacy Policy explains the personal data used to support that access, including identity checks and account message handling.

Cookie wording

Cookie wording deals with browser storage and tracking signals. This policy connects those signals to security, preferences and analytics where they relate to your account.

Security practices

Security pages describe account protection steps. This policy explains the data behind those steps, such as login logs, device markers and suspicious access alerts.

Payment handling

Payment terms explain transaction processing. This policy explains which payment references we keep, who may access them and why retention is needed for reconciliation.

Support records

Support wording tells you how to reach us. This policy explains how chat transcripts, email threads and escalation records are stored and connected to your account.

Promo board records

If you check the promo board, account eligibility data may be used. This policy states how eligibility checks are handled without adding unrelated personal data.

Regional access

Access wording refers to supported regions and local permission. This policy explains how location signals may be used to manage availability and account security.

Privacy layout markers on this page

We design the Privacy Policy page so key data topics are easy to spot before you open an account. The layout separates collection, use, sharing, retention...

Clear data categories

Account details, payment references, device logs and support messages are named separately, so you can see which privacy topic applies to the question you are reading.

Purpose-led wording

Each data category is tied to a clear purpose, such as account access, payment confirmation, fraud checks, support response or service maintenance in supported regions.

Local context chips

References to JazzCash, Easypaisa, SadaPay, NayaPay and Raast appear only where payment data handling matters, keeping local privacy context visible without distraction.

Contact placement

Privacy contact options appear before deeper policy detail, because access, correction or removal requests should not be hidden behind dense legal wording.

Retention signals

Retention wording explains why some records are kept for account safety, reconciliation or dispute handling, while other records can be updated or removed sooner.

Plain language

We use direct Pakistani English and avoid legal clutter where a simpler sentence can explain the same privacy point without changing its meaning.

Questions about your privacy

We may collect your name, contact details, login records, device signals, account activity, support messages and payment references needed for account access, security checks and service records.

Payment references help us match JazzCash, Easypaisa, SadaPay, NayaPay or Raast activity to your account, confirm transaction status and resolve disputes without exposing wallet secrets.

No. We do not sell your personal data. Limited processors may handle data for hosting, payments, support tools or security checks under service-only instructions.

Yes. Contact us from your linked email or chat handoff and state what needs correction. We may verify your identity before changing records tied to payments or access.

Retention depends on the record type. Security logs, payment references and support messages may be kept while needed for account protection, reconciliation or dispute handling.

Only staff roles handling support, security or escalation can view relevant messages. Access is limited by role and used to answer your request or protect the account.