Terms of Use
The terms page carries the contract itself. Everything here explains the same ground in shorter sentences, and where the two ever differ, the contract wording is the version that applies.
Here we set out the account terms, eligibility wording and jurisdiction rules that sit behind a gets bet account, so you know exactly what applies before you fund...
gets bet is offered jurisdiction by jurisdiction. Nothing here invites you to wager where the activity is not permitted, and you are responsible for checking the rules that apply where you are sitting when you log in. Where local law permits, an account opens the lobby; where it does not, registration is blocked for that region at the point of application and
again at login. We write policy to be readable rather than decorative. Account terms, payout verification and balance handling are set out in plain English, and each rule ties back to something visible inside your own account. If JazzCash, Easypaisa, SadaPay, NayaPay or Raast is the rail you use, the clauses on verification and settlement apply the same way, and support hours
are listed further down.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Policy questions rarely arrive at a convenient hour, so several routes stay open. Live chat suits a locked account or a paused payout, email suits a written answer on contract wording, and the regional eligibility desk handles supported-region questions from anywhere in Pakistan. Whichever you pick, quote your account reference so the first reply can be about your case rather than your details.
Chat is staffed for account and policy questions during Pakistan hours. Quote your account reference so the desk can pull your record without a long exchange of background.
Write in when you want a written answer about contract wording, data handling or a payout decision. We reply with a reference number and keep the thread open until it closes.
Ask here whether registration is open where you are, how PKR balances are handled, or which rails settle fastest. Answers use the same wording as the clauses on this page.
Legal text is only worth reading if you can check what it says. Our drafting is done in-house by the team that runs the account desk, revisions carry dates, and every claim...
Every clause on this page is written by people who run the account desk, not lifted from a template. If a sentence needs a second reading, we rewrite it until it does not.
Where we mention numbers or rails, we keep them checkable. Processor names, support hours and settlement windows are stated as they are, and claims we cannot demonstrate are left out.
We name the rails we actually settle through — JazzCash, Easypaisa, SadaPay, NayaPay and Raast — and we do not describe partners we cannot verify. Each one is listed by its registered name.
The rule set you agree to spans the sportsbook and the casino side alike. Payout checks, balance handling and the way dormant accounts are treated do not change when you switch tabs.
If you think a decision on your account was wrong, there is a written escalation path with named stages and reply windows. You get a reference number at every step.
Our eligibility desk answers questions about supported regions, PKR handling and local rails. Hours follow Pakistan Standard Time, and messages raised after hours are queued rather than lost.
Every policy page on gets bet draws from one rule set, so the wording you read here will not contradict the terms, privacy or payout pages. Where a page goes deeper, it...
The terms page carries the contract itself. Everything here explains the same ground in shorter sentences, and where the two ever differ, the contract wording is the version that applies.
Data handling has its own page. This one only describes what we do with account records when a payout check, a regional question or a duplicate-account case is open, and how long those records stay on file.
Payout timing, verification steps and rail cut-offs sit on the payout page. The legal wording here explains why those checks exist, what you agree to when you request a payout and who signs off.
Day-to-day account rules live on their own page: one verified account per person, accurate details and what happens with duplicates. This page sets out the reasoning behind each of those rules.
Login protection, device checks and session handling are described there in full. Here we note only that those steps form part of the terms you accept, and that you agree to keep your credentials private.
Supported and blocked regions are listed on the eligibility page. This page explains how that list is applied at registration, at login and again when you ask for a payout from a PKR balance.
A paused payout or a clarification request follows the complaint route, with named stages and fixed reply windows. Both pages share one reference format, so a number you quote works on either desk.
The policy layout is built so you can find a rule without reading everything. An index, a short summary, a dated change log and a contact block do...