LEGAL REFERENCE

Privacy Policy for Your Account

Live roulette, slot rooms and sportsbook markets all rely on the same account record, so our Privacy Policy explains what we collect before you open an account. We...

Pakistan account dataJazzCash privacy contextEasypaisa handlingSadaPay and Raast checks

Explore the lobby Read FAQ

How We Handle Your Data

Our Privacy Policy covers the data you share when you create an account, verify access, use casino or sportsbook pages, contact support, or request a payout. We collect only the details needed to run your account flow, meet verification duties, protect balances, process payments and answer privacy requests. In Pakistan, payment context may include JazzCash, Easypaisa, SadaPay or Raast references, but we

do not publish your account activity or sell your identity details. Access is intended for supported regions where local law permits. We keep privacy wording plain so you can see why a field is asked for, how long records may be held, and how to reach us when something needs correction.

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

PRIVACY HELP

Reach Us About Privacy

Privacy questions should not get lost in general account chat. We route requests about access, correction, deletion, payment records and device sessions...

POLICY CHECKS

How We Keep The Policy Current

We write this Privacy Policy from the operator side, using the account screens, payment checks and security prompts you actually see. Each update is checked against our sign-in flow, KYC steps, payout...

Account-flow testing

We compare the policy against the fields shown during account opening, sign-in recovery and verification, so the wording matches what you are asked to provide on screen.

Payment data mapping

JazzCash, Easypaisa, SadaPay and Raast references are mapped to purpose, retention and support access, helping us keep payment privacy separate from lobby browsing data.

Security session checks

Device, IP and session signals are used to protect account access and investigate unusual activity, and the policy explains that role without hiding it behind vague wording.

Support script alignment

Our support replies are checked against the Privacy Policy so staff do not ask for documents, screenshots or transaction details that are not needed for the request.

Retention purpose checks

We link record retention to clear purposes such as verification, payment disputes, security logs and legal duties, then remove or restrict data when those purposes no longer apply.

Plain English editing

We avoid dense legal phrasing where a direct sentence works, because you should understand what happens to your name, phone number, payment reference and account activity.

How Our Privacy Pages Stay Consistent

This Privacy Policy sits beside our account terms, cookie notice and support rules. Each page has a different job, but the privacy meaning must stay consistent across them...

Account terms link

The account terms explain account use, while this Privacy Policy explains the data behind that use, including identity fields, session records and support contact history.

Cookie notice link

The cookie notice deals with browser storage and measurement tags, while this policy explains how those signals may connect to fraud checks and account security.

KYC wording link

Verification screens may ask for identity or address details; this Privacy Policy explains the purpose, storage approach and access controls for those records.

Payment rule link

Payment pages describe JazzCash, Easypaisa, SadaPay and Raast flows; this policy explains how related references are stored, checked and shared with support staff.

Support rule link

Support rules tell you how to contact us, while this policy explains how ticket content, chat transcripts and account identifiers are handled internally.

Security notice link

Security prompts may mention device checks or sign-in alerts; this policy explains the privacy side of those logs and why they protect account access.

Update wording link

When privacy wording changes, linked pages are checked so account terms, cookie text and support scripts remain aligned with the current policy.

Privacy Page Layout Signals

The Privacy Policy page is built for quick scanning without turning legal text into a maze. We use visible markers for scope, contact routes, data categories...

Scope marker

The opening section states that the policy applies to account creation, casino and sportsbook use, payment references, support contact and security checks across supported Pakistan regions.

Data category labels

We separate profile details, payment references, device signals, chat records and verification documents so you can understand each category without reading one long legal block.

Purpose blocks

Each data category is linked to a practical purpose, such as account access, payout verification, fraud prevention, support handling or compliance with applicable record duties.

Contact panel

The contact section stays visible in the page flow so you can ask for access, correction or deletion without searching through unrelated casino or sportsbook content.

Retention cues

Where records must be kept, we explain the reason in plain language, including security logs, transaction references, verification records and support ticket history.

Update stamp

Policy updates are marked clearly so you can see when privacy wording changed and decide whether to read the revised account and data handling sections.

Privacy Policy Questions Answered

We may collect your name, phone number, email, account credentials, verification details, payment references, device signals, session records and support messages when needed for account access, security, payments or service handling.

JazzCash, Easypaisa, SadaPay and Raast references help us confirm funding and payout activity, trace support queries and resolve disputes. We use those references for account purposes, not public display.

Yes. Contact us through the privacy route with the account email or phone number and the detail that needs correction. We may verify ownership before changing personal or payment-linked records.

We use device, IP and session signals to protect sign-in access, detect unusual account activity and keep security logs. The policy explains these checks because they affect your privacy.

Yes. Live casino activity may create account records such as session time, table participation, balance movement and support contact. The policy explains how those records fit within account data handling.

Retention depends on the record type and purpose. Verification, payment, security and support records may be kept while required for account protection, dispute handling or applicable legal duties.

Only staff who need the details to handle your request should access it. We limit internal sharing to account identification, verification, payment tracing or support response purposes.