One Policy, Plainly Written For Pakistan
Everything you hand us when you open an account — your name, your number, the JazzCash or Easypaisa reference on each funding transfer — sits inside one privacy...
What Our Privacy Policy Covers
Our privacy policy covers the record we keep on you: what you type when you open your account, the device and browser strings your handset sends, the JazzCash, Easypaisa, SadaPay or Raast reference on each funding transfer and each payout, and the chat logs from any support thread you open. We use it to confirm who you are, settle your balance, meet
record-keeping duties that apply where local law permits, and keep the lobby steady for the rest of Pakistan. We never sell it. Retention periods differ by record type, so the policy lists them one by one instead of quoting a single number. Where local law permits, ask for a copy, a correction or a deletion and we reply inside the stated window
on this page.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Who Maintains This Policy Page
This page is owned by a named compliance team inside hollywood bet, not an outside copywriter. Drafts get read by our data lead and by the payments desk, because JazzCash, Easypaisa, SadaPay...
Named policy owner
One compliance lead signs off each version of this page, and the same person answers escalation threads. Ask who holds the role and we reply with a name.
Revision history kept
Each edit carries a date and a line on what changed, so you can tell whether a change affects you or only the wording. Older copies are available on request.
Plain wording, no padding
Short sentences and no legal filler. Terms like JazzCash and Easypaisa appear exactly as your own banking pages spell them, which matters when a clause turns on a rail name.
Two teams sign off
Payments checks every claim about transaction records, and support checks that the request routes described here match what the desk does each shift. Neither team signs alone.
Escalation route printed
If a reply does not settle your question, this page gives the next step and the address to use. Escalations are logged each month so we can see where answers fall short.
Tracker list published
The page names each cookie category and its purpose, from keeping you signed in to measuring page speed. Anything the account does not need can be switched off.
Where This Page Sits Beside The Rest
Privacy is one of several policy pages we publish, and the wording here stays in step with the rest. The terms page covers account rules, the cookies page...
What You See On This Policy Page
This page is built to be skimmed on a phone. A summary panel sits above the long text, every clause carries a short heading, and the...
Sticky contents rail
A short contents list stays pinned as you scroll, so you can jump to retention, sharing or deletion without hunting through headings on a narrow screen.
Summary panel at the top
The opening panel gives the short version in six lines: what we collect, why we collect it, how long we keep it, who sees it, and how to stop.
Clause-level links
Every clause has its own stable link. Send that link to our desk and the reply covers the exact paragraph you asked about rather than the whole page.
Rail chips that filter
JazzCash, Easypaisa, SadaPay, NayaPay and Raast each get a chip that narrows the page to the clauses covering that rail's records and settlement trail. Useful when you only care about one.
Type built for small screens
Body text is set at a size that survives a cracked browser window, with spacing you can read on a bus without pinching. Long clauses break into short paragraphs.
A dated copy to keep
You can save a dated copy as a file and hold it with your own records, which helps if you later want to compare the version you agreed to with a newer edit.