Privacy Policy for lucky99 accounts
Our Privacy Policy sets out the account, casino lobby and payment data we collect before you open your lucky99 account. You can see how we use it, when...
How we handle your data
This Privacy Policy explains how we collect, use, store and share personal data when you access lucky99.info from Pakistan or other supported regions where local law permits. We collect account details you provide, device signals needed for security, casino and sportsbook session records, and payment verification data linked with JazzCash, Easypaisa, SadaPay or Raast. We use those records to run your account,
confirm identity, process account actions, respond to messages and meet legal duties that apply to us. We do not sell your personal data. When service partners help with hosting, fraud checks, messaging or payment routing, they receive only the data needed for that task and must handle it under written controls. This page also explains retention, cookies and the choices available to
you.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Ask us about privacy
If your privacy question is urgent, we keep contact paths close to your account area. Tell us the email or phone number linked with your lucky99 profile, the data request you want handled, and any payment reference that helps us identify the correct record. We answer in clear Pakistani English and avoid asking for full wallet PINs.
Account privacy inbox
Use the privacy email shown inside your logged-in account for access, correction or deletion requests. We confirm your identity first, then route the request to the team handling account records.
Live chat escalation
Start a chat when you need help locating the privacy channel. Our agent can raise a ticket, but we will not discuss sensitive account data until verification is complete.
Payment record checks
For JazzCash, Easypaisa, SadaPay or Raast privacy queries, share only the transaction reference and account name. We do not ask for wallet passwords or full banking credentials.
Why our policy is checked
We treat this Privacy Policy as an operating document, not a page left aside. Product, account security and customer care teams check it when data handling changes, such as a new cookie...
Account flow match
The policy mirrors the fields you see during account creation, profile changes and password recovery. If a form changes, we check whether the privacy wording needs an update.
Security logging
We describe device and login signals because they help protect your account from unauthorised access. These records are limited to security, fraud checks and account recovery needs.
Payment rail clarity
JazzCash, Easypaisa, SadaPay and Raast checks may create references, time stamps and status records. Our policy explains why those records exist and how long we keep them.
Service partner limits
Hosting, messaging and payment partners receive only the data needed for their task. We require written controls covering confidentiality, access limits and safe handling of your record.
Retention discipline
We keep data for account operation, security and legal duties, then remove or anonymise it when retention is no longer needed. Some records remain longer for dispute handling.
Plain language checks
Our policy wording is checked for clear en-PK language so you can understand what happens to your data without needing legal training or technical background.
Aligned with related policies
Privacy wording works better when it connects with nearby legal pages. We keep this page consistent with our account terms, cookie notice and contact procedures, so the same...
| Account terms link | Our account terms explain conduct and access rules, while this policy explains the personal data behind those actions. We keep both pages aligned on verification and security checks. |
|---|---|
| Cookie notice link | The cookie notice covers browser storage and similar tools. This policy connects those tools to purposes such as login continuity, fraud prevention and site performance checks. |
| Payment terms link | Payment wording describes how wallet actions are processed. This policy explains the privacy side, including reference numbers, status records and identity checks linked with each transaction. |
| Security procedure link | Security procedures describe account protection steps. This policy explains related data use, such as login time, device type and verification results kept for protection purposes. |
| Support script link | Customer care scripts are shaped around the same privacy rules. Agents can identify your account, but they avoid collecting wallet PINs or unnecessary personal details. |
| Retention schedule link | Our retention schedule sets internal time frames for keeping records. This policy gives you the plain-language reason each main record category may remain stored. |
| Change log link | When privacy wording changes, we update the date and keep an internal change log. You can ask what changed if the new text affects your account. |
Privacy page elements you will see
This Privacy Policy is built with visible markers so you can scan it before opening an account. We place collection points, sharing rules, cookie details, retention...
Updated date
The date near the policy header tells you when we last changed the wording. If we alter data handling in a material way, we refresh that date.
Data categories
We group records by account details, device signals, session activity, payment references and messages. This helps you see which part of your lucky99 use creates each record.
Purpose labels
Each data category is tied to a clear purpose, such as account access, fraud checks, service messages or legal duties. We avoid vague reasons where possible.
Sharing limits
The sharing section names the types of partners involved, such as hosting, verification, messaging and payment routing. It also explains why each partner may receive data.
Your request path
The contact block explains how to ask about access, correction, deletion or a privacy concern. We verify your identity before acting on account-level requests.
Cookie wording
Cookie wording explains browser storage used for login continuity, security and performance checks. You can manage some settings through your browser or device controls.