One house style
Headings, kickers and the tone of each commitment follow a single style sheet, so moving between our policy pages feels like reading one document rather than several.
LEGAL REFERENCE
How 777fp Handles Your Account Data
This page sets out what we collect when you open an account with us, why we collect it and how long we keep it. It applies to you...
Plain-language wordingNo hidden clausesDate-stamped updatesContact details on-page
What We Collect And Why
We keep this policy short because you should be able to read it once and understand it. What we collect is limited to what running your account needs: your name, date of birth, contact details, device and login records, and the transaction references created when you move money through JazzCash, Easypaisa, SadaPay or Raast. We use that data to verify you, to
keep your login secure, and to meet the record-keeping rules that apply where we operate. Access to 777fp is offered only where local law permits, so the exact rules that bind us depend on the region you register from. If those rules change, we update this page and the date stamp above it. You can ask us what we hold about you
at any time.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
WHO WRITES THIS
The Team Behind This Page
We write this page ourselves rather than pasting a template. Our compliance lead owns the wording, and any change gets a second read before it goes live, so what you read here...
Named policy owner
One person is accountable for the wording on this page, so change requests do not sit in a shared inbox waiting for someone to pick them up in passing.
Version history
Every edit carries a date, so you can see when the wording last moved and what prompted it, whether a rule shift or a new payment route.
Plain-language drafting
We test sentences on colleagues outside the legal team. Any line that needs a second reading is rewritten before it reaches this page and your screen.
Local rail accuracy
The JazzCash, Easypaisa, SadaPay and Raast paragraphs here are written with the operations team that runs those rails, not copied from a generic draft for another market.
Support feedback loop
Recurring questions from our support desk feed straight back into this page, so the answers you read reflect what you actually ask us about your data.
Regular process checks
We send test data requests through our own channel to confirm the end-to-end process still works for an account registered in Pakistan before any change reaches you.
ALONGSIDE OUR PAGES
How This Page Sits With The Rest
Our policy pages have to agree with each other. If the account terms say one thing about closure and this page says something else, that is our fault and we correct it...
Shared definitions
Terms such as account data, device record and transaction reference mean the same thing on every page, which removes guesswork when you compare two clauses.
Linked where it matters
Where this page refers to the account terms or the cookie page, we link straight to the matching paragraph instead of leaving you to search the site yourself.
One contact route
Data requests, corrections and deletion asks all run through the same address, so a question never gets lost between teams because it landed in the wrong inbox.
Consistent date stamps
Every policy page shows when it was last touched. If this page carries a newer date than the terms page, that simply reflects which one changed most recently.
No duplicated clauses
We keep one version of each rule. When something changes we edit it in one place, and the sibling pages point to it rather than repeating the wording.
An escalation path
If an answer here does not match what you were told elsewhere, ask for the policy owner by name and we reconcile the two within two working days.
WHAT YOU SEE FIRST
Layout Choices On This Policy Page
We build the page so the answers you need are visible without hunting. The structure below repeats on every policy page we publish, which makes moving between them...
Summary block up front
The first thing on the page is a short summary...
Jump links per section
Each heading links down the page, which helps when you...
A single data table
Personal data, its purpose and its retention period sit in...
Question-shaped headings
Headings are written as questions where possible, so the section...
Contact block before the FAQ
Reach-us details sit above the questions section, so you do...
Visible date stamp
A date near the headline records the last change, and...
Questions About Your Privacy Here
Your name, date of birth, contact details and the identity document you upload, plus device and login records. If you fund with JazzCash, Easypaisa, SadaPay or Raast, we also keep the transaction reference from each movement.
No. We do not sell account data. We share it only with the payment and verification partners needed to run your account, and only the minimum each of them requires to complete their part.
Account records stay for as long as your account is open, then for the period local record-keeping rules require us to hold them. After that we delete or anonymise whatever remains.
Yes. Send a request from the email address registered on your account and we send back a copy of the personal data we hold, usually within a month of the request.
We ask for a strong password, watch for sign-ins from unfamiliar devices, and may ask you to confirm a code sent to your registered number before a sensitive change goes through.
We use account data to run the platform and to show you offers inside 777fp. We do not pass your contact details to outside advertisers for their own campaigns.
We update the page and move the date stamp near the headline. If a change meaningfully affects how we use your data, we tell you through your account or by email before it takes effect.