LEGAL REFERENCE

How 777zp Handles Your Account Data

This page sets out what 777zp collects when you open an account, why we hold it and how you stay in control of it. From your first JazzCash...

Data use explained in plain EnglishControls you can change yourselfSupport replies within one working dayApplies in supported regions only
777zp How 777zp Handles Your Account Data

Where This Privacy Policy Applies

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

REACHING OUR TEAM

Contacting Us About Your Data

Data questions land with the same desk that handles your payments, so whoever replies can already see your account context. We answer...

Live chat Open live chat from inside your account and...
Privacy inbox Write from your registered email with a short...
Account settings Most requests you can settle yourself. Open your...
HOW WE WORK

Why You Can Check Our Practices

We draft this page ourselves and keep it in step with how the platform actually runs. When a process changes, the clause describing it is edited in the same working day and...

Written by the operator

Every line here comes from the team running 777zp, not from a template. If our handling of account data shifts, this page shifts with it on the same day.

Plain-language clauses

We skip legal padding. Each clause says what we collect, why we collect it, how long we keep it and who sees it, so you can read the whole page in minutes.

Named payment rails

We name the rails you actually use, JazzCash, Easypaisa, SadaPay, NayaPay and Raast, so you can tell which handler sees which detail at each step of a transfer.

Dated version history

Each revision carries its date at the top of the page. We keep earlier versions on file, so you can compare what applied on the day you first registered an account.

Channels that answer

The privacy contacts listed here are live, staffed channels, not a placeholder address. Messages sent there are logged and answered by the desk handling your account.

Security practices

Account access sits behind the password you set, and our team works from restricted systems. We check access rights on a schedule and remove them once a role ends.

How This Page Sits With the Others

Every policy page we publish shares one drafting standard, one set of contact channels and one dating convention, so nothing contradicts as you move between them. This page...

Same voice throughoutPrivacy, account terms and payment pages are drafted by one team, so definitions line up. A term explained here means the same thing on every other page we publish.
Same contact pointsThe support channels named here also appear on our terms pages. You never have to guess which inbox is the right one for a question about your own data.
Matching update datesWhen one policy page changes we revisit the others in the same pass. The date at the top of each page tells you which version you are reading at that moment.
Shared payment contextJazzCash, Easypaisa, SadaPay, NayaPay and Raast appear across our pages with the same handling detail, so payment behaviour is described identically wherever you read it.
One account, one recordEverything we hold about you sits against a single account record. Data requests, transfer history and support threads all point back to the same profile you sign into.
No conflicting promisesIf a page ever appears to promise more than this policy allows, this policy governs. We would rather correct the other page than let a mismatch stand on our site.
Built for Pakistan firstOur pages are written in the everyday English Pakistani readers use, with local rails and support hours in mind, then kept readable for anyone in another supported region.
ON THIS PAGE

What You Will Find on This Page

We lay this page out to be read quickly on a phone screen. Clauses are short, the chip row names the rails and regions we support, and a...

Short clause blocks Each clause covers one idea and then stops. You can...
Chip row up top The chips below the opening lines name the rails and...
Date stamp on changes A dated line sits at the top of the page...
Question block at the end The closing questions come from messages our support desk genuinely...
No hidden cross-references Where we send you to another page, we say why...
Readable on a phone Blocks are sized for small screens, so the whole page...

Questions We Get About Your Data

We ask for your name, date of birth, contact email and the region you play from. That is what we need to open an account, verify it and keep it reachable for you.

We receive a confirmation reference from the provider, not your credentials. Your JazzCash, Easypaisa, SadaPay, NayaPay or Raast login stays with that provider at every stage.

We hold account and transfer records while your account stays open, then for the period local rules require afterwards. Once that passes, records are deleted or stripped of anything identifying you.

Yes. Message our privacy inbox from your registered email and we compile a copy of your account and transfer records, normally within a few working days of the request.

Only with the payment providers and verification services needed to run your account, and only the detail each one actually requires. We do not sell data to outside parties.

Closing removes your profile from active use straight away. Account and transfer records stay in archive for the retention period local rules set, then leave the system in the normal deletion cycle.

The date at the top of the page updates with each revision, and material changes are flagged inside your account, so you see them the next time you sign in.