Your Data And The Policy Behind It
free casino runs your account, your payments and your play from one profile, and this page shows which data sits behind it. Read it before you open an...
How free casino Handles Account Data
This policy sets out what we collect when you open an account with us, how we store it, and the choices you have over it. We collect only what keeps your account running: your name, contact details, a date of birth check, the payment handle you use for JazzCash, Easypaisa, SadaPay, NayaPay or Raast, and the device data our security layer needs.
We do not sell personal data. Sharing is limited to processors who verify payments, run live tables and answer support messages, and only where local law permits. Where a region requires records to be held for a set period, we keep them for that period and then remove them. Access, correction and closure requests are honoured where supported regions allow. If a
local rule conflicts with a clause here, local law leads.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Ways To Reach Our Privacy Desk
Three routes reach the people who handle privacy requests, and each one is logged so nothing is lost between shifts. Every reply carries a reference number you can quote later.
Privacy mailbox
Write to our privacy desk from the email address on your account. Tell us your account handle and the clause you are asking about, and we reply with a reference number inside one working day.
Live chat window
Chat is staffed through the day for account holders in Pakistan. Use it for quick questions about what we hold, how a JazzCash, Easypaisa, SadaPay, NayaPay or Raast reference is stored, or how to start a correction request.
Closure request
Ask for account closure from inside your settings. We confirm the request, settle any pending payout step, then delete or anonymise your profile within the window your region allows.
Who Writes And Maintains This Policy
The people who write and maintain this policy are the same team that runs account security and payment verification. We keep the wording tied to what the platform does, and recheck it...
Policy authorship
Written in house by our security and payment teams rather than bought in, and matched to data flows we actually run, so each clause reflects what our systems do.
Update cadence
We revisit these clauses when we add a payment rail, a studio feed or a support channel. Changed wording is flagged at the head of the page that week.
Access requests
Ask for a copy of the personal data linked to your account and we send it as a readable file. Requests from supported regions are handled in arrival order within a few working days.
Security practice
Sessions are encrypted end to end, a login from a new handset triggers a verification step, and staff access to profile records is limited to the cases that need it.
Payment records
We store only the handle and reference our payment partners return for JazzCash, Easypaisa, SadaPay, NayaPay and Raast transfers. Full wallet credentials are never written to our servers.
Processor list
The studios, payment partners and chat providers that touch your data are named in the sharing clause. We keep that list current and tell you before a new processor starts handling account data.
Keeping Our Policy Pages Consistent
This page sits alongside our terms and cookie notices, and the three are written to agree with each other. Where two of them describe the same data flow...
What You See On This Policy Page
Six pieces of the page do the practical work: they help you find a clause, grasp it quickly and keep a copy. Nothing is buried in a wall...