LEGAL REFERENCE

How we handle your account data

This privacy policy explains, in plain English, what we collect when you open an account, what we keep on file, and how long we hold it. It covers...

Account data, explained plainlyJazzCash and Easypaisa recordsCookie choices you controlDeletion requests welcome
Explore The Lobby Read FAQ
dazzle slots How we handle your account data

What this policy covers and when it applies

This policy is written for anyone using dazzle slots from Pakistan and other supported regions. It sets out how we gather account details, how transaction records from JazzCash, Easypaisa, SadaPay, NayaPay and Raast are stored, and how long each category stays on file. Where local law permits, some processing depends on the region you sign in from, because rules on retention, marketing

consent and account closure differ between markets. Use dazzle slots from outside Pakistan and the same principles apply unless a local requirement replaces them. We refresh this page whenever our practices change, and the version marker tells you which wording applies to your account. Continued use after a refresh means the revised terms cover you.

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

DATA SUPPORT DESK

Reaching us about your data

Privacy requests deserve a person, not a script. Our team answers in English and Urdu through live chat and email, confirms ownership...

Live chat Ask our privacy desk through live chat inside...
Email requests Send a data request from the email address...
Account settings Change your contact details, marketing consent and cookie...
BEHIND THE POLICY

The checks behind this policy

Trust on a data page comes from specifics, not slogans. A small internal team checks how account records move between our systems, our payment partners and our support tools. We document every...

Plain-language drafting

Each clause is written so one reading tells you what happens to your data, with no need to hunt for a definition buried three clauses further down the page.

Version tracking

We stamp every revision with a date and keep earlier wording available on request, so you can see what changed and when it started applying to your account.

Least-data practice

We collect only what an account and a transfer need: identity checks, transaction references, device signals. Fields that serve no operational purpose stay out of the form entirely.

Partner handling rules

JazzCash, Easypaisa, SadaPay, NayaPay and Raast partners receive only the detail needed to clear or reverse a transfer, and our agreements keep anything beyond that out.

Internal access rules

Staff open account records on a need-to-know basis, every access is logged, and routine checks catch permissions that no longer match someone's current role.

Independent escalation

If our reply leaves your question open, we name the authority that covers data matters in Pakistan and explain how to raise the issue with them directly.

How this page links to our other policies

This page works alongside the terms you accept when you open an account, the cookie notice that explains tracking, and the cashier rules covering JazzCash, Easypaisa, SadaPay and...

Terms of use
The terms cover your account, your conduct and the rules you accept at registration. This page covers data handling, so read the two together rather than in isolation.
Cookie notice
The cookie notice lists each tracker we run, what it does and how long it lasts. Optional analytics only start after you switch them on in settings.
Identity checks
Identity checks explain which documents we ask for, when we ask, and how long a verification copy sits alongside your account record once the retention window closes.
Cashier and transfer rules
Cashier wording covers transfer timing on JazzCash, Easypaisa, SadaPay, NayaPay and Raast, while this page covers what we record about each of those transfers afterwards.
Marketing consent
Consent rules govern promotional messages, how you withdraw your agreement and how quickly we act, and consent records sit in the same schedule this policy describes.
Complaints route
The complaints page sets out timelines for a formal response. Data requests under this policy follow the same escalation path if our first reply leaves you unsatisfied.
Retention schedule
Our retention schedule lists each record type and its holding period. This page explains the principle behind those windows while the schedule gives the figures.
HOW THE PAGE READS

The blocks that shape this policy page

This page is built to be read, not skimmed past. Every clause carries a one-line summary, a worked example and a plain statement of what we do, so...

Summary cards A short card at the head of every clause gives...
Section rail A side rail follows you down the page and lists...
Worked examples Examples show how a rule lands in practice, including what...
Version stamp One line near the header carries the revision date and...
Language choices The page reads in clear English written for Pakistan, and...
Request shortcuts Buttons for access, correction and deletion sit inside the page...

Privacy questions we answer often

We collect what an account needs: your name, contact details, date of birth, identity documents for checks, transaction references from JazzCash, Easypaisa, SadaPay and Raast, plus device and login signals.

Only where a task needs it. Payment partners see the transaction reference, identity checks pass to the provider running verification, and nobody else receives your record unless local law requires a disclosure.

Account records stay while you hold the account and for the retention window that follows closure in your region. Marketing consent records drop off sooner once you withdraw consent, and we tell you when a window ends.

Yes. Message us from your registered email or open a request from this page, and we confirm ownership before sending a copy of your record or correcting a field.

Traffic between your device and our servers is encrypted, sessions expire on inactivity, and staff access to account records is logged and limited to the people handling your request.

We use cookies for sign-in, language and fraud signals. Optional analytics and marketing cookies only run when you switch them on, and you can change that choice in account settings at any time.