Your Data And How We Hold It
This page sets out what 777 gems records when you open an account from Pakistan, why we hold it, and how you can have it corrected or removed...
What We Record And Why We Keep It
When you open an account with us, you give your name, date of birth, contact number, email and the payment reference tied to each balance load. Send funds through JazzCash, Easypaisa, SadaPay or Raast and we receive a confirmation code plus the amount, never your banking password or PIN. Device details such as browser type, approximate region and login times help us
flag unusual access early. Where local law permits, we hold the records our payment partners and regulators expect to see for set periods. We do not sell your personal data; sharing stays limited to processors that help run the platform under written confidentiality terms. Where a provincial rule is stricter than the national one, we apply the stricter rule, and you can
ask us to correct anything that is wrong.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
How This Policy Stays Current
The wording here is written and checked by the team that runs 777 gems accounts for Pakistan, not handed to an outside desk. We revisit it whenever we add a payment partner...
Policy owner
One named team owns this page from start to finish. They read every version before it goes live, confirm the wording matches what our systems do, and sign off before publication.
Scheduled passes
We run a full pass at least twice a year and any time a payment rail, hosting process or account security control shifts, so the text reflects present practice rather than an older setup.
Plain drafting
Sentences stay short and free of legal padding. Where a term is unavoidable we explain it in the same paragraph, because a clause you cannot follow offers you no protection at all.
Partner alignment
Before we link a new payment rail we confirm what data it sends and update this page. JazzCash, Easypaisa, SadaPay and Raast confirmations are handled the same way every time.
Security team input
Engineers who handle encryption, login monitoring and access records write the technical parts themselves, so the description of how your account is protected comes from the people maintaining it daily.
Change record
Each update is logged with the date it took effect. Earlier versions stay on file, and you can ask for the wording that applied when you first opened the account.
Aligned With Our Other Policy Pages
Everything we publish about your account follows the same standards, definitions and timeframes, so reading one page tells you what to expect from the next. If a term...
| Terms of use | Our terms cover what you agree to as an account holder; this statement covers what we do with the data you hand over. Both use identical definitions of account, session and closure. |
|---|---|
| Cookie notice | Cookies are set out on their own page, but the rule is the same: nothing optional runs until you allow it, and clearing them does not close your account or wipe stored records. |
| Account security page | Security steps such as password rules and login alerts are described there, and the data they generate is named here, so you always know which team holds it and for how long. |
| Payments page | Timings and rail names sit on that page; this one explains the references we retain from JazzCash, Easypaisa, SadaPay and Raast and how long each of those references is kept. |
| Contact hub | One place lists live chat, email and form routes. Privacy requests go through the same channels with the same reply windows, so support teams cannot lose your message between pages. |
| Questions page | Short answers there cover everyday queries about accounts and payouts; anything touching your personal data points back to this statement, so the longer explanation has one clear home. |
| Complaints route | If you are unhappy with how a request was handled, the escalation path on that page applies, and the team handling it works separately from whoever gave the first answer. |
What You See On This Page Here
We built this statement to be read on a phone without pinching or scrolling sideways. Headings sit in a pinned contents list, long clauses break into...
Pinned contents list
A short index stays visible as you scroll, so you can jump straight to the clause about retention, sharing or deletion without hunting through the whole page on a small screen.
Plain headings
Each block carries a heading that says what sits inside it, written the way you would describe it yourself rather than in formal drafting language that hides the meaning.
Two-column tables
Where we list what is collected against why it is needed, the answer appears in a simple block that reads cleanly on a phone as well as on a desktop screen.
Save and print
You can save a copy for your own files or print it. The saved version carries the effective date, so you always know which wording you are holding.
Effective date stamp
One line at the start shows when this text last changed. If that date is newer than the copy you saved, a quick comparison shows exactly which clauses moved.
Quick exit links
Buttons to live chat and to the contact form sit close to the text, so a question raised while reading does not mean losing your place or starting again.