Next To The Terms
The terms page covers how your account is governed; this page covers the data behind it. Where both mention age checks, the wording matches word for word, so nothing contradicts.
LEGAL REFERENCE
How 777co Handles Your Account Data
This page sets out what 777co collects, why we collect it, and the choices you hold over it. From your first JazzCash or Easypaisa payment to a final...
Data You ControlLocal Payment RecordsAccount Login SecurityPolicy Version Dates
Policy Posture Where Local Law Permits
777co runs as a policy-led platform: what we may collect, store and share depends on the rules that apply where you are. Register from a supported region in Pakistan and we hold your identity records, transaction history and device data so we can run your account and settle disputes. Where local law permits, you can ask to see, correct or remove the
personal details we keep, and those requests come through the support channels listed below. We do not sell personal data. Payment references from JazzCash, Easypaisa, SadaPay and Raast are stored as proof of settlement, and access inside our team stays limited to the people who need it to verify a transfer. When a rule changes, we update this page and email registered
accounts before the change takes effect.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
REACHING OUR DESK
Ways To Reach Our Privacy Desk
Questions about your data go to real people, not an automated queue. Our privacy desk runs every day from 09:00 to 01:00 Pakistan time, and every request touching your account records gets a ticket number you can follow. Write in English or Urdu, whichever suits you.
Team online
In-App Chat
Live chat sits inside your dashboard, so you can raise a data question while your account is open. Agents pull up your ticket history and route anything complex to our privacy team.
Email Requests
Write to our privacy mailbox for access, correction or deletion requests. Include the email address linked to your profile so we can verify ownership, and we reply within a few working days.
Account Settings
Update contact details, language and notification choices yourself from your profile page. Changes save instantly and appear in your account history, so you always hold a record of what was altered.
HOW WE DRAFT
How This Policy Gets Written
We revisit this page whenever we add a payment route, a new studio or a change to how logins work. A named data-protection contact signs off each update, a version number sits...
Named Data Contact
One accountable officer owns this policy, not a committee. The role is listed in our footer, and letters sent to that address reach a monitored mailbox rather than a general enquiry queue.
Plain Language Drafting
Every clause is written so someone without a legal background can follow it. Where a term carries a specific meaning, we define it in the same paragraph instead of a separate glossary.
Version History Kept
Each rewrite gets a date and a short changelog. You can open any previous version, which matters when you want to see what the policy said on the day you registered.
Testing Before Launch
When a policy change touches consent screens or cookie banners, it goes through the same release checks as any product change, on phones and larger screens before it reaches registered accounts.
Third Parties Listed
Payment processors, analytics vendors and cloud providers are named by category, with what each one receives. You never have to guess which outside company sees a transaction reference or a device identifier.
Staff Access Logged
Internal tools record which teammate opened an account file and when. That log is spot-checked monthly, and access without a linked ticket reaches the data contact within the same week.
CROSS-PAGE MATCH
Consistency Across Our Policy Pages
Our privacy page sits beside the terms, cookie and complaints pages, and the same wording runs across all of them. If privacy says we keep a payment reference for a set period...
Matching Cookie Text
Cookie categories on the consent banner use the same labels as the table on this page, so a toggle you switch off here is the one the banner lists.
Payment Clause Aligned
Our payment page shows what JazzCash, Easypaisa, SadaPay and Raast transfers cost; this page explains what we record from those transfers and why we keep it. Both are written by the same team.
Complaint Route Shared
If a data question turns into a formal complaint, it follows the same escalation path published on our complaints page, with the same response windows applied to each stage.
Support Hours Match
The contact hours printed here are the contact hours you get in the app, so you are not reading a schedule that only applies to one channel. Chat, email and profile settings share it.
Same Version Number
Every sibling page carries the revision date you see on this one. When we publish a change, all of them update on the same day rather than drifting apart over weeks.
One Shared Glossary
Defined terms such as personal data, processing and retention mean the same thing on every page in this set, so you can move between them without relearning the vocabulary.
What You See On This Policy Page
The layout you are reading is deliberate. A short summary opens the page, the full clauses sit under clear headings, and every data category links to...
Summary Box
The box near the opening lists the data categories we hold in plain bullets. Each bullet links down to the full clause, so you can skim the shape of the policy before reading any detail.
Pinned Contents
A contents rail stays fixed as you scroll, letting you move between collection, sharing and retention clauses on a phone without losing the heading you came from. It collapses neatly on small screens.
Plain Headings
Each clause heading states the subject in ordinary words, so a section about device data is titled that way rather than hidden behind a legal label you have to decode.
Consent Switches
Optional uses sit behind switches you control from your profile. Essential processing is listed separately and marked clearly, so you can tell an opt-in from something your account cannot run without.
Retention Table
A small table pairs each record type with how long we keep it, from identity documents to chat transcripts, and states what happens once that period ends. It is dated too.
Language Switcher
The page renders in English for Pakistan by default, with Urdu available for the summary and support sections, so households that read either language can follow the same rules.
Privacy Questions We Get Often
Your name, date of birth, contact details and the identity document you upload, plus the device and network signals that help us confirm you are the person logging in.
We keep the transfer reference, amount and timestamp so a withdrawal can be matched to its source. We never hold your wallet PIN or your full card number on our systems.
Open accounts keep records while they are active. After closure we retain what regulators require for the applicable period, then delete or anonymise the rest, as set out in our retention table.
Yes. Write from the email address on your profile and we will send an export covering your identity details, transaction history, login records and support conversations within a few working days.
Support agents handling your ticket, the payments team verifying a transfer, and compliance staff checking a case. Each lookup is tied to a ticket and logged, with monthly spot checks.
Only what is needed to clear a transfer or confirm a withdrawal, such as the reference and the account name you registered. Processors work under contract, and we do not sell personal data.