Your privacy policy, written for Pakistan accounts
This page sets out how jacks casino collects, uses and stores the data behind your account, including every JazzCash, Easypaisa, SadaPay and Raast transfer you make with us.
How we treat your data where local law permits
We run this policy from Pakistan and write it to match the rules that apply where you live, so the wording stays jurisdiction-dependent. Where local law permits, we collect only what an account needs: your name, contact number, date of birth, device signals and the trail created when money moves through JazzCash, Easypaisa, SadaPay, NayaPay or Raast. We log sign-in activity so
we can spot a session that does not look like yours. We share records with payment partners and fraud-screening providers only when a transfer or a dispute needs it, and we do not sell your contact list. Retention follows a schedule tied to account status, so closing your account starts a wind-down clock rather than an instant delete. Where a supported region
sets a stricter rule than ours, that rule governs.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Six ways we keep your records accountable
We keep a short audit trail for every privacy change we ship, and the person who drafts the wording is not always the person who signs it off. Two teams check the...
Named data lead
One accountable person signs off on this policy and any later edits. If you question a clause, we say plainly who wrote it and why it still exists.
Change log with dates
Every amendment to this page shows a revision date under the headline. We keep earlier versions so you can see what changed instead of guessing what moved overnight.
Plain-language drafting
We draft clauses in short sentences and skip legal padding. When a technical term is unavoidable, we define it in the same paragraph rather than link you away.
Local transfer trails
Transfers through JazzCash, Easypaisa, SadaPay and Raast leave a reference on your account. We store that reference only to settle disputes, not to profile how you spend elsewhere.
Device history
Your account shows which devices signed in, from where, and at what hour. If a session looks unfamiliar, end it and reset your credentials without waiting on us.
Escalation path
If our reply does not settle your question, the matter moves to a senior handler who answers in writing. You keep the same reference through every step of that exchange.
One voice across every policy page
The wording here mirrors the terms on our other policy pages, so a clause about your account does not contradict a clause about cookies. Where two pages overlap...
What you see inside this privacy page
This page is built as a single reading column with a sticky index on the left, so you can jump to retention, sharing or account rights...
Reading index
A fixed sidebar lists every clause on this page. Tap a heading and the column scrolls straight to it, which keeps long sections manageable on a small phone.
Revision stamp
A date sits under the headline and changes whenever a clause does. You can tell whether the version in front of you is older than the one you saved.
Data-use blocks
Each practice, such as verifying a payout to your Raast account, sits in its own block with the reason beside it. You never have to hunt through prose.
Chip row context
Payment names appear as simple chips near the headline so you can confirm which rails this policy covers. JazzCash, Easypaisa, SadaPay, NayaPay and Raast are listed in plain text.
Account controls
Buttons for downloading your records, correcting a detail or closing the account sit in one panel, so your choices are a click away rather than buried in a form.
Print-friendly layout
This policy exports to one clean sheet if you want a copy for your files. Headings, dates and chip rows travel with it, so the print matches this page.