Terms connection
The Privacy Policy explains data handling, while our terms explain account use. When both pages mention verification, this page controls how personal data is collected, stored and shared.
LEGAL REFERENCE
Privacy Policy for your l77 account
l77's Privacy Policy explains how we handle account, device, session and payment data when you open your account and use our lobby in supported regions. Read it before...
Account dataDevice checksSession recordsJazzCash context
How we handle your data
Our Privacy Policy sets out the data we collect, why we use it, how long we keep it, and the choices you can make when you access l77 from Pakistan where local law permits. We collect only the details needed to create your account, secure sign-ins, process support requests, run fraud checks, and connect payment references with the right account record. When
you use JazzCash, Easypaisa, SadaPay or Raast, we receive confirmation data such as reference numbers, status messages and timestamps rather than full wallet credentials. We may share limited records with service providers who help with hosting, analytics, identity checks, security monitoring and payment processing, but they must handle that data under written controls. You can ask us to correct account details, explain
a data use, or handle a privacy request through the contact paths below.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
CONTROL SIGNALS
Checks behind this privacy policy
We maintain this page as a working policy, not a decorative legal page. The controls below describe how l77 keeps privacy wording aligned with account flows, support handling and payment references used...
Clear data map
We map account, device, payment and support data to the exact purpose that needs it. This helps us avoid collecting extra fields that do not serve security, access or service handling.
Access verification
Before we share account data back to you, we verify ownership using records already linked to your profile. This may include mobile, email, session signals or recent payment reference details.
Limited staff access
Only trained staff with a service need can view personal data inside our tools. Access is role based, logged, and narrowed so each team sees only what their task requires.
Retention checks
We keep records only for account service, security, legal handling and dispute support. When a record no longer has a valid reason to stay, we remove or anonymise it under our process.
Provider controls
Service providers handling hosting, analytics, security or payment processing receive limited data for their task. We require them to protect it and not use it for unrelated purposes.
Policy change log
When we revise privacy wording, we check it against current account screens, support scripts and payment status flows. If the change affects your choices, we make the update visible here.
POLICY ALIGNMENT
Consistency across l77 policy pages
Our legal pages are separate, but they should not contradict each other. This section explains how the Privacy Policy connects with account rules, cookie choices, security wording and support procedures across l77.
Cookie wording
Cookie settings and similar tools are explained in privacy language here. Any separate cookie banner should match these purposes, including analytics, security checks and session continuity.
Payment records
Payment pages may show how a transfer works, but this policy explains what data is attached to that action. We separate wallet credentials from status records and account matching data.
Security page fit
Security wording should support privacy choices, not replace them. If we describe device checks or unusual login alerts elsewhere, this policy explains the personal data involved.
Support scripts
Support replies must match this policy when asking for identity checks or account correction data. We train our team to request only the details needed for the privacy task.
Promotion records
If a campaign creates account activity records, this policy explains how those records are handled. We keep promotional data tied to account service, fraud checks and required reporting only.
Change handling
When another legal page changes, we check whether it affects this Privacy Policy. If a data practice changes, we update this page so your privacy choices remain clear.
PAGE MARKERS
What this policy layout shows
The visible parts of this page are designed to make privacy decisions easier. We separate data categories, control points, contact paths and account-security cues so you can find...
Plain sections
Each section focuses on one privacy task, such as collection...
Local context
Pakistan payment names appear only where they help explain data...
Choice cues
Where you have a privacy choice, we point to the...
Security prompts
Security labels show where data may be used to protect...
Retention markers
Retention wording separates short session data from longer account or...
Contact placement
Contact details sit close to the relevant privacy tasks. If...
Answers about l77 data handling
We collect details needed to create and secure your account, such as name, mobile, email, login records and support history. Extra documents may be requested only when verification or dispute handling requires them.
No. For JazzCash, Easypaisa, SadaPay and Raast flows, we use status data such as reference numbers, timestamps and confirmation results. Your wallet password or full banking credential is not collected by us.
Device checks help us protect account access, spot unusual sessions and keep payment requests tied to the correct profile. We use signals such as browser, IP range and session timing for security purposes.
Yes. Send us the detail that needs correction and enough account proof to verify you. We will check the record, update what is inaccurate, or explain why a record must remain unchanged.
Access is limited to staff or service providers who need the data for support, security, payments, hosting or legal handling. We use role controls and logs to reduce unnecessary internal access.
Retention depends on the record type and reason for keeping it. Session data may be shorter lived, while account, payment reference or dispute records may stay longer for service and legal handling.
Email [email protected] or start with support chat if your request is urgent. We may ask you to confirm account ownership before we share, correct or discuss personal data.