How betting win Handles Your Account Data
Your data is the whole subject of this page, and we keep the explanation short: what we collect when you join, why we hold it, who sees it...
Where We Operate And Which Rules Apply
We collect and hold personal data under the rules that apply in the regions where we operate, and where local law permits we apply one internal standard across every market, Pakistan included. That standard covers what we gather to run your account: your name, contact details, a date-of-birth check, and the wallet identifiers tied to your JazzCash, Easypaisa, SadaPay, NayaPay or Raast
transfers. We keep session and wager records because we need them to settle disputes and meet our own audit rules. If the law where you live gives you stronger protection, that protection still applies to you. Where local law permits, we share a limited set of details with payment partners so your transfers clear and withdrawals can be verified.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Contact Us About Any Data Question
Privacy requests land with a real person on our Pakistan support desk rather than a queue that never moves. Write to us about a copy of your data, a correction, or a deletion, and we will tell you plainly what we can and cannot do. We answer in English and log every request so nothing slips between shifts.
Live chat
Our chat window stays open through the night for account and data questions, and the agent can open your record while you type. Most replies land within minutes.
Email the privacy desk
Use email when you want a written trail: data copies, corrections, deletion requests, or questions about our cookies. We answer every message, usually inside one working day, Monday to Saturday.
Request from your account
Signed in? Open account settings and send the request from the panel. It arrives tagged to your profile, so we can confirm who you are before anything is opened or changed.
Written By The Team That Runs Accounts
This page is drafted in house by the same people who staff the accounts desk, the settlements queue and the security checks, so nothing here is written by someone who has never...
Drafted in house
The accounts, settlements and security teams write every clause, so each line reflects a process we actually run rather than generic wording borrowed from another operator's site. We date each edit.
Settlement knowledge
Our writers sit beside the people who reconcile JazzCash, Easypaisa, SadaPay, NayaPay and Raast transfers daily, which is why the sections on stored payment details name each rail and explain it.
Security-led wording
Clauses on access logs, device data and two-step verification come from the engineers who built those controls. When a safeguard is replaced, the matching paragraph is rewritten in the same release.
Plain Pakistani English
We write for readers in Pakistan and cut the padding. Long sentences get split, borrowed legal jargon gets explained, and each heading tells you what sits underneath before you begin reading.
Dated versions
Every update carries a date stamp and a short line describing what moved. You can hold the current text beside the older one and see exactly which paragraph was altered.
Checked twice a year
We walk through the document twice a year, testing each claim against the live system. Anything that no longer matches how we handle accounts gets rewritten or taken out.
How This Page Sits With Our Others
We keep a short set of policy pages and they are meant to be read together. This one covers personal data. The terms page covers your account and...
| This page vs terms | Our terms cover account conduct, wager rules and closure. This page covers what we collect, how long we hold it, and how you ask for a copy of it. |
|---|---|
| This page vs cookies | Cookies live on your device; personal data sits on our systems. The cookie page lists what each script does, while this page explains the login and transfer records those scripts help create. |
| This page vs verification | Document checks belong to our account verification page, which lists what to upload. Here we explain where the results are stored and which staff can open them. |
| This page vs settlements | Settlement timings sit on their own page. This policy covers the reference numbers we keep from JazzCash, Easypaisa, SadaPay, NayaPay and Raast transfers, and the reason we keep them. |
| One voice throughout | Every policy page uses the same plain Pakistani English, the same heading order and the same date format, so you never have to relearn the layout when you move between them. |
| Single change log | One change log spans the whole set. When a page is updated, the log records the date, the reason, and a link to whichever companion page the edit also touches. |
| Disagreement path | If you believe two pages contradict each other, quote both lines to us. Our compliance lead compares the wording and replies once the out-of-step page has been corrected and confirmed. |
What You Will Find On This Page
We laid this page out so you can reach the clause you need without scrolling through one long block. Each heading answers a single question, the...
Dated change list
A running list near the foot of the page shows what changed and when, with older wording archived beside it. You can check whether a clause moved since your last visit.
Clause links
Each heading links to its own section, so a support agent or a friend can send you straight to the paragraph that answers your question without extra scrolling.
Named wallets
Where storage differs between rails we say so. JazzCash, Easypaisa, SadaPay, NayaPay and Raast each get their own line instead of one vague mention of payment partners.
Short summaries
Each technical clause opens with a sentence in everyday words, then the precise obligation follows underneath for anyone who wants the exact wording we work to and nothing more.
Prints cleanly
The page prints to a single column and keeps its heading order, so you can save a copy to your device or hand a printed version to someone helping with your account.
Regional clauses
Where a rule shifts by market, a short line names the region and the condition attached, including the wording we use for supported regions and places where local law permits access.