LEGAL REFERENCE

How 777ph Handles Your Account Data

777ph sets out exactly what we collect when you open an account, from contact details to the JazzCash, Easypaisa, SadaPay or Raast reference behind a top-up, and how...

Account data mapCookie choicesRetention windowsEdit requests
Explore the lobby Read FAQ
777ph How 777ph Handles Your Account Data

Data Rules That Follow Your Region

Because you reach 777ph from Pakistan, how we process personal data depends on where you are, and we only offer account access where local law permits. Where a supported region sets extra requirements, we follow that region's rules rather than a single global standard. The details behind a JazzCash, Easypaisa, SadaPay or Raast transfer, your device fingerprint and your session logs are

handled under the strictest standard that applies to you. If a rule changes in your area, we date the update near the start of this page rather than editing quietly. Ask our support desk if a rule for your city matters to you.

Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.

REACH THE DESK

Ways To Reach Our Privacy Desk

Privacy questions rarely wait, so we run three routes to the desk that actually handles your file. Each request is logged against your account and answered by someone who can see your stored data, not by a script reader working from a template.

Team online

Live Chat Desk

Reach our privacy desk through live chat from inside your account, seven days a week, and ask about stored data, cookie settings or a correction request without emailing anyone.

Account Inbox

Send a written request from the email address tied to your 777ph account so we can match it to the right profile and answer inside our published reply window.

Data Requests

Ask us to copy, correct or delete the personal details on file, and we will confirm what was actioned, what is still stored and why any part has to remain.

HOW WE CHECK

How This Page Earns Its Keep

A small policy team inside 777ph owns this page, checks each claim against our live systems and republishes the text when something stops being accurate. We would rather show you how a...

Policy Owner

A named team inside 777ph writes and maintains this privacy page, checks every claim against our live systems and republishes the text instead of quietly editing it later.

Data Inventory

We group what we hold into four buckets: contact details, payment references, device signals and session logs, with one named owner and one deletion rule written beside each bucket.

Plain Language

Every clause is rewritten into short en-PK English with the formal wording kept beside it, so you can read the operational meaning before you reach the legal phrasing.

Local Rails Named

When we describe payment data we name the rails you actually use, JazzCash, Easypaisa, SadaPay and Raast, so you know which reference numbers can appear against your account.

Change Log

Each update to this page carries a date and a line on what moved, so a returning reader can spot a changed cookie rule or a shorter retention window at once.

Written Checks

Before publishing we test the wording against how our support desk and payment systems actually behave, so this page describes real practice rather than an idealised version of it.

One Set Of Rules, Every Document

Your account touches several documents, and they should not contradict each other. We keep this privacy page, the account terms and the payment screens aligned, so a rule...

Terms Consistency
The account rules you accept when you open your profile use the same defined terms as this page, so a word such as retention carries one meaning across every document.
Cookie Settings
Cookie choices you set here carry across the lobby, the sportsbook and the payment screens, so you are not asked to make the same decision twice in one visit.
Payment Screens
Where a payment screen mentions JazzCash, Easypaisa, SadaPay or Raast, the description matches what this page says we store, including reference numbers, timestamps and the agent wallet used.
Account Security
Login steps, device confirmation and password rules are described the same way on the security page and here, so nothing contradicts when you enable a new device or sign in from another city.
Complaint Route
If you raise a data complaint, the escalation path on this page is the one your support thread follows, with the same reply windows quoted in both places.
Verification Steps
Document checks that confirm your name and age before a withdrawal follow one published list, and this privacy page points to that list rather than describing a separate process.
Revision Dates
Every sibling page carries the same revision stamp as this policy, so you can tell at a glance which documents were refreshed together and which ones are trailing behind.

What You Can See On This Page

Everything you need to act on sits on this one page instead of a downloadable PDF. We built the layout around the questions our support desk...

Summary Strip

A short strip near the start of this page names the four things most readers want: what we collect, why we hold it and how to ask for removal.

Data Table

A single table names each data group beside its purpose and retention window, so you can read down one column and understand the whole account without jumping between paragraphs.

Control Shortcuts

Shortcuts beside the text open the account screens where cookie choices, marketing consent and stored contact details can be switched or edited by you without raising a ticket.

Desk Hours Block

The contact panel states when the privacy desk is staffed, which languages it answers in, and how long a routine data request takes from receipt to written reply.

Glossary Glosses

Terms such as controller, processor and retention period get a one-line gloss in plain English, so you never have to leave the page to decode a contract clause.

Update Banner

When something material changes, a dated banner sits near the start of the page for thirty days, and the previous wording stays reachable from the same archive link.

Privacy Questions We Get Asked Weekly

We collect your email, phone number, name, date of birth and country, plus the device signals and session logs created when you sign in, and a reference for any transfer you make.

No. Passwords are stored as salted hashes that cannot be reversed, and any wallet PIN you enter is handled by the provider, JazzCash, Easypaisa, SadaPay or Raast, never by our servers.

Contact details stay while your account is open and for the period local rules require afterwards; payment references are held longer where financial record-keeping rules apply, while session logs are kept for a shorter window.

You can request deletion from your account or through live chat at any time. We remove what no longer has a legal purpose and tell you plainly which records must stay on file and why.

Open the contact preferences screen in your account and clear the marketing boxes. The change applies at once, while essential messages about logins, withdrawals and policy updates keep reaching you.

Each revision is dated and published near the start. If a change affects how your stored data is used, we message you inside the account before the new wording takes effect.