How 777dc Handles Your Personal Data
Your 777dc account runs on data we collect only to verify you, protect your session and move money through JazzCash, Easypaisa, SadaPay and Raast. This policy sets out...
What This Policy Covers and Where It Applies
777dc applies this policy to every account opened from Pakistan and to supported regions where local law permits us to operate. It covers the personal details you give at sign-up, the device and session data our systems log, and the transaction records created when you move money through JazzCash, Easypaisa, SadaPay, NayaPay or Raast. Where you ask us to delete data, we
action that request except for records we must retain under financial or anti-fraud rules. Where a question sits outside this policy — payout timing, table rules, market lists — we point you to the matching page instead of stretching this one. We name the categories we hold rather than hiding them behind broad wording, and we keep the same definitions across every
language version we publish, so a Pakistani reader and a reader abroad see identical commitments.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Ways to Raise a Privacy Question
When something in this policy needs clarifying, our support desk handles it directly rather than routing you through a bot loop. We answer account-data questions, deletion requests and access requests from the same queue, and we log every ticket so nothing quietly disappears. Live chat runs while our team is on shift; email stays open around the clock for anything longer.
Live chat
Open live chat from your account dashboard between 9am and 1am Pakistan time; a privacy-trained agent picks up your data question within minutes and saves the reference to your history.
Email support
Write to our privacy team at any hour and we reply within two working days, quoting the account details you gave so your thread stays on record.
Account settings
Use the data panel inside your account to request a copy of what we hold, correct your details or close the profile without emailing anyone. The request lands in the same queue our agents work.
The People Behind Our Data Commitments
This policy is drafted by the same operations and compliance staff who build the account flow, not by an outside agency. Every revision is dated and published on this page so you...
Operations desk
Our in-house operations team drafts each clause, checking it against the way accounts, verification and wallet activity actually run on 777dc every day, from first sign-up to final account closure.
Compliance sign-off
A compliance officer reads every revision before it goes live and confirms the wording matches the rules we follow in Pakistan and in supported regions where local law permits.
Revision log
Each update carries a date and a short line on what changed, so you can track how our handling of personal records has shifted from one version to the next.
Plain-English pass
Before publishing we strip out legal shorthand and rewrite anything a reader in Lahore or Karachi would have to read twice, keeping the meaning and the same commitments intact.
Data map
We publish a short list of the data categories we hold, from phone numbers and wallet references to device logs, instead of describing everything as broad account data.
Region wording
Clauses that differ by market are flagged individually, so you can see which commitments apply to Pakistan accounts and which apply to supported regions where local law permits us to operate.
How This Policy Matches Our Other Pages
This policy is written to sit beside our other legal pages without contradicting them. Where a term shows up in two places, we use the same definition, the...
| Terms of Service | The account contract and this policy share one definition list, so the words we use for your profile, wallet and records mean the same thing on both pages. |
|---|---|
| Cookie Notice | Tracking choices you set in the cookie panel feed straight into this policy, and switching a category off changes what we log from the next page load onward. |
| Payout Page | Retention wording here matches the payout page: transaction records stay for the period financial rules require, and nothing extra is stored beyond that window. |
| Verification Steps | The documents you upload during checks are described the same way here as on our verification page, including which copies we remove once approval is granted. |
| Sportsbook Rules | Market and settlement rules sit on their own page, while this policy explains only how the activity behind them is recorded against your account. |
| Language Versions | Every translated version of this policy carries identical commitments, and where wording differs we default to the English text published on this page for clarity. |
| Contact Page | Addresses, chat hours and the ticket queue named on our contact page are the same ones used for privacy requests, so there is one route to remember. |
What You Will Find Across This Policy
This page is built so you can find a clause without reading it end to end. A summary strip opens it up, the full wording follows...
Summary strip
Four lines at the start of the page tell you what we collect, why we hold it and how to remove it, before any clause-by-clause reading begins.
Data table
A plain table lists each category we hold, the reason we keep it and the retention window, so you can scan the whole picture in under a minute.
Jurisdiction block
A short block names the markets this policy covers and repeats the wording that applies only to supported regions where local law permits us to operate.
Cookie panel
The cookie panel sits inside the page rather than a separate window, letting you switch analytics and preference tracking on or off without leaving the text.
Deletion steps
A numbered sequence shows how to request removal of your data, what we keep for financial rules and how long each step usually takes to complete.
Change log
Every amendment to this policy is listed with its date, so you can compare versions and see exactly which clause was rewritten and when.