Shared definitions
Words such as profile, transfer reference and device record carry one meaning across every policy page, so you are never left guessing whether two clauses describe the same thing.
Everything 7f777 org collects when you open an account is set out below in plain English: profile fields, your JazzCash, Easypaisa, SadaPay and Raast references, and the device...
This policy is the rulebook we work from, not a page we file away. When you register from Pakistan, we collect only what is needed to confirm who you are, clear JazzCash, Easypaisa, SadaPay, NayaPay and Raast transfers, and keep the lobby running. Where local law permits, identity documents stay with our verification partners under written contract, and transfer references are held
for as long as our accountants and the authorities require. Supported regions differ in what may be retained; where a province asks for a shorter period, the shorter period wins. You can request a copy of what we hold, ask for corrections, or close the account, minus anything we are still bound to keep. We never sell your data.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Questions about your file do not need to sit unanswered. Our support desk runs every day and can walk you through what we hold, why we hold it, and how to have it changed or removed. Most requests are logged the day they arrive, with a reference number to follow.
Open a chat from your signed-in account and ask for a data copy, a correction or a deletion. Our team pulls the record while you wait and confirms it in writing.
Write to our privacy address with your account reference and the change you want. We reply in writing, usually the next working day, and explain anything that cannot be altered.
Ask us to close your profile and we remove the personal fields, keeping only the transaction references our accountants must retain. Confirmation arrives once the removal is done.
The wording here is drafted by the compliance and platform teams who run 7f777 org day to day, then checked line by line against what our systems actually do. When a feature...
Every clause is drafted by the people who run sign-up, cashier flows and live tables, so the wording matches the systems you actually touch when you open your profile.
Before a policy change ships, our engineers confirm each statement against the live build, then sign off. A clause that cannot be traced to a real setting is rewritten.
Each update carries the date it took effect and a short summary of what moved. You can compare the current wording with the earlier version at any time from your account settings.
Our advisors in Pakistan read the page against federal and provincial rules before publication. Where a province sets a shorter retention window, that limit is written into the clause itself.
Legal drafts are translated into everyday Pakistani English before they appear here. A sentence that needs a second reading goes back to the drafting team until it reads clearly the first time.
Spotted something that no longer matches your experience? Report it through support and we log it as a defect with a deadline, then tell you which wording changed and why.
The rules you read here also shape the other pages on 7f777 org. Our terms, cookie notice and account-opening pages share the same definitions, so a phrase means the same thing wherever...
Words such as profile, transfer reference and device record carry one meaning across every policy page, so you are never left guessing whether two clauses describe the same thing.
The retention windows quoted in this document line up with the account terms and the cashier pages, so the period we keep JazzCash or Easypaisa references is stated the same way.
The cookie notice lists the same tracking categories described here, so if a clause names analytics or fraud prevention, you can find the matching entry on that page without hunting.
Data requests, corrections and closures all run through one support queue, whichever page you arrived from. Your reference number works across every document and the reply comes from the same team.
When one policy page changes, we check the others that share its wording and revise them together, so you are not reading an old clause on a page updated last season.
Supported regions and local law phrasing are handled identically across the site, so when you move from the cashier terms to this document the jurisdiction language reads the same way.
Nothing material lives only in one document. If a rule affects your account, it appears on the page that governs that feature and is cross-referenced here rather than buried in a footnote.
This document is built as labelled blocks rather than one wall of text, so you can jump straight to the part you need. Each block carries...
A fixed strip down the side lists every clause heading, so you can jump from the opening paragraph to retention windows without losing the part you were reading.
A date stamp near the headline shows the day the current wording took force. When we revise a clause that date shifts and the change is flagged beside the affected paragraph.
Longer clauses sit behind a tap-to-open panel, so the page stays scannable on a phone. Open the ones that matter to you and skip the rest until later.
Every technical clause is followed by a short box that restates the same rule in ordinary language. If the two ever disagree, the longer legal wording is the one that governs.
The document loads in Pakistani English by default, and you can switch the interface language without leaving the clause you were reading. Your choice is remembered on the device.
A save button exports the whole document as a single file you can keep, which helps if you want a record of the wording that applied on the day you opened your account.