LEGAL REFERENCE

Privacy Policy for Your ds3 Account

ds3 puts live casino tables, slots and sportsbook access behind an account flow that depends on clear privacy handling. Before you open your account, this policy explains what...

Account privacyPakistan contextDevice dataSupport requests
Explore the Lobby Read FAQ
ds3 Privacy Policy for Your ds3 Account

How We Handle Your Data

This Privacy Policy describes how ds3 handles details connected to your account, device, location signals, identity checks, payment references and support chats in supported regions of Pakistan, where local law permits. We collect only what we need to run your account, protect access, process withdrawals, respond to your questions and keep records required for operational checks. When you use JazzCash, Easypaisa, SadaPay

or Raast, we receive transaction references rather than your full banking credentials. We do not sell your personal records. We share data only with service partners who help us verify accounts, secure sessions, process payments, maintain the lobby and answer privacy requests under controlled access rules.

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

CONTACT ROUTES

Contact Paths for Privacy Requests

If you want to ask about your privacy records, start with the support route linked inside your ds3 account. We use account-based contact first because it helps us match the request to the right profile without exposing details in open messages.

Team online

Account support

Send privacy questions from the support panel after signing in. We can then check your account reference, confirm the request type and reply without asking for sensitive details in public channels.

Email privacy desk

For a longer request, email our privacy contact with your account nickname, registered mobile ending and request purpose. Please do not include passwords, card details or full wallet credentials.

Live chat handoff

Live chat can capture the first privacy question, then move the matter to the correct team. We may ask you to confirm account ownership before discussing stored records.

POLICY CHECKS

How We Keep This Policy Current

Our privacy wording is checked against how ds3 actually operates: account entry, wallet references, live table sessions, withdrawal checks and support handling. When a workflow changes, we update...

Version record

We maintain dated policy versions so changes can be traced internally. This helps our team answer your questions about which...

Plain wording

We write privacy sections in direct Pakistani English rather than legal shorthand alone. The goal is that you can understand...

Regional fit

Policy wording reflects Pakistan access, supported regions and local payment labels. When we mention JazzCash, Easypaisa, SadaPay or Raast, we...

Security alignment

Privacy checks sit beside account-security rules, session monitoring and withdrawal verification. That keeps your personal records, device signals and transaction...

Partner checks

Service partners receive only the records needed for their task, such as payment processing or account verification. We restrict reuse...

Change alerts

When a material privacy change affects your account, we aim to flag it through account messages or site updates. You...

Consistent Wording Across ds3 Legal Pages

The Privacy Policy is written to work with our other legal pages without repeating them. Account terms explain access rules, while this page focuses on personal records, payment...

Account terms
Where account terms explain login conduct and access rules, this Privacy Policy explains which personal records support those checks and how we manage them inside ds3 systems.
Cookie page
Cookie wording covers browser storage and tracking choices. This policy connects those tools to broader account privacy, including device signals, session security and preference handling.
Payment wording
Payment pages explain available rails, while this policy explains how transaction references are recorded. We separate wallet instructions from privacy handling so each page stays focused.
Security wording
Security content explains access controls and verification steps. This policy adds the privacy angle, including why we may check account ownership before disclosing stored records.
Support wording
Support pages describe how to reach us. This policy explains how chat transcripts, email requests and account tickets may be stored while your privacy matter is handled.
Promo wording
Promotion pages may refer to account eligibility. This policy explains the data used for eligibility checks without turning privacy wording into an offer or campaign page.
Regional wording
Market wording explains access in supported regions, where local law permits. This policy states how location signals may help us apply those regional access rules.

Policy Layout You Can Read Fast

We designed this privacy page so you can scan the parts that matter before opening an account. The structure separates data categories, reasons for use, sharing...

Scope block

The opening scope block states which records the policy covers, including account details, device signals, identity checks, payment references and support messages tied to your ds3 profile.

Use reasons

Each data category is connected to a reason, such as login security, wallet reconciliation, withdrawal checks or support handling. This helps you see why a record exists.

Sharing rules

Partner sharing is described by task, not vague labels. We state when processors may help with verification, payments, hosting, support tools or security monitoring for your account.

Retention cues

Retention wording explains why some records must remain for operational, security or legal purposes. We also point you toward contact routes for account-specific privacy requests.

Request links

Visible contact routes help you ask for access, correction or deletion where applicable. We may verify ownership first so private account records are not disclosed improperly.

Pakistan context

Local labels appear where they matter, including JazzCash, Easypaisa, SadaPay and Raast transaction references. The policy avoids copying wallet instructions into privacy sections.

Privacy Questions Before You Join

We collect account details, contact data, device signals, session records, payment references and support messages needed to run your account, protect access, process withdrawals and respond to privacy requests.

No. For JazzCash, Easypaisa, SadaPay and Raast, we handle transaction references and reconciliation details. Your full wallet login credentials stay with the payment provider, not inside ds3.

We use device and location signals to secure sessions, detect unusual access and apply supported-region rules where local law permits. These signals help protect your account and support fair access handling.

Yes. Contact us through account support or the privacy email route with the record you believe is wrong. We may verify account ownership before making changes or sharing details.

Selected service partners may receive limited records for tasks such as verification, payments, hosting, security monitoring or support tools. We do not sell your personal records to outside advertisers.

Retention depends on the record type and the reason it was collected. Some data is kept for security, payment reconciliation, dispute handling or legal duties before deletion or restriction.