How no7777 Handles Your Account Data
Your account records stay under your control, and this page sets out how we collect, use and store them. Read through and you will see exactly what no7777...
The Rules Behind Your Account Records
We keep one policy for the whole brand, and it applies wherever you reach no7777 from a supported region. Where local law permits, we collect only what an account needs: your name, contact details, age confirmation, and the transaction records that follow your JazzCash or Easypaisa activity. We do not sell your details to data brokers. Pakistani rules, payment partner terms and
host-country requirements can each change how long we hold a record or who may act on your request. Where those rules differ, the stricter one governs. If a request cannot be met in full because a legal hold blocks it, we tell you which rule stopped it and what you can still change. Collect less, explain more, answer every request in writing.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Raising a Privacy Request With Us
One inbox handles everything that touches your records: access, corrections, deletion, and questions about a single transaction. Write from the email or phone number tied to your account so we can match you quickly, then say plainly what you want changed. We reply in writing, in the order requests arrive, in English or Urdu.
Account Inbox
Send access, correction or deletion requests from the email registered on your account. We confirm receipt inside one working day, then answer in writing once the record check closes.
Live Chat Desk
Use chat for quick questions about a data field or who touched a payment record. Longer requests get logged and passed to the team holding the file, so nothing rests on one chat session.
Payment Queries
If a JazzCash, Easypaisa, SadaPay or Raast entry looks wrong, give us the amount, time and reference. We trace it with the partner and fix our side of the log.
Who Writes and Checks This Policy
This page is written by the team that runs no7777, not by an outside agency. Our compliance and support staff draft each clause, then a second checker inspects it against how the...
Drafted In House
Drafted in house by staff who run the platform daily. What you read here matches what the systems do, because no outside agency writes our data wording for us.
Two-Person Check
A second pair of eyes signs off each version before it goes live, comparing the wording against configuration screens, payment partner requirements and the scripts our support agents follow on calls.
Change Log Kept
We date every revision and keep earlier wording on file. If you asked a question under an older version, we answer against the clause that applied at the time.
Plain English First
Legal phrasing is rewritten into everyday sentences before publishing, in English for Pakistan readers. If a clause still needs a lawyer to decode it, we redraft until it does not.
Rails Named Openly
JazzCash, Easypaisa, SadaPay, NayaPay and Raast are named outright, so you can see which partner touches a transaction record and what data each one returns to us afterwards.
Region Realism
Access is described as it works in supported regions rather than pretending one rule covers every country. Where local law permits is the wording we use, because it stays true.
How This Page Matches Our Others
Privacy sits beside our terms, cookie wording and account rules, and all four pages share the same definitions. A term that means one thing here means the same...
| Shared Definitions | Account data, payment partner and supported region carry one meaning across this page, the terms and the cookie wording. No term is defined twice with different senses here. |
|---|---|
| Same Check Cycle | The privacy wording, terms and cookie page are checked on the same schedule by the same two staff members. A shift in one triggers a read-through of the others. |
| Consistent Contact Path | The support inbox, chat desk and payment query route listed here are the same on every other page. You never hunt for a different address depending on the clause. |
| One Retention Table | Holding periods for records appear in the same units everywhere. If the terms mention a span for transaction logs, the privacy wording repeats it exactly instead of rounding it. |
| Aligned Naming | JazzCash, Easypaisa, SadaPay, NayaPay and Raast keep the same spelling and the same role on each page, so a partner named in a clause is the one you picked. |
| Matching Region Wording | Where local law permits appears on every policy page with one meaning. Access and record handling follow the rules of the region you are in, not a single global set. |
| Version Dates In Step | Each page carries its own revision date, and shared wording updates land together. If the dates drift apart, that marks a page-specific change rather than a contradiction between them. |
Visible Building Blocks of This Page
The page is built from blocks you can scan in seconds: a summary at the start, a detailed stance, the routes for asking questions, and answers at the...