Account terms
Our account terms define registration, logins and closure, and this page reuses those exact words. When the wording lines up, you never wonder which page governs your session.
We collect only what an account, a login and a payout genuinely require, and we show you where each record sits. Open your account and your data controls...
Our privacy policy spells out, in everyday Pakistani English, what we log when you register, which payment rails appear on your account record, and how long each entry stays with us. Because we serve several regions, the rules that bind your data depend on where you sign up and on what local law permits. Inside the policy you will find how we
handle your name, phone number and identity details where required, the login signals we watch for signs of account takeover, and the retention windows tied to JazzCash, Easypaisa, SadaPay, NayaPay and Raast transactions. Where a regional requirement is stricter, that rule takes priority for your account. You can ask for a copy of what we hold, request a correction, or close the
account and let the retention clock run out.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Privacy questions deserve a real answer from a real person, so we keep three ways in. Tell us which data point you mean and add your registered email, and we route it to the colleague who owns that record. Most privacy requests get a first response within one working day, while account-access issues jump the queue.
Reach our privacy desk through live chat inside your account panel. Share the email you registered with and what you want changed, and the team opens your record.
Write to our privacy mailbox with your account email and a short description of the request. Attach screenshots of any JazzCash or Raast entry so we can match it quickly.
Use the in-account form to ask for a copy, a correction or a deletion. The form time-stamps your request, which sets the clock we work to for your region.
Before any policy sentence goes live, our own team tracks the flow a Pakistani account actually takes: registration, a first transfer through Easypaisa, a live-table session, then a payout to Raast. We...
One named privacy lead signs off every change to this page, so wording does not drift between releases. That person also handles escalations raised by our support desk.
Each quarter we route a fresh test account from sign-up to a payout and check every field captured. Anything that check cannot justify gets removed before the next release.
Our privacy line runs seven days a week, 9am to 11pm Pakistan time. Account-access complaints are handled around the clock, because a locked login should never wait for opening hours.
Staff access is logged too, so a look at your record is itself recorded. Only colleagues handling your ticket can open the file, and our privacy lead sees every entry.
If a field is not needed for a payout, a login or a legal duty, we do not collect it. That rule shapes every form you fill, right from registration.
Payment partners, streaming hosts and message providers work under written data terms. They handle only the slice their task needs, and we check that each partner keeps to that limit.
This page sits in a set, and every page in that set uses the same voice, the same definitions and the same contact routes. Read our account terms, cookie page or payout...
Our account terms define registration, logins and closure, and this page reuses those exact words. When the wording lines up, you never wonder which page governs your session.
Device signals and cookies are described in full on the cookie page. Here we say how those signals feed login checks, and we link across so both pages stay in step.
Payout rules cover how JazzCash, Easypaisa, SadaPay, NayaPay and Raast transfers are verified. This page carries the matching data note on what a transfer record keeps and for how long.
Sportsbook rules explain market settlement, while this page says which betting-history lines we retain. Same window, same definitions, so a query has one answer rather than two.
Password resets, two-step logins and device approvals sit on our security page. The privacy side describes the records those steps create, quoting the same access limits for both.
A refusal under this policy can be escalated through the complaints route on our contact page. You get a written reason and a second look from someone outside the original team.
Every edit to this page lands in a dated change log at the foot of the page. Material shifts are flagged before they take effect for your account.
Everything this policy describes has a switch or a screen behind it, and those screens live in one panel. From your account you can open the record of...