LEGAL REFERENCE

How 777wu Handles The Data You Share

Open an account with 777wu and you hand us a small set of details — your name, contact number and the payment handle you use for JazzCash, Easypaisa...

Account Details ExplainedPayment Handles MaskedDeletion RequestsAge Screening
777wu How 777wu Handles The Data You Share

What We Hold And For How Long

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

ASK OUR DESK

Reaching The Team Behind Your Policy

Privacy requests should not sit in a queue for weeks. Our desk handles them through live chat inside your account, email from...

Live Chat In Your Account Open the chat panel from any page inside...
Email The Privacy Desk Write to our privacy address from the email...
WhatsApp In Working Hours Our WhatsApp line runs through Pakistani working hours...
INTERNAL CHECKS

Who Checks How We Handle Data

Every change to how we store or share account data passes an internal sign-off before it goes live, and the person who wrote it never approves it. Our team works to Pakistani...

Separate Approvals

Policy changes reach production only after a second team signs off. The writer and the approver are never the same person, and every edit carries a date and a reason.

Access Logs

Each time a staff account opens a customer record, the system writes a timestamp. We sample those logs monthly, which keeps casual curiosity out of your file and makes misuse visible.

Quarterly Permission Audits

Rights are granted per task and expire when a project ends. Four times a year we pull the full permission list and remove anything that no longer matches a live job.

Training That Sticks

Anyone touching account data finishes privacy training when they join and repeats it yearly. Sessions use real cases from Pakistani payment flows rather than generic slides, so the guidance fits the work.

Plain Wording

We write these pages in the same voice we use on chat, without legal padding. If a clause cannot be read in one pass, we rewrite it before publishing.

Escalation Contacts

A named data lead owns privacy escalations, and the route to reach that person sits on this page. If a first reply misses the mark, ask for the lead directly.

Same Rules Across Every Page We Publish

This privacy page sits beside our terms, payment and account pages, and the definitions have to agree. When a term changes, every page carrying it is updated in...

Shared Definitions
Words like account, payment handle and transaction mean the same thing here, on our terms page and on our payment pages. A change to any definition triggers a matching edit elsewhere.
One Release Calendar
Policy edits ship together rather than page by page. When we change how long records are held, the wording here and the related clause elsewhere carry the same date.
Consistent Retention
Retention windows quoted here follow the schedule our operations team works to daily. Support cannot promise a shorter or longer period than the one written down on this page for your account.
Aligned Payment Clauses
JazzCash, Easypaisa, SadaPay, NayaPay and Raast handling is written once, then referenced by our other pages. The same masked references and visibility rules apply wherever you read about them.
No Contradicting Claims
If a line on another page seems to promise more than this one allows, this page governs. We correct the mismatch rather than leaving two answers in circulation.
Contact Paths Repeated
The chat, email and WhatsApp routes listed here match those on our support pages, so you reach the same desk whichever page you start from. Nobody gets bounced between teams.
Version Tracking
Each update carries a date beside the heading. Older copies stay in our internal archive, so we can show exactly what you agreed to on the day you joined.
ON THIS PAGE

What You'll Find On This Page

The layout here is built for reading rather than scrolling past. Blocks follow the order questions usually arrive in: what we hold, how long we keep it, who...

Summary First The opening block lists the categories of data your account...
Plain Headings Every heading names its subject outright: retention, sharing, access, deletion...
Jurisdiction Line Access lines sit close to the sections they affect, using...
Chip Row Context The chips above tie this policy to the rails you...
Change Dates When something shifts, the date beside the heading moves with...
Your Controls Correction, access and deletion requests each get a short block...

What You Ask Us About Your Data

Your name, mobile number, email and date of birth for age screening, plus the payment handle you plan to use. We verify the mobile number with a one-time code.

No. We hold a masked reference tied to your account so you can move money without re-entering credentials each time. Full payment credentials stay with the provider, not on our systems.

Records stay for as long as Pakistani rules require for the payment type you use, then move onto a rolling deletion schedule. You can ask which period applies to you.

Yes. Send the request from your registered email or through in-account chat. We close the account, delete what we can, and confirm in writing which records we must keep.

Only staff whose current role needs it: payments, support and compliance. Access is logged, limits are set per task, and permission lists are audited each quarter so rights do not linger.

Where local law permits, you get the same handling and the same request routes. Some markets restrict particular features, and we tell you before you open an account.