LEGAL REFERENCE

Your Data, Explained In Plain Terms

One page covers everything we hold on you — the details you give at sign-up, the session records your device sends, and the payment references that pass through...

Account data onlyLocal rails coveredRemoval on requestWritten in plain English
Explore lobby Read FAQ
new slot Your Data, Explained In Plain Terms

How Local Law Shapes What Applies

We keep a single privacy policy for everyone, then adjust the mechanics where local law permits. In Pakistan that means your account records for JazzCash, Easypaisa, SadaPay and Raast sit with our payments team and are matched against identity checks before any payout leaves. If you play from another supported region, the same records may be held on servers there under that

region's retention rules. Retention differs by record type as well: payment trails stay longer than session logs because tax and audit requirements ask for it. Where a mandatory local rule conflicts with a clause on this page, the local rule takes priority for your account, and you can write to us for written confirmation of which version applies to you.

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

REACHING OUR TEAM

Where To Send Your Data Questions

Ask us anything about this policy and a person answers, not a script. Our privacy desk runs seven days a week from...

Privacy Email Write to our privacy desk from the email...
Live Chat Use the chat bubble inside your account area...
Account Settings Open the settings tab to download a copy...
WRITING STANDARDS

Who Writes And Checks This Page

This policy is drafted by the team that runs your account and checked by our compliance lead before any edit goes live. Each change carries a date and a short reason, so...

Named Owner

The policy sits with a named data owner inside our operations team, so questions about a clause go to a person who can actually change the wording.

Dated Edits

Changes are logged with the day they take effect, and older versions stay readable, so you can compare what applied when your account was opened and see exactly what shifted.

Compliance Sign-Off

Our compliance lead signs off every rewrite before it goes live, checking that the wording matches what our systems actually do rather than what sounds tidy on paper.

Local Payment Detail

Because JazzCash, Easypaisa, SadaPay and Raast records sit at the centre of account security, this page spells out how those references are stored and shared with third parties.

Plain Language Rule

Every clause is rewritten until it reads clearly without a legal dictionary, and we keep a short version near the start for anyone who wants the summary first.

No Third-Party Sales

We do not sell account records or hand your contact details to advertisers, and any partner that touches our systems is bound by a written agreement we can show you.

How This Policy Lines Up With Our Others

Every legal page on new slot shares one structure, so you can move between them without relearning the layout. This policy covers account records; the pages beside it...

Terms of Use
Sits beside this policy and sets out how you may use your account, while every question about stored records is answered here instead, by the same privacy desk.
Cookie Notice
Explains the small files that keep you signed in and remember your language choice, then links back to this page for anything about wider account records and payment trails.
Sportsbook Rules
Covers market settlement and bet acceptance only, while the identity and payment records sitting behind those bets are described on this privacy page and nowhere else.
Payout Conditions
Handles withdrawal timing and verification steps, then points across to this policy for how long the matching identity and payment records stay on file after a payout clears.
Account Security
Describes logins, device checks and password resets, with a direct link to the clause here that explains which login history we store and for how long.
Complaints Route
Sets out how to raise a dispute and the timeline we work to, and links to this page whenever the issue turns on how your data was handled.
Change Log
Lists every edit across our legal pages in date order, so you can see when this privacy policy changed and jump straight to the clause that moved.
ON THIS PAGE

What Sits On This Policy Page

Scroll and the layout stays the same each time we update, so you always know where to look. Summary badges sit near the head of the page, the...

Summary Strip Four short badges sit above the first paragraph and name...
Jurisdiction Block One paragraph explains which rules apply to your account, including...
Scope Chips A short chip row names the local rails inside the...
Contact Cards Three cards spell out where to send a request, what...
Clause Anchors Each heading links straight to its own clause, which means...
Version Footer The closing line carries the version number and the day...

Straight Answers On Your Account Data

We store your name, date of birth, contact details and the payment reference from your first funding, whether that came through JazzCash, Easypaisa, SadaPay, NayaPay or Raast. Nothing beyond what we need to run and secure the account.

Yes. Open your account settings and request a copy, and we send the file to the email address on your profile, usually within two working days. The export covers profile records, session history and payment references.

Payment references from JazzCash, Easypaisa, SadaPay, NayaPay and Raast are held for the period tax and audit rules require, which is longer than session logs. We delete the rest once it is no longer needed.

Only where it is needed to run the service, such as identity checks or payment processing, and each partner works under a written agreement. We do not sell records or pass contact details to advertisers.

Closing the account stops new activity immediately and starts a deletion timeline for anything we are not required to keep. You get an email confirming what was removed, what remains on file, and why.

If you play from another supported region, the same policy applies but data may be held on servers in that region under its own retention rules. Where local law is stricter, that requirement takes priority for your account.