What We Collect and Why We Keep It
This page sets out what 777six collects from your account and why we keep it. It covers the details you hand over at sign-up, the records that arrive...
Where Local Law Permits, Your Data Stays Yours
This policy states our posture on personal data, and it is written to work where local law permits. When you open an account from Pakistan, we record the details you give at sign-up, the transfers you make through JazzCash, Easypaisa, SadaPay or Raast, and the device data that keeps your session secure. Some regions hold their own rules about what an operator
may keep and for how long, so where a local requirement is stricter than this page, the local requirement leads. We do not sell your personal data, and we share it only with the processors who help us run the platform. Ask us what we hold about you at any time and we will answer in writing.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Who Writes and Checks This Policy
Behind this page sits a small editorial routine. One writer owns the wording, a colleague from another team checks it against how our systems actually behave, and we re-read the whole document...
Named Policy Owner
One writer owns this document. They sit with the data team, so wording on retention and sharing reflects how our systems behave rather than a template borrowed from elsewhere.
Second Pair of Eyes
A colleague from another team reads each draft and challenges any line that cannot be traced back to a real process. If nobody can explain a clause, we cut it.
Revision Date Line
The date near the header shows when the wording last moved. We update it the same day we publish a change, so you never have to guess whether the page is current.
Plain-Language Edit
Before publishing we strip legal padding, shorten sentences that run past two lines, and replace vague phrasing with a direct statement of what actually happens to your data.
System Cross-Check
Each claim about collected data is matched against the live account database and the payment logs. If a field is described here but not stored, the description changes rather than the system.
Kept Change Log
We keep an internal log of every wording change with a short reason beside it. That log shows a new team member why a line reads the way it does.
How Our Policy Pages Stay Aligned
We keep the policy set on this domain moving together. When the privacy wording changes, the cookie notice, the account terms and the payment pages are checked in...
What You Will See on This Policy Page
Scan this page and you will notice a few deliberate choices. Every heading names its subject in ordinary words, every rule sits close to the example...
At-a-Glance Row
Short badges sit under the headline so you can see what the page covers before reading on. They name the data types, account areas and support route in a few words.
Rail Chip Bar
A row of chips names JazzCash, Easypaisa, SadaPay, NayaPay and Raast, so you can confirm your own rail is covered before scrolling into the longer clauses.
Short Clause Blocks
No clause runs longer than a short paragraph. Where a rule needs three conditions, we give it three sentences rather than one dense block you have to untangle.
Ordinary Headings
Headings say what each section contains in everyday words. Skim them and land on the part that matters to you, whether that is retention, sharing or making a request.
Date and Version
Every revision carries a date and a version marker near the header, so when you come back months later you can tell whether anything has changed since your last visit.
Jump Links
Links between our policy pages sit inside the copy, not only in the footer. Follow one and you land on the related clause instead of searching a menu for a document.