Privacy terms
The privacy page covers what we collect and why, while this agreement covers what you and we must do. Data handling sits there; account conduct and obligations sit here.
Every account here runs off one written agreement, and this page is it. We set out what you can expect from us and what we expect from you...
These conditions are the agreement between you and casino slots from the moment you open an account and start using the lobby. They apply where local law permits and, in supported regions, they sit alongside the payment rules that cover JazzCash, Easypaisa, SadaPay, NayaPay and Raast transfers. Some clauses shift with your region, because different areas allow different products, withdrawal routes and
stake ranges. Where that happens, the version you accepted at registration takes priority over the general wording here. We keep the language plain so you can check one clause without help. If a rule cannot be enforced in your area, the rest of the agreement still stands. You confirm the current text each time you log in, and every amendment appears on
this page with its date.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
The same account and payments team that runs the lobby writes these conditions, so nothing here is copied from a template. We date every amendment and keep the text that applied on...
Our own account and payments staff draft these conditions rather than copying a template, so the wording matches how the lobby, wallet and verification steps actually behave for you.
Each change carries the date it took effect, letting you match a rule to a period. Ask support for the version that applied on any day your account was open.
We skip legal padding where a short sentence says the same thing. If a clause still confuses you, support will rewrite it in simple English while you are connected.
Clauses that differ by area carry a short region marker. You see the list that applies to your registered country at login, next to the wallet rails you use.
Older copies of this agreement stay on file. Request a dated copy and we email it to your registered address so you can compare what has changed since you joined.
Acceptance is logged against your account with a timestamp. That record shows which version was live when you joined and which one you confirmed at each later update.
This page sits inside a small set of documents, and each one answers a different question. Read them together for the full picture of how an account works; read this one alone...
The privacy page covers what we collect and why, while this agreement covers what you and we must do. Data handling sits there; account conduct and obligations sit here.
Offers we run carry their own campaign conditions. This agreement explains the account behind them, while each campaign document holds the qualifying rules and the timeline.
That page lists the rails we support and the time each one needs, while here we cover what happens when a request is refused, reversed or held for a check.
Fair play deals with how a round is settled and how a dispute over a result is handled. This agreement sets the wider obligations that surround those rounds.
Where an offer involves turnover conditions, the campaign document sets the numbers. Our agreement explains how those numbers attach to your account and when they lapse or reset.
Sign-in, device approval and password recovery are explained on the security page. This agreement states your duty to keep credentials private and to report a suspected breach fast.
If a decision goes against you, the complaints page shows the escalation steps and the reply windows. This agreement confirms those windows and the point at which a matter closes.
The layout follows the order you meet the platform: account, verification, rounds, then disputes. We place the clause you are most likely to need first, so you find...