Shared Definitions
Where this text says account data, our terms page means the same fields. One glossary feeds every policy page, so you are not translating between documents when you compare them.
This page sets out how 777me collects, stores and uses the personal details you give us when you open an account, verify your identity and move money through...
777me operates under the rules that apply in each supported region, so the way we treat your details can shift slightly between markets. In Pakistan, account records are held for the periods Pakistani law requires, and access is limited to staff who need it for verification, payment checks or dispute handling. We collect what an account needs: your name, date of birth,
mobile number, email, device signals and the transaction trail created by JazzCash, Easypaisa, SadaPay and Raast transfers. We do not sell that data. Where local law permits, you can ask us to correct or delete details no longer needed for legal, accounting or fraud-prevention purposes. Where two sets of requirements differ, we follow the stricter one, and the wording here changes only
when that rule changes.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Questions about your records go to a small team that handles account and privacy requests, not a general queue. We answer through live chat inside your account and by email at [email protected], and most replies land within 24 hours.
Open your account and tap the chat bubble to reach the privacy desk. Sessions run 09:00 to 01:00 Pakistan time daily, and every request gets a reference number.
Write to [email protected] with your registered mobile number and a short description of the change you want. Attach screenshots of JazzCash, Easypaisa, SadaPay or Raast confirmations where a payment record is involved.
Simple record updates are handled the same day. Requests touching payment history or account closure take up to five working days, because we confirm with the payment provider first.
We keep this document accurate by tying every clause to something we can show you: encryption standards, staff access logs, retention windows and the exact fields our forms collect. When a payment...
Each paragraph carries an internal owner from our operations side, so you know a real team signs off on the wording rather than a borrowed template. Contact addresses here stay current.
Every change to this text is dated and listed in a short changelog at the foot of the page, so you can see which clause moved rather than guessing.
Policy detail covers the rails you actually use. JazzCash and Easypaisa wallet references, SadaPay card trails and Raast bank confirmations each carry their own retention and sharing rules inside this document.
Account pages run over encrypted connections, sensitive fields stay masked in our back office, and staff access is granted case by case. We describe those measures in the same terms our engineers use.
Legal text only helps if you finish reading it. We keep sentences short, define jargon the first time it appears, and link related clauses so one paragraph answers most of what you came for.
If something here looks out of step with how the platform behaves, write to [email protected] and we will correct the page or explain why the wording stands.
Our terms, payment pages and privacy text follow one set of definitions, so the same phrase means the same thing wherever you read it. If a clause here points to another document...
Where this text says account data, our terms page means the same fields. One glossary feeds every policy page, so you are not translating between documents when you compare them.
Retention windows quoted on the payment pages match the numbers used here. If a rail's record-keeping period shifts, both pages change in a single release, and the changelog records it.
Request routes stay identical: live chat inside your account, and [email protected] by email. Support pages point to those same two channels, with no extra addresses for you to memorise.
JazzCash, Easypaisa, SadaPay and Raast are spelled the same way across our pages, so a search for a payment term returns both the privacy clause and the payment text.
Encryption and access-control sentences come from one shared block, so the security paragraph here reads the same as the one in our account-access text. No page softens those commitments.
This document and its siblings carry the same revision date whenever a shared clause changes. You can track a single date instead of checking each page separately before relying on a rule.
The supported-regions wording at the head of each policy page comes from the same legal clause, so nothing contradicts another page about where our terms apply in practice.
The document is arranged the way people look for answers: a summary of the data we hold, the sharing rules, the retention windows, and the controls you can...