Privacy vs Account Terms
Our account terms explain what you agree to when you register, while this page explains what we do with the details you give us. Where the two touch, this policy sets the standard.
LEGAL REFERENCE
How We Handle Your Account Details
This privacy policy explains, in plain language, what we record when you open an account with 777sb, what we do with it and the choices open to you...
Plain-language clausesCookie choicesData request panelPakistan payment rails
What We Record and Why We Hold It
When you register from Pakistan, we collect the details needed to run your account: your name, date of birth, contact number and email, plus the verification records we are required to keep where local law permits. Payment references from JazzCash, Easypaisa, SadaPay, Raast and NayaPay are stored so a transfer can be matched to your account if something goes wrong. Device and
session data — browser type, approximate region, login times — help us spot unusual activity on your account. We keep this to run the service, meet record-keeping duties and answer you when you ask. Access is restricted to staff who need it for support or fraud checks. We do not sell your details, and we share only with processors who help us
operate in supported regions.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
HOW WE WORK
The Standards Behind This Policy
The people who maintain this page are the same team who run account security, payment reconciliation and support at 777sb, so the wording reflects how the platform actually behaves. We date every...
Version Dates We Publish
Every revision of this privacy policy carries a date. You can see when a clause last changed, and we keep earlier versions so you can compare what applied to your account at any point.
Named Contacts, Not a Black Box
Questions about your records go to a named team, not a generic inbox. Staff can see the same account tools you use, so a payment or login question gets settled without repeating yourself.
Security Practices We Follow
Account sessions are encrypted in transit, and access to your records inside our systems is logged and audited. Staff see the minimum needed, and internal access is revoked the moment a role changes.
Local Rails We Reconcile
JazzCash, Easypaisa, SadaPay, Raast and NayaPay transfers are matched to your account using the reference your provider issues. We store that reference so a delayed transfer can be traced without you digging through messages.
Plain Language Over Legalese
Clauses here are written so you can act on them. Where a legal duty forces specific wording, we keep the required sentence and add a short line underneath explaining what it means for your account.
Corrections We Make Openly
If a mistake appears on this page, we correct it and say what was amended rather than editing silently. That habit keeps the text honest and signals that what you read matches what we practice.
ACROSS OUR PAGES
How This Policy Sits With Our Other Pages
This page covers privacy only. Our terms page deals with account rules, our payments page explains how transfers are handled, and our help area answers everyday questions. Read them together and you...
Privacy vs Payments
Our payments page sets out which rails we support and how long a transfer takes. This page covers the references we store and when a JazzCash or Raast reference is matched to your account.
Privacy vs Help Articles
Help articles explain everyday tasks like resetting a password or checking a withdrawal status. They link back here whenever a task touches personal data, so you land on the governing clause.
Consistency of Dates
Whenever a related page changes, we check this privacy policy the same day. That way the date in the header here and the dates on our terms pages do not drift apart.
Same Contact, Any Page
You do not need to find the right form for the right page. Whether your question starts on our terms page or in a help article, we route data questions to the team behind this policy.
One Set of Definitions
Terms such as account data, session record and payment reference mean the same thing on every page we publish. We keep a shared wording list, so a phrase you learn here reads identically in our terms.
Where This Page Wins
If a summary elsewhere on the site ever conflicts with a clause written here, this policy takes precedence for everything about your personal data. That rule exists so you are never left guessing.
Elements You Will See On This Page
Everything you need to act on this privacy policy is visible without hunting through a menu. The header shows when we last revised the text, the...
Revision Date Strip
A dated strip runs under the headline so you can tell at a glance whether you are reading a current version, and we refresh it the moment a clause changes.
Anchor Link Row
Short anchor links sit near the opening so you can move straight to the clause on payments, cookies or retention. If a JazzCash reference is what interests you, two clicks take you there.
Cookie Choice Controls
A preferences control lets you accept or refuse non-essential cookies and change your mind later. Your selection is stored against your account, so the question is not repeated at every sign-in.
Data Request Panel
One short panel collects what you need: a copy of your records, a correction, or removal where the law allows it. You get a reference number to quote in any follow-up.
Contact Block
Email and live chat details sit in one block, with the hours our desk is staffed in Pakistan time. That is the fastest route if a clause here raises a question before you register.
Region Notice Banner
A short banner states where the service is offered and reminds you that access depends on local rules in supported regions. The wording stays the same across the site.
Questions We Hear About Your Records
Your registration details, verification records, payment references from the rails you use, and a log of logins and device data. That mix lets us run your account, confirm a transfer and flag activity you did not authorise.
We keep the reference number and amount attached to a transfer so it can be matched to your account. We do not store your provider PIN, and staff see the reference only when a delay is investigated.
Verification and payment records stay for the period local rules require, because we must account for transactions long after they settle. Session and device logs are held for a much shorter window.
Yes. Send a request from the email address registered to your account and we compile what we hold, explain anything unusual and send it to you in a readable format.
Tell the support desk which detail is incorrect and attach any document that supports the change. We update the record once it checks out and confirm in writing, so you hold a dated record.
Only with processors that help us operate — payment handling, identity checks, fraud screening and hosting — and only the records each one needs. We do not sell your data to advertisers.