Terms Of Use
Our terms page covers the rules of an account, while this policy covers the data behind it. Read them together and the two should agree on every point.
When you open an account, sign in, or move money with JazzCash, Easypaisa, SadaPay or Raast, some data passes through our systems. This page sets out what we...
We collect what an account needs to work: the name, date of birth and contact number you give at sign-up, your device and connection details, and the transaction records created when you deposit or withdraw through JazzCash, Easypaisa, SadaPay or Raast. We also log lobby activity and support chats so a disputed round can be settled quickly. We use that data to
confirm the account holder, clear payments, keep sessions secure and meet record-keeping duties where local law permits. We do not sell your details, and we share them only with processors who help us run the platform under written contracts. Records stay while your account is open and for the retention period local rules require after closure. In supported regions you can ask
us to correct or delete anything not needed for those duties.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Behind the account screens sit a handful of safeguards we apply to everyone, whether you are browsing a live table or tracking a wallet withdrawal. None of them is optional, and none...
Every page you load, and each transfer step with JazzCash, Easypaisa, SadaPay or Raast, travels over an encrypted connection. Short session timers sign you out if a shared phone is left idle.
Your password sits in our systems as a one-way hash instead of readable text, and no member of staff can retrieve it. Forgotten passwords reset through a code sent to your registered number.
Signing in from a new device asks for a one-time code by SMS before the lobby opens. That single step blocks most account takeovers, so we keep it switched on by default.
Only a small operations group can open account records, and every lookup is stamped with a time and a reason. Access closes the same day when someone moves role.
We run scheduled checks on where data sits, who can reach it and how long we hold it. Findings become a written action list the team works through each quarter.
We ask for the fields an account genuinely needs and nothing more. Extra details you send to the support desk are cleared once the query is closed.
This policy does not stand alone. It sits beside the other pages that govern your account, and the wording on retention, sharing and access is written to match them. Where two pages...
Our terms page covers the rules of an account, while this policy covers the data behind it. Read them together and the two should agree on every point.
The cookie notice explains the small files that keep you signed in and remember your language choice. Each one follows the same retention periods set out here.
Payment terms explain how JazzCash, Easypaisa, SadaPay and Raast transfers settle, while this policy covers the records those transfers leave behind and who can open them.
Table rules govern how a round settles and how a dispute is raised. The data we hold from a live table session is exactly what this policy describes, with nothing added.
Market settlement rules sit alongside this page, and bet records follow the same retention window. When a settlement query needs your history, we pull it from one account store.
If you disagree with how a request was handled, the complaints route escalates to a senior officer. Response windows there mirror the ones stated on this page.
Closing an account does not erase every record at once, because settlement and tax duties still apply. The closure page and this policy state the same holding period.
What you see on the page itself matters as much as the wording. We laid this policy out so a first read is quick, a second read is...