LEGAL REFERENCE

Privacy choices for your dzapk account

dzapk explains how your account data, device signals and transaction references are handled when you open access to our casino and sportsbook in Pakistan. Read this Privacy Policy...

Pakistan account dataJazzCash contextEasypaisa contextRaast references
Explore Lobby Read FAQ
dzapk Privacy choices for your dzapk account

How this policy applies locally

This Privacy Policy describes the data we collect, why we use it, how long we keep it and how you can contact us about it. When you access dzapk from supported regions where local law permits, we may process sign-in details, verification records, gameplay session logs, device data, support messages and payment references connected with JazzCash, Easypaisa, SadaPay, NayaPay or Raast. We

use those records to run your account, protect access, reconcile transaction status, respond to requests and meet legal duties that may apply to us. We do not write this policy to cover third-party pages you may leave dzapk to visit, and we expect you to check any separate privacy wording shown by those services.

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

CONTACT ROUTES

Where to send privacy requests

Use the routes below when your question is about data access, correction, deletion, retention or consent. We ask you to contact us...

Email privacy desk Send us privacy questions from the email linked...
Live chat handover If you start in chat, we collect only...
Account settings route When a data change is simple, such as...
DATA CHECKS

How we keep policy wording accurate

Our Privacy Policy is maintained alongside the systems that handle your account, support cases and transaction references. We check wording against actual dzapk flows, so the page stays...

Operational ownership

Our account, support and compliance staff feed policy changes back to the privacy owner when a real dzapk workflow changes...

Data map checks

We map account details, device records, payment references and support messages to the reasons we process them, then reflect those...

Access verification

Before discussing account data, we check control of the email, phone or account session, because privacy replies can expose sensitive...

Retention review cycle

We check retention periods against account activity, transaction reconciliation and legal needs, then remove or restrict records when there is...

Vendor checks

Where service providers process hosting, messaging, analytics or fraud signals for dzapk, we assess the role they play and limit...

Plain language edits

We edit privacy wording so you can understand what data is involved, why it matters, and which dzapk contact route...

How this policy fits our legal pages

This page works with our other legal pages, but it has a separate job. Terms explain account rules, cookie wording covers browser storage, and this Privacy Policy focuses...

Terms page link
Our terms may describe account conduct, but this policy explains the personal data we use when those terms are applied to your dzapk account.
Cookie page link
Cookie wording covers browser storage and similar tags, while this policy explains how those signals may connect with account security and session management.
Bonus page link
Promotional pages may show account offers, but this policy explains how eligibility checks, message preferences and related records are handled by dzapk.
Support page link
Support pages explain how to reach us, while this policy explains how we handle the messages, attachments and identity checks inside each request.
Security page link
Security wording may focus on account protection, while this policy explains the data signals used to spot unusual access and protect your records.
Payment page link
Transaction pages may describe available rails, while this policy explains how references from JazzCash, Easypaisa, SadaPay, NayaPay and Raast are processed.
Consent link
Where we ask for consent, this policy explains what the choice covers, how to change it, and what data use may continue.

Privacy page elements you can scan

We structure this Privacy Policy so you can find the privacy point that matters without reading unrelated copy. Each visible element is designed to separate data...

Data category labels

Section labels separate account data, device signals, transaction references and support messages, so you can see which part of dzapk processing is being discussed.

Reason statements

Each major data use is tied to a reason, such as account access, fraud checks, service messages, transaction reconciliation or a legal duty.

Retention cues

Where a record is not needed forever, we explain the factors that affect retention, including account status, dispute handling and legal record duties.

Choice markers

We mark where you may update preferences, request correction, ask about deletion or limit optional messages connected with your dzapk account.

Third-party clarity

When another provider helps us with hosting, communication, analytics or security checks, we explain that role without treating their service as dzapk.

Local context chips

Pakistan payment names appear only where privacy context needs them, such as receipt checks, reconciliation, account matching or support requests about transactions.

Privacy Policy questions answered clearly

We may collect account details, contact records, verification results, device signals, session logs, support messages and transaction references. The exact data depends on how you access dzapk and which account actions you take.

We use data to create and manage your account, protect access, process support requests, reconcile transaction status, send service messages and meet legal duties that apply where local law permits.

Yes, limited sharing may happen with providers that support hosting, messaging, analytics, security checks or transaction reconciliation. They receive only the data needed for their assigned task.

We may store transaction references, status updates and matching details connected with JazzCash, Easypaisa, SadaPay, NayaPay or Raast so support and reconciliation teams can trace account activity.

Yes. Contact us from the email or phone linked to your account, explain the correction needed, and we will verify control before changing records that identify you.

Retention depends on the record type, account status, transaction history, dispute needs and legal duties. When data is no longer needed, we remove it or restrict access.

Use the privacy contact route in this policy and include your account email, the data topic and the action you want considered. We verify identity before replying.