Cookie notice
Sets out which cookies keep you signed in and which measure lobby use, matching the cookie line in this policy, with browser steps for clearing or blocking them.
LEGAL REFERENCE
How lemon casino Handles Your Account Data
We keep one plain-language privacy policy so you always know what lemon casino stores when you open an account, fund it through JazzCash, Easypaisa, SadaPay or Raast, and...
What we storeWhy we store itHow to ask for a copySupport in Pakistani English
What lemon casino Collects and Why
Where local law permits, we collect only what an account needs to work: the name, date of birth, contact number and email you give at sign-up, plus the payment reference each time money moves through JazzCash, Easypaisa, SadaPay, NayaPay or Raast. We also log device type, browser, IP address and session times so we can spot a sign-in that does not look
like yours. Verification documents are checked once and stored securely. Play history stays with us to settle rounds and answer disputes. We do not sell this data. Sharing is limited to payment processors, identity-check partners and authorities acting on a lawful request. Retention follows the rules of your supported region.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
HOW WE HANDLE IT
Rules We Apply Behind the Scenes
This policy is written by the team that runs the platform, not lifted from a template. Every change starts as a written request, gets checked against Pakistani data practice and the rules...
Role-based access
Only staff who need a field can open it. Support sees payment status, the payments team sees the reference, and nobody outside those teams can pull a full profile.
Encrypted transfers
What you send us travels over an encrypted connection, and payout details sit encrypted at rest. When a partner needs data to clear a JazzCash or Raast transfer, we send the fewest fields.
Written change log
Each update is dated and summarised in plain English so you can compare what moved without reading the whole page again.
Identity checks
Before releasing a copy of your data or a payout, we match the request against your sign-in details and the document you verified at sign-up. Slightly slower, and deliberate.
Local data handling
Accounts held in Pakistan follow Pakistani data practice. We adjust only where the regulator of another supported region asks for something different, so one account always means one set of rules.
Single contact
One named privacy contact owns every request, so you are not passed between teams. That person replies, tracks the timeline and closes the loop when your change is done.
ONE RULE SET
The Same Rules Across Our Pages
This page sits alongside our terms of use, cookie notice, withdrawals page and account-security page, and the data rules read the same in all of them. Where a line here seems to...
Terms of use
Covers account rules, trading terms and the conduct expected in the lobby. Anything about personal data points back here rather than repeating the wording.
Withdrawals page
Explains payout steps, processing windows and the reference numbers you see on your account. The data side, including who sees those references, is handled on this page.
Account security page
Deals with passwords, sign-in alerts and device checks. The logging behind those alerts is described in the collection block above rather than repeated there.
Verification block
Covers document checks at sign-up and after a profile change, what is stored once a check clears, and what is destroyed afterwards.
Contact page
Lists the privacy desk email and chat hours directly, so the routes named on this page are the same ones you find there without hunting.
Language versions
The English wording here is the version we act on. Where a translation is offered for convenience, a conflict is settled by the text you are reading.
ON THIS PAGE
What You See on This Policy Page
This page is built to be scanned rather than swallowed whole. A short summary sits first, the full wording follows in dated blocks, and every heading lets you...
Dated changelog
A running list at the foot of the page shows...
Opening summary
The first block boils everything down to four lines: what...
Jump links
Every heading is tappable, so you land on cookie rules...
Supported rails strip
Small chips near the opening name the rails this policy...
Section owners
Each block ends with the team that owns it, whether...
Printable copy
The page prints cleanly to a single document if you...
Privacy Questions We Get Often
Your sign-up details, the reference for every JazzCash, Easypaisa, SadaPay, NayaPay or Raast movement, sign-in logs and your play history. That is what settles rounds and answers disputes.
Only with payment processors and identity-check partners that need a specific field to finish a request, or where an authority acts lawfully. Account data is never sold.
Yes. Write from the email on your account and ask for an export or a deletion. We verify the request first and explain anything we must keep for audit.
It depends on your supported region and on what the record is for. Play and payment history stays while your account is open, then is deleted once the audit window closes.
Cookies keep you signed in, remember your language and show which lobby areas get used. You can clear or block them in your browser, though sign-in may then misbehave.
Each edit carries a date near the opening and a line in the changelog. When a change affects how your data is used, we also email account holders.