How 777re Handles Your Account Data
When you register, the details you type, the payment references behind your JazzCash or Raast transfers and your activity in the lobby sit on one profile that only...
Where Our Privacy Rules Apply
777re is built for people who hold accounts in places where local law permits online play, and our privacy commitments follow that same map. If you are in Pakistan, your records are handled under the terms on this page and the partner conditions you accept when you open an account. Where a province, region or wallet partner applies stricter rules of its
own, the stricter version applies and we tell you before the position changes. The partners we work with, from a studio streaming a live table to the wallet clearing your Easypaisa transfer, see only the slice of data needed to finish one job. We keep a dated trail of every request our desk handles, so you can ask what was shared, with
whom and when. Access stays limited to supported regions, and we may need to close an account if the rules where you live change.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Who Maintains This Privacy Page
The wording on this page is owned by our compliance team rather than a sales desk, and it is dated each time a paragraph changes so you can see exactly what moved...
Named owner
Every clause on this page has a named owner inside 777re, so a question lands with a person rather than a shared inbox that nobody feels responsible for.
Change log
We date each revision and can share the earlier wording on request, letting you compare what you agreed to with the version published on this page today.
Plain wording
Formal phrasing that confuses readers is rewritten in the same update; where a sentence needs a lawyer to decode it, we treat that as a fault worth fixing quickly.
Operations input
The staff who handle JazzCash, Easypaisa and Raast queries write the sections covering transfer references, because they work with those records during every shift and know where confusion starts.
Facts we can show
We quote figures we can point to, such as support hours and reply windows, and leave out claims about our size that we cannot evidence when somebody asks.
Second read
Someone from our support desk reads every rewrite against Pakistani data expectations before publication, and their comments are folded into the wording before it appears.
Keeping Every Policy Page Consistent
Our account rules, cookie notice, settlement wording and this privacy page are written as one set, so a phrase you read here means the same thing on the...
| Shared definitions | Terms such as account record, transfer reference and verification data carry one meaning across every policy page, so you never have to guess which version applies to your situation. |
|---|---|
| One contact route | All of our policy pages point to the same privacy desk address and chat entry point, so a question cannot be passed around in circles between separate teams. |
| Matching revision dates | When we touch this wording we check the neighbouring pages on the same day, so the revision dates line up and you can see which documents changed together. |
| Identical chip row | The JazzCash, Easypaisa, SadaPay and Raast chips shown here carry the same names on our account and settlement wording, keeping the language flat across every document. |
| Shared retention logic | The period we keep a closed account's records is described the same way here and on the account rules page, so both documents give you one answer. |
| Consistent escalation | If a request needs a manager, the path from chat to the compliance team is identical whichever policy page you started reading, and one reference format follows you. |
| One language policy | Everything is published in English for Pakistan first, and any Urdu summary added later is checked against this wording rather than drafted as a separate text. |
What Sits Inside This Policy Page
You should not have to scroll through ten screens to find one answer, so this page is built in blocks that read well on a phone. Each block...