LEGAL REFERENCE

Privacy Policy for your account

Live tables, slot rooms and sportsbook access on best casino use one account record, and this Privacy Policy tells you what we collect, why we keep it, and...

Pakistan account dataPayment record handlingSupport message privacySecurity checks explained

Explore lobby Read FAQ

How this policy applies

This Privacy Policy applies when you create, access or manage a best casino account from supported regions where local law permits. We collect only the details needed to run your account flow, check access, process payment records, answer support messages and protect the lobby from misuse. That can include your name, contact details, device data, account activity, payment references and documents you

choose to send for checks. We do not sell your personal data. We share limited data only with service partners that help us operate support, security, analytics, payment routing or verification. When law, payment rules or security needs require a record, we keep it for the period needed, then remove or anonymise it where suitable.

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

CONTACT ROUTES

Ask about your privacy

Privacy questions should reach the team that can trace your account record, not a public comment box. Use the same contact details linked to your account so we can match your request safely before replying.

Team online

Live chat privacy queue

Open chat while signed in and ask for privacy help. We check your session, confirm the account link, then route your request to the team handling access, correction or deletion questions.

Email request channel

Email us from the address on your account for a written privacy request. Include the account name and request type, but do not send card scans unless our team asks.

Payment record help

For JazzCash, Easypaisa, SadaPay or Raast privacy questions, share the reference code only. We use that code to find the record without asking for extra private details.

DATA CONTROLS

Policy checks we maintain

Our Privacy Policy is written from the account systems we operate, not from generic wording. We check it against product changes so new login, payment and support flows...

Account access records

We log sign-in events, device clues and session status to protect your account. The policy explains why those records exist...

Payment reference handling

Payment records show references, timestamps and routing status, not your full wallet life. Our policy separates JazzCash, Easypaisa, SadaPay and...

Support transcript care

When you contact support, we keep the conversation so the next agent can understand your request. Privacy wording explains retention...

Verification file limits

If verification is needed, we ask for the smallest set of documents suitable for the check. The policy states why...

Security partner sharing

Some fraud screening and hosting partners process limited data for us. We require them to use it for our service...

Policy update logs

When the Privacy Policy changes, we update the page date and adjust wording around affected data flows. Material changes are...

How related pages connect

This page sits beside our terms and cookie wording, but it has a narrower job. It explains personal data handling only, so you can separate privacy rights from...

Terms page link

The terms explain account conduct and service rules, while this Privacy Policy explains data collection, sharing and retention. If a topic concerns personal data, this page controls that explanation.

Cookie wording link

Cookie wording covers browser storage and preference tools. This Privacy Policy connects those signals to account analytics, security checks and any choices available inside your account area.

Payment terms link

Payment terms explain processing steps and timing. This Privacy Policy explains the personal data behind those steps, including references, wallet names, verification checks and support records.

Security page link

Security content describes protection controls in plain language. This page explains which data those controls create, who may see it internally and how long it may stay.

Promotions page link

Promotion pages may mention eligibility checks. This Privacy Policy explains how account activity is assessed for those checks without turning eligibility wording into a data handling rule.

Support page link

Support pages show where to contact us. This Privacy Policy explains what happens to your message, account identifiers, attachments and follow-up records after you contact us.

App access link

App access may use device identifiers, push preferences and session tokens. This Privacy Policy explains how those signals help keep your account connected and controlled.

Visible cues in this policy

Privacy pages can feel dense, so we keep clear signals across the layout. These markers help you see what is collected, what is shared, what stays...

Plain section names

Each heading names a real privacy task, such as collection, sharing or retention. We avoid vague legal phrasing where a direct explanation helps you understand your account data.

Local data examples

Pakistan payment examples appear only where they explain data records. JazzCash, Easypaisa, SadaPay and Raast references help you recognise what we may store after a transaction.

Short retention wording

Retention paragraphs explain why some records stay longer for legal, security or payment reasons. We separate active account data from archived records that support checks.

Clear sharing limits

Sharing language names the service purpose before naming partner types. That makes it easier to see when support, hosting, analytics, security or payment partners may process data.

Rights request path

The page points you towards account-linked contact routes for access, correction and deletion requests. We ask for identity checks before acting so another person cannot alter your record.

Update marker

Policy changes are marked through page edits and account messages where needed. The marker helps you spot privacy wording that changed after a product or support flow update.

Questions about this policy

We collect account details, contact data, login signals, device clues, payment references, support messages and verification files when needed. The exact set depends on how you use the account and which checks apply.

Payment references help us match JazzCash, Easypaisa, SadaPay and Raast activity to your account, answer support questions and check transaction status. We do not need your full wallet history for that purpose.

Yes. Contact us from the email or signed-in chat linked to your account and explain what needs correction. We may ask for a verification step before changing personal details.

Yes, where activity connects to your account record. The policy covers session data, table access records, security signals and support messages created while you use live casino features.

Only teams that need the messages for account help, safety checks, dispute handling or quality checks can access them. We limit internal access and keep records only as long as needed.

We update the Privacy Policy page when wording changes. If a change affects how important account data is collected or used, we may also show a message through your account area.

Send the request through signed-in chat or your account email. Some records may remain for legal, security or payment reasons, but we will explain what can be removed or anonymised.