Account pages
Account screens may show short privacy prompts when you update your phone, email or password. Those prompts connect back to this policy for fuller data handling detail.
LEGAL REFERENCE
How l99 protects your privacy
l99 keeps your account data, identity checks and payment-related records inside a controlled privacy process for Pakistan where local law permits. Open your account with clear visibility on...
Account data usePakistan supportJazzCash contextSecurity checks
Our privacy posture for Pakistan
This Privacy Policy explains how l99 collects, uses, stores and shares data linked to your account in supported regions of Pakistan. We collect details you provide during account opening, sign-in activity, device signals, customer care messages and records needed to process withdrawals or other account actions. Payment names such as JazzCash, Easypaisa, SadaPay and Raast may appear in account records so we
can match a request to your profile and reduce misuse. We do not sell your personal data. We share limited data only with service partners who help run security, payments, verification, hosting, analytics or customer care. Where local law permits, you can ask us to access, correct or erase eligible account data, subject to security and record-keeping duties.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
CONTACT ROUTES
Contact us about privacy
You can reach us about privacy through the channels shown on l99 after sign-in and on public contact areas. To protect you, we may ask for account markers before discussing personal data. Keep your request clear, include the email or phone linked to your account, and never share passwords or one-time codes.
Team online
Privacy email
Use the privacy email listed on l99 for access, correction or deletion requests. We read each request against account records and reply through the same channel unless extra verification is needed.
Live chat path
If you are signed in, chat can pass your privacy question to the right team. We may confirm recent account activity before discussing data linked to JazzCash, Easypaisa or Raast.
Account ticket
A ticket creates a dated record of your request and our response. It helps when your privacy query involves name spelling, phone changes, device access or withdrawal verification.
POLICY CHECKS
How we keep this policy current
Our privacy wording is maintained by the teams that handle account security, customer care and payment reconciliation. When a process changes, we check whether the policy still explains...
Operational input
The people handling verification, withdrawals and support queues help shape this policy. That keeps the wording connected to real account...
Change tracking
When we adjust data collection or partner access, we check the policy text and keep internal change records. This helps...
Security alignment
Privacy wording is checked against sign-in protection, session controls and device alerts. The policy should match how we actually reduce...
Payment record care
JazzCash, Easypaisa, SadaPay and Raast references are handled as account records, not public profile details. Access is limited to teams...
Plain English drafting
We write this policy in clear Pakistani English, with direct wording about collection, use and sharing. You should not need...
Request handling
Privacy requests are logged with dates, account markers and response status. This gives you a clearer path when asking about...
PAGE CONSISTENCY
Policy consistency across l99 pages
Privacy wording must stay aligned wherever l99 describes account handling. The same ideas apply on contact pages, cashier screens and account settings, but this page gives the full privacy position. If another...
Cashier screens
Cashier areas may mention record checks for JazzCash, Easypaisa, SadaPay or Raast. This policy explains why those records are stored and who may access them.
Support forms
Support forms collect only the fields needed to answer your request. If your message includes personal data, we handle it under this policy and our security rules.
Cookie banner
Cookie wording is kept short on the banner, while this policy explains device identifiers, analytics signals and session records in a broader privacy context.
Promotional pages
Campaign pages may ask you to sign in before showing account-specific material. This policy covers how we connect that activity to your profile and communication settings.
Security alerts
Security alerts may use phone, email or device data to reach you. This policy explains that use as part of account protection and fraud reduction.
Legal pages
Other legal pages may refer to identity checks or record retention. This policy focuses on personal data, privacy rights and how l99 handles your requests.
LAYOUT SIGNALS
Privacy cues you can see
We design privacy elements so you can spot important data handling points without searching through every screen. Short notices appear near forms, account changes and verification steps. This...
Form notices
When a form asks for personal data, the nearby wording...
Account markers
Your phone, email and verification status help us match privacy...
Session prompts
Sign-in prompts may mention device checks or session expiry. Those...
Cashier labels
Labels near JazzCash, Easypaisa, SadaPay and Raast requests explain why...
Support history
Your past support messages may be visible to trained agents...
Policy date
The policy date tells you when this wording was last...
Privacy questions from your account
We collect account details you give us, sign-in records, device signals, support messages and verification records. Payment references may also be stored when needed to match JazzCash, Easypaisa, SadaPay or Raast activity.
Payment-related records help us match requests to your account, check unusual activity and resolve support questions. We use references such as transaction IDs and wallet names only for account handling and security purposes.
Yes, you can ask us to correct eligible account data where local law permits. We may request proof or account markers before making a change, especially for phone, name or payment-linked records.
We share limited data with service partners who help provide hosting, security, verification, analytics, support and payment processing. They receive only what is needed for their role and must handle it securely.
We keep account records for as long as needed for service, security, legal and dispute-handling reasons. Some records may remain after closure when retention duties or fraud checks still apply.
Send your request through the privacy email, chat path or account ticket route shown by l99. Include account markers, describe the data involved and avoid sending passwords or one-time codes.