Privacy Policy
This page is the master document. It names the data categories we hold at mc777, the purpose behind each and the retention period that applies to every record type.
LEGAL REFERENCE
How mc777 Handles Your Account Data
Open your account and this privacy policy tells you plainly what mc777 records, why every field is held, and how references from JazzCash, Easypaisa, SadaPay and Raast move...
What we collectWhy we keep itWho we share withHow long it staysHow you change it
What This Privacy Policy Actually Covers
This privacy policy explains the data practices behind every mc777 account opened in Pakistan or in a supported region where local law permits us to operate. We describe the categories we collect, including registration details, device and connection data, chat transcripts with our support desk, and the transaction references created when money moves through JazzCash, Easypaisa, SadaPay, NayaPay or Raast, and we
state the purpose each category serves. We also set out how long records are kept, which processors handle them on our behalf, and the rights you can exercise from inside your account. Where local law sets a different standard, that standard governs your account rather than the general wording here, and we revise the clause when a market's rules change.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
BEHIND THE TEXT
Who Writes And Maintains This Page
A small in-house team owns this page: our data protection contact, our security lead and two writers who turn legal drafting into sentences you can read once. Every edit carries a date...
Data Protection Contact
One named contact owns every privacy question on this page. When you write in, that person or their deputy replies with a reference you can follow up later.
Change Log Discipline
Each amendment gets a version number, a date stamp and a one-line reason. You can open the log and trace any clause back to the day it moved.
Local Law Checking
Our compliance contact maps each clause against the rules that apply where you hold your account. Where a market needs a stricter line, we write that line into the policy itself.
Plain English Editing
Two writers rework every legal draft so it reads like a conversation, not a contract. Long clauses get split, jargon goes, and anything ambiguous returns to the legal owner.
Security Team Input
Engineers who run our account systems check the technical claims before they go live. Where we mention encryption or access logs, the wording matches what the platform does.
Reader Feedback Loop
When the same question arrives from several account holders, the support desk flags the clause and we redraft it. Confusion reports carry the same weight as legal updates.
SIDE BY SIDE
How This Page Sits With Our Others
Our other policy pages answer narrower questions, and this one links straight to each of them instead of repeating their wording. Read them together and you have the full picture of how...
Cookie Policy
The cookie page handles browser storage only: which tags we set, what each one remembers and how you switch them off from your browser or the account settings panel.
Terms Of Use
The terms page covers the account contract: who may hold an account, what behaviour breaks the agreement, and how a closure is handled when either side ends it.
Payment Terms
Payment terms explain clearing times for JazzCash, Easypaisa, SadaPay, NayaPay and Raast transfers made in Pakistan, plus the reference number on your statement and what to do if one stalls.
Retention Schedule
The retention schedule lists every record class with the period we keep it, the legal reason for that period, and whether it is then deleted, anonymised or archived.
Security Notice
The security page describes how sign-in, device checks and password resets work, plus what our team will never ask you for when they contact you about your account.
Closure And Deletion
The closure page covers ending an account, exporting your records first, and confirming afterwards what was deleted, what was kept and why each kept item stayed in our archive.
The Blocks That Shape This Page
Every block on this page has a job. The summary cards sit above the long clauses so a quick read answers the question you arrived with...
Sticky Section Menu
A fixed menu follows you down the page, so you can jump from the summary to retention, sharing or your rights without scrolling through clauses you already read.
Date Stamp In Header
The version date sits beside the policy number on the first screen. If that date has moved since your last visit, read the change log before assuming the old wording holds.
Plain Summary Cards
Short cards open each major clause with a one-paragraph version in everyday English. They do not replace the full text, but they show you when to read further.
Jurisdiction Line
One line near the start states which market's rules apply to your account. It saves you reading three paragraphs to work out whether this page covers you at all.
Record Table
A single table lists each record type, the reason we hold it and the period it stays. Row names match the ones our support team uses when you ask about a record.
Contact Strip
The page closes with the three ways to reach the privacy desk, repeated from the support block above, each with an average reply time so you know what to expect.
Questions We Get About Your Data
Your name, date of birth, contact number and email, plus the address you register. We also store device data, sign-in records and reference numbers returned by JazzCash, Easypaisa or Raast with your transfers.
No. We share records only with processors that run parts of the platform for us, such as payment partners and identity checks, and those categories are named in the sharing clause.
While your account is open we keep records current. After closure we hold transaction and identity entries for the period local rules require, then delete or anonymise everything else.
Yes. Use the privacy panel in your account or write to the records desk. We send a readable summary, usually within a few working days, naming each field and where it came from.
Closure starts the retention clock rather than wiping everything at once. We export your records on request, stop all messaging, and keep only the entries local rules require us to hold.
Every change carries a version number and a date stamp in the header. Material changes are also flagged inside your account the next time you sign in.