Data Collection Scope
Defined here and referenced without contradiction in our Terms of Use, so you see the same collection scope in both documents.
At 77bit, your account data belongs to you — we collect only what we need to run your account, process your deposits via JazzCash, Easypaisa, SadaPay or Raast...
This privacy policy applies to every account opened on 77bit.win and covers all personal data submitted during registration, identity verification, and payment processing in supported regions where local law permits. When you fund your account through JazzCash or Easypaisa, we receive a transaction reference and your registered mobile number — nothing beyond what the payment provider shares to confirm settlement. SadaPay and
Raast transfers carry similar minimal metadata. We retain this data for as long as your account remains active or as required by the financial record-keeping obligations that apply to us. You may request a full export of your stored data at any time through our support channel.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
77bit keeps this policy current with each change to how we collect or process data. The six signals below reflect the concrete practices behind this document — not...
We review every clause in this policy at least once per year and publish an updated effective date whenever a...
Personal data tied to your 77bit account — including payment references from JazzCash and Easypaisa — is stored using AES-256...
We do not sell, rent, or trade your personal information to marketing agencies or data brokers. Any third-party sharing is...
We define how long each data category is kept. Payment records are held for the period required by applicable financial...
Our data handling procedures account for the payment rails Pakistani accounts use — JazzCash, Easypaisa, SadaPay and Raast — so...
You can request a copy of every data point we hold on your account. We fulfil verified access requests within...
Our privacy policy does not operate in isolation — it connects directly with our terms of use, cookie policy and account security practices. The table below shows how key privacy commitments are...
Defined here and referenced without contradiction in our Terms of Use, so you see the same collection scope in both documents.
JazzCash, Easypaisa, SadaPay and Raast transaction metadata treatment is described consistently in this policy and in the Payments section of our Terms.
Our Cookie Policy lists every cookie category in use; this privacy policy references that list rather than maintaining a separate, potentially conflicting inventory.
The deletion steps described here match exactly what the Account Settings panel executes, with no hidden retention not disclosed in this policy.
The no-sale commitment in this policy is echoed in our Terms of Use under the Data Sharing clause, giving you two consistent points of reference.
Retention timelines stated in this policy are the same figures our support team will quote if you ask directly — there are no internal schedules that differ from what is published here.
When this policy changes materially, the same update is flagged in the site footer and in your account notification feed, keeping all three surfaces in sync.
A privacy policy should give you real control, not just legal cover. These six elements define how 77bit has structured this document so you can act...
Every clause opens with a plain-English summary so you understand the point before reading the legal detail. No legalese without an explanation alongside it.
The policy is split into named sections you can jump to directly from the contents list at the top of the page, saving you from scrolling through irrelevant clauses.
Your stored data is exportable directly from the account Settings panel — no email required, no waiting for a manual response from the support team.
The effective date of the current policy version is shown at the top of the page and updated immediately whenever a material change is published.
Privacy requests go to a specific team address — not a general inbox — so data queries are handled by the people who manage account data, not routed through general support.
A summarised change log records what was amended in each policy revision so you can see exactly what shifted between the version you last read and the current one.