LEGAL REFERENCE

What We Do With Your Data

This page sets out what new casino gathers when you open an account from Pakistan, why we hold it, and how to have it corrected or removed. Read...

Account data onlyNo resale of recordsWallet references heldDeletion on requesten-PK wording
Explore The Lobby Read FAQ
new casino What We Do With Your Data

Where This Policy Applies

Where local law permits, new casino processes the details you hand over at registration and the transaction trail your chosen rail leaves behind. Pakistan is our home market, so JazzCash, Easypaisa, SadaPay and Raast appear constantly in those records, yet the protection you receive follows the rule of the place you are sitting in when you use the account. We split what

we must hold from what we choose to hold. Your name and wallet reference stay with us because a payout rail or a regulator needs a match. Session and device records stay because they let us flag a strange login before it damages you. When your province or country lays down stronger requirements than this page sets out, the stronger requirement governs

your account.

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

REACHING US

Ask Us About Your Records

You can raise any privacy question or deletion request through the same channels that handle your account. We reply to wallet-linked data...

Live chat Open live chat from any page and an...
Email request Send a written deletion or correction request to...
Account controls Your profile area lets you rewrite contact details...
WHO WRITES THIS

The People Behind These Words

This policy is written and maintained by the new casino operations team in plain English, then passed to our data handler for a second read before anything changes. Every clause names the...

Account ownership

Your account belongs to you. We hold a copy so the platform can run, but we never treat your wallet reference or past sessions as something to trade away.

Retention windows

We publish how long each record type stays with us. Identity papers clear once the period a payment rail needs has passed, and play logs clear sooner.

Access limits

Only staff holding a named role can open a customer file, and every open is written to a log we read weekly. Everyone else sees numbers with no names.

Transport security

Pages run over an encrypted connection, so details typed on a Pakistani mobile network stay unreadable in transit. Passwords are hashed, never stored, and odd sessions trigger a fresh login.

Wallet data

When you move money with JazzCash, Easypaisa, SadaPay or Raast, we see a reference number, an amount and a status. We never see your wallet PIN.

Plain wording

We write these pages for readers, not lawyers. Where a legal phrase is unavoidable we explain it in the next sentence, so you never guess what a clause means for you.

Keeping Our Policies Consistent

The wording here is matched against our account rules, withdrawal terms and cookie notice, so the same promise cannot mean two different things in two places. When one...

Account rules
Registration requirements on our account rules page mirror the consent wording here, so a data use you agreed to at registration appears in both places without contradiction.
Withdrawal terms
The identity records mentioned here are the same ones the withdrawal page asks you to verify. Neither page expects a document the other one does not already hold.
Cookie notice
Our cookie notice explains the small files that remember your language and login state. Anything described there as optional also appears here as optional, so switching it off never breaks access.
Payment terms
Wallet handling on our payment terms page matches the reference-number point made here. Both pages agree on what we can and cannot see from JazzCash, Easypaisa, SadaPay or Raast.
Verification page
Identity steps on our verification page draw only on the data categories described here. We do not widen the request on one page and narrow it on another.
Complaints path
When a query reaches us as a complaint, the response time and escalation route stay the same whichever page pointed you there, and your ticket follows the case to the end.
Language versions
Every clause is held in English for our Pakistani readers. If a translation is ever added, the English text stays the version we stand behind.
PAGE HIGHLIGHTS

What You Will Find Laid Out

Everything a privacy page needs sits in the open here: the categories we store, the wallets involved, the people you can reach, and the clauses that carry across...

Plain summary The opening block gives you the short version before any...
Wallet chip row A row of Pakistani payment names shows which rails generate...
Jump links Each block carries a short label so you can skip...
Contact card Our support routes sit inside the policy rather than on...
Version marker A marker at the head of the page changes whenever...
Plain examples Where a clause could read two ways we add a...

Privacy Questions We Hear Often

Your name, contact details, date of birth and the wallet reference from your first transfer. We also keep session records showing when and where you logged in, which helps us spot access that is not yours.

No. We do not trade, rent or sell account data to advertisers. The only parties who see your records are the payment rails that move your money and the providers who keep our servers running, each under a written limit.

Yes, from your profile area or by writing to support. We clear contact details, session logs and marketing preferences straight away. Records a payment rail requires us to retain stay for their fixed period, and we tell you which ones.

Never. When you move money through JazzCash, Easypaisa, SadaPay or Raast, the rail confirms the transfer and we receive a reference, an amount and a status. Your PIN stays inside the wallet you installed.

That depends on what the rail or a regulator asks us to keep. Identity checks clear after the retention period attached to them, and play history clears earlier. We publish the windows so you are not left guessing.

Only named roles with a work reason, and every file open lands in a log our team reads each week. Staff outside those roles work with numbers that carry no names attached.