Account terms
The terms page sets out the rules of use; this policy deals with the data those rules generate, including sign-in records, device signals and the trail attached to your support tickets.
LEGAL REFERENCE
How We Look After Your Account Data
Open an account and we ask for as little as possible: a mobile number, a wallet reference from JazzCash, Easypaisa, SadaPay or Raast, and basic device data. This...
Minimum data collectedOne-time code on sign-inNo data sold onYour settings, your choices
What This Policy Sets Out For You
Our privacy commitments apply wherever you use laam 777 in supported regions, and they sit alongside the law that governs your account. Where local law permits, we hold only the minimum needed to run your account; where a payment partner or authority in Pakistan requires more, we keep it for as long as that obligation lasts and no longer. JazzCash, Easypaisa, SadaPay
and Raast process your transfers themselves, so we receive a confirmation reference rather than your wallet credentials. If a clause here clashes with a mandatory rule in your region, that rule wins and we revise this page. Change notices reach your account inbox before new wording takes effect, so you always know what applies to you at the point of use.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
HOW WE HANDLE IT
The Standards Behind Our Data Handling
We publish the same rules we follow internally: collect little, hold only while there is a reason, and give each request a named owner. Our team checks this page whenever a new...
Data minimisation
We collect the fields an account needs to work, such as mobile number, wallet reference and device signals, and leave out anything we cannot explain a purpose for when you ask us.
Named owners
Each request type has a person accountable for it, from wallet reference lookups to cookie preferences, so your ticket never sits without a named owner inside the team.
Retention windows
Payment references tied to JazzCash, Easypaisa, SadaPay and Raast follow fixed retention windows, after which they clear from active systems and are held only where the law requires.
Access control
Account access runs on session checks and one-time codes sent to your registered mobile number, so a leaked password alone cannot open your profile on another device.
Written trail
Every request is logged with a timestamp and a result. You can ask for that summary at any point, which keeps our answers checkable rather than promises made verbally in chat.
Plain wording
We write this page in everyday English, revisit it whenever our systems change, and flag dated revisions so you can see what moved and when it moved.
ACROSS OUR PAGES
How This Page Sits With Our Others
This policy stands on its own, but it reads alongside our account terms and payment pages. Where those pages describe what you can do, such as join, fund an account or withdraw...
Payment pages
Our payment pages explain how JazzCash, Easypaisa, SadaPay and Raast transfers reach your balance. Here we explain the reference kept from each transfer and how long it stays.
Cookie notice
The cookie part of this policy names the categories we set, what each one does for your session, and how to switch the non-essential ones off from your browser.
Security wording
Security copy across the platform describes how we protect your account. This page adds the retention side, covering how long access logs and verification records are held afterwards.
Campaign notices
Any campaign you enter carries its own short notice. This policy explains the contact details and eligibility flags we hold while that campaign runs and for a set period after.
Help centre
Help-centre articles answer quick how-to questions, while this page records our formal position on access, correction, portability and deletion requests raised against the account data we hold.
Change log
Dated revisions at the foot of every policy page show what changed between versions, so a difference you spot between two pages is always traceable to a specific update.
WHAT YOU SEE FIRST
The Layout That Keeps Policy Readable
A long policy only works if you can find the clause you need. We built this page around short sections, plain headings and control panels you can act...
Section jump bar
A sticky jump bar sits across the header and moves...
Clause summaries
Each clause opens with a one-line summary in everyday wording...
Consent switches
Cookie categories appear as switches you control, grouped by what...
Dated version stamp
Every revision carries a date and a short line on...
Request panel
One panel handles access, correction and deletion requests, pre-filling your...
Phone-first spacing
Text sizes, tap targets and tables adjust for smaller screens...
Common Questions About Your Data
Your mobile number, the wallet reference from the method you used, basic device and browser signals, and the written trail our support desk keeps on any request you raise with us.
No. JazzCash, Easypaisa, SadaPay and Raast process the transfer themselves, so we receive a confirmation reference and the amount, never your wallet PIN, balance or full credentials.
Account data stays while your account is open. Payment references follow fixed retention windows, and a closed account clears from live systems once any legal holding period has ended.
Yes. Send an access request from your account inbox or the support panel, confirm your identity with a one-time code, and we compile the record and release it to you.
You can request deletion at any time. We remove everything not under a legal or payment obligation, and tell you which records must stay and how long they will stay.
Only what a service needs to work: payment confirmations with the wallet provider, and fraud signals where local law permits. We do not sell personal data to anyone.