Shared definitions
Terms such as account data, wallet record and retention window mean the same thing on every policy page we publish, so you can move between pages without a glossary open.
LEGAL REFERENCE
Our Privacy Policy and What It Covers
This page explains, in plain English, what happens to your details when you hold an account with 777 sp. We cover what we collect, why we collect it...
Account dataWallet recordsDevice signalsChat transcriptsCookie choices
Where Local Law Permits, This Policy Applies
777 sp operates in supported regions, and this privacy policy applies only where local law permits you to hold an account. Where a Pakistani rule is stricter than what we describe here, that rule takes priority over our wording. We store account and wallet records — including JazzCash, Easypaisa, SadaPay, NayaPay and Raast references — for as long as your account stays
active, plus a short period afterwards for accounting and dispute handling. If you close your account, we delete or anonymise anything we no longer need. Requests to see, correct or remove your details can be sent to our data desk at any time. We keep this wording short on purpose, and you can ask for a fuller written explanation of any clause.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
HOW WE BUILD IT
How This Policy Is Drafted and Kept
The wording here is written by the team that runs day-to-day account operations, then checked line by line before it goes live. We re-read every clause when the...
Author team
Privacy wording here is signed off by our own operations leads rather than an outside agency. They answer account queries...
Revision dates
Every edit carries a date and a short changelog line, so you can see whether your rights moved. Older versions...
Plain-language pass
We test each paragraph against one question: could a new account holder in Karachi follow this after a single read?...
Security practice
Account access runs over encrypted connections, with optional two-step verification and alerts when a new device signs in. Staff reach...
Second-read checks
A reader from a different team works through the draft before publication. They flag vague promises, missing retention periods and...
Corrections route
Spot something out of date? Tell our data desk and we will investigate it, then publish the fix with a...
PAGE CONSISTENCY
How This Page Matches Our Other Policies
Our policy pages share one structure so you do not have to relearn the wording each time. Definitions carry across, retention windows are stated in the same format, and every page names...
Matching retention wording
Each page states how long we keep the records that clause covers, using the same active-plus-follow-up phrasing. That keeps the whole set easy to compare at a glance.
One contact route
Every policy page points to the same privacy helpdesk, with identical chat and email options. You are never handed a different address depending on which page you opened.
Same jurisdiction wording
Where pages touch on access, all of them use the same supported regions phrasing instead of implying worldwide availability. That keeps your legal position clear as a reader in Pakistan.
Synchronised edits
When we amend one clause we check the sibling pages for the same wording in the same release, so you never see two policy pages disagreeing about your rights.
Aligned changelogs
Revision dates appear in the same place on each page, and changelog lines follow one order: what changed, when it took effect and which records are involved for you.
Consistent rail names
Pages that mention money movement all name JazzCash, Easypaisa, SadaPay, NayaPay and Raast the same way, so your statement references line up with what you read here on this page.
What You See Across This Policy
This page is built to be skimmed before it is read closely. Kicker labels at the start of each block tell you what the block covers...
Skim-friendly headings
Each block carries a short heading plus a kicker tag, so you can find the retention clause or the contact route without reading every sentence on the page.
Payment name chips
Where a clause touches on money movement, the chips beside it name JazzCash, Easypaisa, SadaPay, NayaPay and Raast directly, keeping our wording tied to rails you already use.
Question block
Common privacy questions sit together near the bottom, each answered in a short paragraph. If our helpdesk answers the same one three times a week, it earns a place there.
Shorter paragraphs
We keep paragraphs short and skip dense walls of text, because most policy reading happens on a phone between other tasks and long blocks tend to get skipped.
Date stamp
A revision line at the foot of the page shows when the wording last changed, so you can tell whether the copy you saved is still the copy we publish.
Support hours
Our helpdesk keeps Pakistani working hours and replies in the language you write in, including English and Urdu, so answers arrive while you are awake and ready to read them.
Privacy Policy Answers for Your Account
We collect the details you type at sign-up plus wallet references from JazzCash, Easypaisa, SadaPay or Raast. Device type, login times and lobby activity are also logged so unusual access stands out.
Those references let us match an incoming transfer to your account and settle disputes quickly. Without them we cannot confirm a payment belonged to you, which slows any correction you request.
While the account runs we keep its records. After closure we hold accounting and dispute entries for the period Pakistani rules require, then delete or anonymise the rest.
Yes. Your profile page lets you edit contact details, switch off promotional messages and download your account data. Removing the whole record needs a written request so we can confirm the account is yours.
Payment partners and fraud-checking services see only what they need to process a transfer or verify a login. We do not sell account data, and marketing partners receive aggregated figures only.
Write to our data desk with the dates and what you expected. We investigate, reply within the timelines local rules allow, and where we got it wrong we correct the record.