Account conditions
The account conditions you accept at sign-up sit alongside this notice, and both describe the same registration fields so you never meet two different explanations of one form.
777gem explains, in plain English, what account data we collect when you open an account, why each field matters to your cashouts, and how you can ask us...
This notice covers the 777gem account area, our lobby, the sportsbook pages, the cashier, and our email and chat support. It applies where local law permits, and it applies whether you reach us from a phone browser or a tablet. We act as the data controller for the account records we hold, and we keep those records for the periods Pakistani tax
and audit rules require once you close your account. Where local law permits, you may ask to see the fields we store, ask us to correct a mistyped name, or ask us to erase the marketing preferences we keep. Some retention duties survive an erasure request, and we will tell you which ones apply to your file.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Data requests reach a small team rather than a queue that closes tickets without reading them. Pick the route that suits you: email gives you a written trail, chat answers while you are signed in, and a marked written request gets a reference you can quote later.
Write to our privacy desk from the address on your 777gem account and we will match the request to your file before we answer. Replies usually land within one working day.
Signed-in chat is the quickest route for data questions tied to a cashout, because the agent can see your JazzCash or Easypaisa reference without you pasting it again.
If you want a formal written response, mark the message as a data request. We log it, assign a reference, and keep a copy in your account history for your own records.
The notice is maintained by the people who build the account flow, not assembled from a template. When the cashier gains a rail or the sign-up form loses a field, the matching...
Every paragraph on this page is drafted by the 777gem team that runs the account system, so the wording matches how our cashier and support desks actually behave day to day.
We rewrite this notice when the account flow changes rather than leaving outdated clauses in place, and we keep sentences short enough to read on a phone screen between trains.
Before publishing, we walk the sign-up form, the cashier and the chat widget to confirm each clause we describe still matches what you see while signed in yourself.
The payment names you read here, JazzCash, Easypaisa, SadaPay, NayaPay and Raast, are the rails our cashier actually supports for Pakistan accounts, not a copy-pasted list of foreign wallets.
We name the categories of providers we share data with, such as payment processors and fraud screening tools, instead of describing them as unnamed third parties somewhere in the chain.
Each time we change a clause we note the date at the foot of the page, so you can tell whether the version you accepted last month still stands today.
You will meet this notice beside our account conditions, cashier page and security page. We keep one vocabulary across all of them: the same field names, the same payment rails and the...
The account conditions you accept at sign-up sit alongside this notice, and both describe the same registration fields so you never meet two different explanations of one form.
Our cashier page lists the same JazzCash, Easypaisa, SadaPay and Raast rails that appear in the chips on this notice, and it explains how each reference is stored.
Sign-in rules, device checks and password resets are set out there in the same order you meet them here, so the security wording and the privacy wording agree.
Support answers link back to the matching clause on this page rather than repeating it, which keeps one authoritative wording for every data question you raise with our desk.
Escalation steps published elsewhere on the site finish on the same address shown in our contact card, so a data complaint never dead-ends without a reply from us.
The opt-out checkboxes in your account mirror the preferences we describe here, so unticking one removes you from the same mailing list this notice names, and at once.
Pages aimed at Pakistan readers use the same where local law permits phrasing, so nothing on a sibling page contradicts what this notice promises for your file at any point.
The policy layout itself tells you a lot about how we work. Clause numbers, a payment chip row, a dated change stamp and cross-links to the...
Each clause on this page carries its own number, which makes it quick to quote a specific line when you write to our privacy desk about a stored field.
A short row of chips names JazzCash, Easypaisa, SadaPay, NayaPay and Raast so you can see which rails feed the transaction records we describe here on this notice.
A date stamp near the foot of the page tells you when the wording last changed, and we update it whenever the account flow adds a new data field.
An opening summary states what the notice covers before the numbered clauses begin, so you can decide quickly whether you need the full detail on your first read.
Inline links point to the cashier, security and account-condition pages so you can jump straight to the clause that answers your data question without searching the whole page.
The card you see in the contact block repeats the email address and chat route that handle data requests, so you never have to hunt through the page.