Privacy Policy For Your 777nz Account
Everything we collect, why we keep it and how long it stays is set out below in plain English, with no legal fog. Open your account and you...
How We Handle Your Account Data
Where you access 777nz from matters, so this policy is written to sit alongside the rules of your supported region. Where local law permits you to hold an account, the same data rules apply whether you signed up on a phone or a computer. We collect what you give us at sign-up — your name, contact number and the payment tag tied
to JazzCash, Easypaisa, SadaPay or Raast — plus the technical records our servers write each time you log in. That data verifies your account, settles payments and keeps the lobby running. We do not sell your records. Retention windows differ by record type, and you can ask us to erase anything we are not required to keep. Where the law of your
region demands something different, the stricter rule wins and we tell you which one applies.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Reach Our Privacy Team Directly
Data questions should not sit in a queue for days. Privacy requests arrive on the same channels you already use for account help, seven days a week from 9am to 2am Pakistan time. Write from the email address on your account and we match the request to a record in minutes rather than hours, with a written confirmation each time.
Live Chat
Open live chat from your dashboard and ask for the privacy desk. Agents pull your record, confirm what we hold and log a correction or erasure request in the same session.
Email Requests
Write from the address on your 777nz account and include your registered number. We confirm receipt and give you a clear timeline for the request.
WhatsApp Line
Message our Pakistan support line on WhatsApp for quick questions about JazzCash or Easypaisa transaction records. Larger jobs, such as a full data export, go to the privacy desk.
The People Behind This Policy
Policy pages often read like they were bought from a template. Ours is written by the same people who run account verification, payment settlement and the support desk you reach at midnight...
Written In-House
The wording comes from our own compliance and operations teams, not a bought template. When login record storage changes, the paragraph describing that storage changes with it.
Revised Every Quarter
We go through every clause four times a year and after any payment integration change, including JazzCash and Raast updates. Support can tell you which revision applies to your account.
Drafted By Operators
The people drafting this policy work on the systems it describes. They know how long a failed Easypaisa record stays live and how verification flags are cleared.
Built Around Pakistan
We serve Pakistan, so our practices account for local payment rails, mobile-first sign-ups and the network conditions you browse in. Wording copied from other regions rarely fits.
Nothing We Cannot Show
You will not find certification badges or partner names we cannot back up. Everything stated here is something we can show inside your dashboard or in a support reply.
Short Sentences Win
Legal text protects us, plain text protects you. Where a clause could be read two ways we rewrite it until it reads one way and keep the sentence short.
One Standard Across Every Policy Page
A privacy policy only counts if the rest of the site agrees with it. Our terms, cookie notice, payment pages and this document are kept in step, so...
| Terms And Conditions | The terms cover account rules; this policy covers the data behind them. Both are edited together, so clauses on verification, account closure and record keeping never drift apart. |
|---|---|
| Cookie Notice | The cookie notice lists each cookie by purpose, from login sessions to lobby preferences, and matches the storage windows described here for anything saved on your device. |
| Payment Pages | The JazzCash, Easypaisa, SadaPay and Raast pages state which records travel with a transaction. That mirrors the retention clauses here, so both places give the same answer. |
| Account Security Page | Login alerts, device history and two-step verification are described from a security angle there and a data angle here. Both draw on one internal specification. |
| Help Centre Replies | Support scripts are built from these clauses. When an agent quotes a retention period to you, that number comes from the same source as this page. |
| Mobile App Screens | In-app screens show a shortened version of the same points, covering what the app reads from your handset and what it sends back to our servers. |
| Change Log | Every revision is dated and summarised so you can see what moved and when. Earlier wording stays available for accounts opened under a previous version. |
What You Can See On This Page
This page is built to be read, not skipped. Instead of one wall of legal text it is split into short blocks you can scan on...
Sticky Contents Strip
A fixed menu follows you down the page and jumps to any clause, so you reach the retention rule or the sharing rule without scrolling past sections you already read.
Everyday Summaries
Each clause is paired with a one-line summary in everyday wording. The summary never replaces the clause, but it tells you what you are about to read.
Revision Date Shown
The date near the heading always reflects the live version. If it has moved since your last visit, the change log below shows which paragraph was edited.
Local Rail Cards
Cards for JazzCash, Easypaisa, SadaPay and Raast sit beside the clauses that mention them, so you can see which records each route creates.
Tap To Expand Clauses
Longer clauses collapse to a single line until you tap them, which keeps the page short on a handset while leaving the full wording available when you want it.
Save A Copy
You can download the current version from the footer. That file carries the revision date, so you always know which wording applied to your account.