Registration Terms
Agrees with the sign-up section of our account pages: one account per person, your legal name, and a mobile number you control for verification codes.
Every rule behind your sapphire bet account sits on this page — how you register with a Pakistani mobile number, how JazzCash, Easypaisa, SadaPay and Raast transfers are...
These terms bind the account you open with sapphire bet, and they sit alongside the rules of whichever jurisdiction applies to you. Where local law permits online play, you can register, move money in through JazzCash, Easypaisa, SadaPay, NayaPay or Raast, and withdraw to the same wallet, with every movement logged against your account record. Where local law does not permit it,
please do not open an account with us. We revise this page when payment rails, tax treatment or provider requirements change, and the version live at the time governs you from that moment. Staying signed in after a revision means you accept the altered wording. If a clause reads differently to what you were told at registration, the written terms on this
page take precedence.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Our terms pages earn confidence when the people writing them can show how the platform runs. The policy desk sits with the payments and risk teams, so wording about JazzCash clearing times...
The people who write these terms also work beside the payments, risk and support desks, so clearing times, hold periods and verification steps described here match the queues you actually meet.
Every revision to this page carries a date and a short summary of what moved, so you can see which clause changed and whether it touches withdrawals, registration or bet settlement.
We describe JazzCash, Easypaisa, SadaPay, NayaPay and Raast in the way those rails behave in Pakistan, including weekend clearing delays, wallet name matching and the documents a bank may ask for.
Two-factor codes at login, device checks on a new phone and forced sign-out on shared computers appear here as they work in the product. Keep your number current so codes reach you.
Support takes English and Urdu callers across Pakistan time zones, and this page uses Pakistani English so payment names, working days and public holidays line up with what your bank uses.
We avoid award claims, player counts and dates we cannot show you. Where a rule depends on the requirements of a supported region, we name that region and point you to the notice in your dashboard.
Our legal pages share one structure, so a rule reads the same way wherever you find it. The wording, version stamp and support contacts stay matched across every notice we publish, letting...
Agrees with the sign-up section of our account pages: one account per person, your legal name, and a mobile number you control for verification codes.
Uses the same definitions for personal data, retention periods and processors that appear here, so a term carries one meaning across every page we publish.
Mirrors our clause on timing, wallet name matching and document checks for JazzCash, Easypaisa, SadaPay, NayaPay and Raast, counted in the same working days.
Sits beside the term on void bets, pricing errors and market suspension. When a settlement question reaches us, both pages are read before a decision.
Repeats the login, two-factor and device rules stated here, and keeps identical wording on what happens if you share a password or lose a registered number.
Sets out the same escalation path described on this page, from a first reply at the support desk to a written outcome inside the stated response windows.
Logs each revision with a date and a plain summary, so you can compare what moved across policy pages without hunting for older wording elsewhere.
The terms page is set out so you can reach a clause without scrolling through walls of text. A clause index runs down the side on wider screens...