Privacy Clauses
Covers what we collect, why a verification file is stored, and how long records stay. Nothing here overrides that page, and both are dated together.
One page holds every rule that shapes a rewards casino account, from how we check a JazzCash transfer to what happens if you request a payout from a...
Where local law permits, rewards casino opens accounts to people in supported regions of Pakistan, and access stays tied to the rules that apply where you live. We keep this page deliberately plain: what you accept when you register, how a dispute is handled, what happens when a rail such as JazzCash, Easypaisa, SadaPay, NayaPay or Raast is briefly unavailable, and how
we tell you before a clause changes. Wording can shift with your province or your bank's own conditions, so the version shown to you at sign-up is the one that binds your account. If a rule cannot be applied where you are, we say so instead of quietly restricting your login. Ask about any clause before you register, and our desk answers
policy questions the same day it answers payment ones.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Reach the policy desk the same way you reach payments support. The channels below are monitored by the same team, and if a clause reads oddly you can ask us to explain it before you register rather than after.
Send the clause you want explained along with the region you are in. Our desk replies in Pakistani English, usually within one working day, and gives you the wording as it applies.
Once your account is open, chat runs from morning until late evening Pakistan time for anything urgent — an access hold, a verification question, or a transfer query that touches a term.
Ask by email for a dated copy of the terms that apply to your account, and we send one you can keep. Banks often request it when a JazzCash or Easypaisa transfer is queried.
Every page here is written in-house by the people who run the lobby, then checked against the rails you actually use before it goes live. We date each revision so you can...
These pages are drafted by the team that runs the lobby, the payment desks and the verification queue, not outsourced. If a clause does not match how we actually operate, we rewrite it.
Every change carries a date and a short line saying what moved. Scroll to the foot of the page and you can see when the wording you are reading was last touched.
Provinces differ, and so do banks, so we re-read each clause against the regions we support and against Pakistani rails including Raast, SadaPay and NayaPay before publishing.
The wording around transfers mirrors what our cashier actually does with JazzCash, Easypaisa, SadaPay, NayaPay and Raast, including the hours each rail settles and the checks it runs.
Questions you send to support feed straight back into these pages. When the same clause gets asked about twice in a month, we redraft it and flag the change clearly.
Login, device and verification rules are described in the same language our security team uses internally, so nothing in the terms reads differently from the screen you see.
Our sibling pages are kept consistent, so a rule you read here never contradicts the withdrawals or verification wording elsewhere on the site. The list below shows where each one sits and...
Covers what we collect, why a verification file is stored, and how long records stay. Nothing here overrides that page, and both are dated together.
Sets out what you accept at registration, how we handle a suspended login, and when an account is closed. It shares its definitions with this page word for word.
Explains the small files your browser stores and how to switch them off. Its scope line matches the one used here, so the two read as a single document.
Describes the documents we ask for, why Raast and SadaPay transfers trigger checks, and the usual turnaround. Timings quoted here are pulled straight from that page rather than written twice.
Lists how long JazzCash, Easypaisa, SadaPay, NayaPay and Raast payouts take once cleared. Any figure in a clause on this page matches the cashier schedule exactly.
Shows the order to follow if something goes wrong — chat first, then email, then a written escalation. The same sequence appears in this page's dispute clause.
Holds the registered contact points, the trading name that appears on your bank statement, and the language we correspond in. Cross-references on this page all point there.
Beyond the clauses themselves, a few page elements do the practical work: they tell you what changed, which rule applies where you live, and how to ask about...