What We Do With Your Account Data
This page sets out what welcome slots collects when you open an account, how we hold it and who else sees it. We wrote it in plain English...
How We Treat Data Across Supported Regions
Every clause here describes the posture we hold for accounts opened from supported regions, and we say when something depends on where you live. If a rule in your province or country differs, the stricter reading applies. We do not sell account data. We share it only with the payment partners that clear your JazzCash or Easypaisa transfer, the studios whose tables
you open, and the providers that keep our systems online, each bound to one job. Records tied to a transfer or a session stay while local rules require and no longer. You can ask what we hold, request a copy, or have a wrong detail corrected.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Who Writes And Maintains These Clauses
This page is kept by the team that runs the account systems it describes, so the wording tracks what our platform does rather than what a template says. Payment rails, studio partners...
Written In-House
The copy here comes from our own operations and compliance writers, not a bought article, so the examples you read match how our systems behave in practice.
Dated Updates
Every revision carries a date and a short line saying what changed. If we adjust how long a record lives, or add a partner, you read it here first.
Plain Wording
We skip legal shorthand where a normal sentence works. When a clause depends on your province or country, we say so in the same paragraph rather than cross-referencing.
Named Partners
Studios, payment rails and hosting providers that handle data for us are named, so you can see who is involved. None may use it for their own campaigns.
Local Focus
This page is written for Pakistan, covers JazzCash, Easypaisa, SadaPay, NayaPay and Raast flows, and borrows the vocabulary our support team uses, so nothing gets lost.
Open Corrections
Spotted something that does not match your experience? Tell us. We publish a correction when a detail was wrong, and we mention the reader who raised it, if they want that.
How This Wording Sits With Our Other Pages
Our policy pages share one vocabulary, so you are not reading a different definition of the same word on each one. The wording here lines up with our...
What You See On This Policy Page
This page is built to be scanned. A short summary opens it, the full clauses follow in numbered blocks, and the questions we get asked most...
Summary Block
The opening block gives you the posture in five lines: what we collect, why, who sees it, how long we hold it and how to object.
Numbered Clauses
Each clause carries a number you can quote in a support message. Send the number and our desk opens the exact rule, which saves a long explanation.
Context Chips
Rail names and studio names sit as short chips beside the clause they affect, so you can tell at a glance whether a holding period covers a JazzCash transfer.
Jump Links
A small contents row links to each heading. Tap it and the page moves to that clause, which helps when you check one point on a phone.
Request Buttons
Copy, correction and erasure requests each have a button that opens a short form. The form asks only what our desk needs, nothing beyond that.
Reader Wording
Headings and key clauses use en-PK wording written for Pakistan, so terms like Raast and supported region read the way you use them, without legal phrasing.