Account Terms
The rules you accept when you open your account. The data clauses there match this page, so nothing contradicts when you read both together.
This privacy policy explains what we collect when you open an account with us, how we use it, and the choices you keep. We wrote it in plain...
We treat your account data as yours, not ours to trade. Where local law permits, we process the details you give us so your account opens, your JazzCash, Easypaisa, SadaPay and Raast payments settle, and our support desk can trace anything you report. Access rules differ by market, so if something is not available in your supported region we will tell you
before you send documents. Retention follows the rules where you live, and we keep transaction references while a payment dispute could reasonably be raised. You can ask what we hold, request a correction, or opt out of updates. One message to our privacy desk starts that, and we confirm in writing once it lands.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Questions about this policy should reach a person, not a queue. Our privacy desk answers emails within one working day, and chat is staffed from 10am to 10pm Pakistan time, seven days a week. If you are asking about a JazzCash or Raast reference, quote the transaction ID so we can trace it with our payments team the same day.
Send your question from the email address on your account. We confirm receipt the same working day, then reply once the relevant team has checked your request.
Chat runs 10am to 10pm Pakistan time, seven days a week. Keep your account email ready so our agent can pull your record and explain what we store.
Want a copy of your details or a correction applied? Ask through chat or email and we list what we hold, then confirm once the fix lands.
A policy only helps if you can check it against real practice. These are the habits behind ours: a named team per clause, dated revision entries, plain-English summaries...
Each clause here has a team behind it. Ask who set a retention window and we name the desk that...
Every edit carries a date and one line explaining why. You can see which wording moved between versions instead of...
Long clauses sit beside a short summary written for readers, not lawyers. You get the practical meaning first, then the...
We verify sign-ins with device checks and one-time codes, so nobody else reads your records. Spot a login you do...
Ask for a copy of what we hold and we build it from your account, payment and chat history. Expect...
Agents who answer policy questions can view your account while they write back, so replies about JazzCash references or withdrawal...
Every policy we publish, from account terms to cookie handling, follows the same editorial shape so you are never guessing where a rule sits. When we change how data is handled, the...
The rules you accept when you open your account. The data clauses there match this page, so nothing contradicts when you read both together.
Which cookies and local storage we set, and why. The identifiers listed there are the same ones described in the device-data part of this policy.
How sign-in, device checks and password resets work. Anything touching your personal details is cross-referenced here instead of repeated in different words.
How JazzCash, Easypaisa, SadaPay and Raast transactions are recorded, reversed and traced. The references mentioned there are the ones our payments desk keeps.
Where to raise a concern about how we handled your details or a withdrawal. The escalation steps are identical to the ones in the support block above.
The rules that keep games and markets level for everyone. Where fair play checks use your account data, this policy explains what is collected and for how long.
The page you are reading. When data handling changes, the revision date at the head of the page moves and the sibling pages follow within the same working week.
We built this page to be skimmed on a phone and read properly on desktop. Sections carry anchor links, the revision date sits above the first heading, and...