Account terms
Account terms describe how your leeapk account may be used. The privacy policy explains what personal data supports those actions, including login details, verification records and account contact fields.
leeapk keeps casino, slot and sportsbook account data in one privacy policy so you can see what we collect before you open an account. We explain payment verification...
This policy applies when you browse leeapk, open your account, enter the lobby, use cashier pages or contact our team from Pakistan, where local law permits. We collect only the details needed to run your account, verify payments, secure access and answer privacy requests. That can include your name, mobile number, email, login activity, device signals, transaction references and chat history. We
do not sell your personal data. We share limited records with payment and security partners only when that is needed to process a transaction, check misuse, meet a lawful request or keep your account services working.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Privacy questions should reach people who can act on them. We route account access, correction and deletion requests through channels that connect your message with your leeapk account record, payment reference or device session.
Email [email protected] with your account mobile number, the request type and any payment reference you want us to check. We answer from the same privacy queue so your thread stays together.
Use in-account chat when you can still log in. Our team may ask short verification questions before discussing personal data, because privacy changes must be linked to the correct account.
For JazzCash, Easypaisa, SadaPay or Raast privacy queries, include the transaction time and reference code. We use those details to locate cashier records without asking for wallet PINs.
We keep the privacy policy useful by tying each promise to an account process you can recognise. The wording is checked against cashier flow, sign-in security, support handling and the data stored...
We describe account, device, payment and support data separately, so you can understand why each group exists. This avoids vague wording and helps you decide what to share with us.
JazzCash, Easypaisa, SadaPay and Raast records are explained as transaction references, timestamps and status checks. We do not ask for wallet passwords or codes inside this policy.
Only teams with a work need can see account records. Cashier staff, support staff and security staff have different access levels, and access changes are tracked inside our tools.
We explain device logs, IP signals and failed login records because they help us spot account misuse. These records are handled for security, not for selling your profile.
We keep records only for account service, dispute handling, security and legal needs. When a record is no longer needed, we remove it or make it harder to link back to you.
When privacy wording changes, we place the date near the policy heading. That helps you see whether the section you read reflects the current account and cashier flow.
Our privacy policy sits beside account terms, cookie wording and cashier rules, but it has its own job. This page explains personal data handling, while related pages only repeat privacy points when...
Account terms describe how your leeapk account may be used. The privacy policy explains what personal data supports those actions, including login details, verification records and account contact fields.
Cookie wording covers browser storage and session tools. This privacy policy connects those tools to account security, remembering preferences and keeping cashier pages working during your visit.
Cashier rules explain transaction steps. This privacy policy explains the data behind those steps, such as wallet references, transfer status, account matching and checks for unusual activity.
Support pages tell you how to reach us. This privacy policy explains what we keep from those conversations, including chat text, email threads and verification questions used during help requests.
Security messages may warn you about passwords or devices. The privacy policy explains the records behind those alerts, including login time, device type, IP signal and failed access attempts.
Promo terms may ask for account eligibility checks. The privacy policy explains how we handle the account data used for those checks without turning it into unrelated profiling.
Withdrawal wording covers how a request is processed. This privacy policy explains identity matching, transaction references and support records that may be checked before money leaves your account.
This page is built so you can spot the parts of our privacy practice that matter before you join. The layout separates data types, legal reasons, local payment...