LEGAL REFERENCE

How lake 777 Handles Your Personal Data

This page explains what we collect when you open an account with us, and what we do with it afterwards. It covers the transaction records behind JazzCash, Easypaisa...

Plain-English wordingApplies to web and appPakistan account holdersData requests answeredCurrent policy wording
Jump into lobby Read FAQ
lake 777 How lake 777 Handles Your Personal Data

The Posture We Take With Your Records

We keep your account details only as long as we need them to run your account, and we say so plainly rather than burying it. Records tied to JazzCash, Easypaisa, SadaPay and Raast transactions are held for the periods Pakistani financial rules require, in encrypted storage, with access limited to staff who need them. Where local law permits, you can ask for

a copy of what we hold, ask us to correct it, or ask us to delete what we are not obliged to keep. Availability of some features differs across supported regions, so the wording here covers those differences instead of promising one global standard. We do not sell your personal data to third parties, and partners who handle it for us are

bound to that task alone.

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

PRIVACY DESK

Reaching Our Team About Your Data

If something in this policy does not match what you see on your account, tell us and we will go through it...

Live chat line Chat from your signed-in account and ask for...
Email request Write from the email tied to your account...
Help form in your account The help form inside your account sends your...
HOW WE CHECK

Who Checks This Policy Before It Ships

This text is written by the team that runs your account, then checked by our data and payments staff before it goes live. When a payment rail changes...

Drafted by account teams

The people handling sign-ups, payments and support write the first draft, so the wording reflects what actually happens when you...

Checked by data staff

A second pass measures each paragraph against our internal data map, confirming that every field named really is collected and...

Payments clauses verified

Our payments team goes through the clauses on JazzCash, Easypaisa, SadaPay and Raast so retention wording matches what those rails...

Version history kept

Each published version is dated and stored, which lets you see what changed between two revisions instead of guessing whether...

Plain-English passes

We rewrite phrasing that reads badly for account holders, then have the legal team confirm the shortened version carries the...

Change notices in account

When a revision affects your rights, a notice appears inside your account and stays visible for thirty days before the...

How This Page Lines Up With Our Other Policies

The privacy policy sits alongside our other policy pages, and the set is meant to be read together. Definitions, contact routes and retention windows are kept identical across...

Same definitions
Terms like account data, transaction record and device identifier carry one meaning across every policy page, so moving between them does not change what you are reading.
Matching contact routes
The support channels listed here are those on our terms and cookie pages too, so you never hunt for another address to raise a privacy point.
Aligned retention windows
Retention periods quoted in this policy match the figures used in our account terms for JazzCash, Easypaisa, SadaPay and Raast transaction records.
One shared date
When we revise one policy page we revise the shared date with it, so the set always shows how recently the whole group was updated.
Shared cookie wording
Where our cookie page describes how tracking is set, this page uses the same sentences rather than a second, contradictory explanation of the same practice.
Consistent jurisdiction lines
The phrase where local law permits appears identically wherever access, storage or deletion is limited by the rules of a supported region.
One policy for app and web
Our app and the web version share a single policy, so data handled on your phone is covered by the same paragraphs you are reading now.

What Stands Out on This Policy Page

We keep the layout of this policy deliberately flat: a short summary first, then the detailed clauses underneath it. Each heading answers one question, so you...

Summary rows first

The opening block gives you the short version, what we collect, why we need it and how long we keep it, before the clause-by-clause detail begins.

One heading per subject

Each section holds a single subject, so you can read about account access without working through unrelated storage paragraphs to find it.

Storage tables

Retention windows are listed in a simple table rather than buried in prose, which makes it quick to check how long a record type stays with us.

Contact block in a fixed spot

Support details sit in a block that repeats at the foot of every policy page, so they are in the same place whichever page you land on.

Phone-first reading

Type is set so it stays readable on a handset, since many of our Pakistan account holders open these pages on the same phone they use for the lobby.

Change markers

Revised paragraphs carry a small marker with the date they moved, so returning readers see what shifted without comparing the whole document.

Questions We Get About Your Data

We take what an account needs to run: your name, date of birth, contact details and verification documents. Transaction records from JazzCash, Easypaisa, SadaPay and Raast are added as you use it.

Only to processors that help us run the service, such as payment handlers and identity checks. They work under contract and cannot use your data for their own marketing.

Yes. Raise the request through live chat or the help form in your account and we send a copy of your stored data, subject to verification and any records we must keep.

Records tied to payments stay for the period Pakistani financial rules set, then come out. Account activity that is not tied to a payment is held for a shorter window.

Files are encrypted in storage and in transit, and access is limited to staff whose role needs it. Sign-in activity is logged so unusual access can be spotted early.

We revise it when our operations or local rules change. Material changes appear as a notice inside your account, and the page date moves each time a new version goes live.