Terms Of Use
Your account terms and this policy share one foundation: we collect the minimum we need, we say why, and we never trade your details for reach. Read them together.
This page sets out what we collect when you open an account, why we need it and the choices you keep. It covers device data, the payment reference...
We write this policy the way we run our brand home: plainly. When you register, we collect your name, mobile number, email, date of birth and the payment reference that JazzCash, Easypaisa, SadaPay or Raast sends us. We use it to verify your account, release withdrawals to the wallet you chose, and meet record-keeping duties that apply in supported regions. We do
not sell your details to outside advertisers. Access inside our team is restricted, transfers are encrypted and every look-up is logged. Retention follows the local timelines; after that we delete or anonymise the record. Where local law permits, you can ask to see, correct or erase what we hold. We keep this page current as our rails change.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
This policy is not assembled by an outside agency and left alone. Our data team drafts each clause, tests it against how our account tools and wallet rails...
A named data team inside beste casino owns this text. They revisit it after any change to our wallet rails...
Every edit to this policy is dated and summarised in a short changelog at the foot of the page. You...
A second reader strips out legal padding before publication and rewrites sentences that could be misread. If a paragraph still...
We document what each local rail shares with us. JazzCash, Easypaisa, SadaPay, NayaPay and Raast return a payment reference and...
Our team follows the data rules that apply in the regions we support, and flags any clause we cannot honour...
Spotted something unclear or out of date? Write to the privacy desk and we will explain the clause or fix...
Every policy page on this site reads from the same set of definitions, so the wording here lines up with our clauses elsewhere. You are never left wondering which page wins when...
Your account terms and this policy share one foundation: we collect the minimum we need, we say why, and we never trade your details for reach. Read them together.
That notice lists the tags our pages drop and the switches you can turn off. Anything that identifies you is described here as well, so the two pages never disagree.
Verification and one-account-per-person rules live there. The fields we gather to enforce them are named in this policy, including what stays after an account closes.
That page names JazzCash, Easypaisa, SadaPay and Raast as our local rails. Here we explain the reference each one returns and how long we keep it for audit.
Encryption, device checks and staff access controls are described there. This policy tells you which of those controls touch your personal record and who can open it.
Answers on account access, closures and contact updates use the same vocabulary as this page. If two pages ever read differently, our desk confirms which applies to your case.
If our handling of your data falls short, escalate through that route. Every complaint is logged with a reference, checked by the data team and answered in writing.
We designed this page so you can find your answer without reading every clause. Short badges sit under the headline, the stance panel opens with our position, and...