Terms of use
Sets out the rules for holding an account with betpak, including what happens if details you give us turn out to be wrong or have gone out of date since you joined.
This page sets out, in plain Pakistan-focused English, what we collect when you open an account with betpak, why we collect it, and how long we keep it...
Privacy rules differ from province to province, so we apply the standard that fits where you are located, and we always work within local law. Where local law permits online play, we keep records of the data we need to run your account, settle payments and meet our own legal duties. If a rule in your region asks for something different, that
rule comes first and we adjust our handling to match it. Nothing on this page sets aside a protection you already have under Pakistani consumer or data law. We treat supported regions separately so that your experience, including how your payment references are stored, follows the same rules whichever device you sign in from, so our team knows which retention window applies.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
This policy is drafted by the betpak compliance team and checked by the same people who handle account security and payment reconciliation. When a payment partner changes how it passes references to...
The team drafting this page also handles daily account and payment checks, so the wording reflects how your details really move through our systems, not a template borrowed from elsewhere.
Before we publish a change, we trace each claim back to the live setup, including the account dashboard, our payment reconciliation logs and the chat tool you use to reach us.
We avoid legal padding where a short sentence does the job. If a clause affects what you can ask for, or how long we keep something, we say so directly on this page.
Every edit to this policy carries a date. If you want to see whether anything affecting your account has moved, check that line first, then ask us if something looks unclear.
We collect the fields we need to verify you, run your account, settle transactions and answer your messages. Nothing extra is added simply because it is easy to store.
Whether you sign in from a phone on the way home or a desktop late at night, the same privacy rules apply. Device choice never changes what we collect or who can see it.
Our policy pages share one structure so you can move between them without relearning the layout. This page explains what we collect and why; the terms page sets out the rules of...
Sets out the rules for holding an account with betpak, including what happens if details you give us turn out to be wrong or have gone out of date since you joined.
Explains the small files stored by your browser, what each one does for sign-in and for keeping your session stable, and how you can clear them from your own device.
Covers passwords, one-time codes and what we do if we see a sign-in that does not look like you, plus the steps you can take from your own phone or laptop.
Describes how JazzCash, Easypaisa, SadaPay and Raast transfers are matched to your account, and which details appear on your statement afterwards, so nothing on your side is a surprise.
Shows how long each type of record stays on our systems, from chat transcripts to transaction references, and what triggers a scheduled deletion rather than an indefinite hold.
Explains which supported regions can open an account and why access depends on local law, so you know where the service is meant to be used and where it is not available.
Lists the channels where you can reach us about policy questions, including the in-account chat window and the email address monitored by our support desk throughout the week.
The policy page is built from the same parts you meet elsewhere on betpak: short chips, plain headings and answer boxes you can scan. Currency in examples follows...