Cookie page
The cookie page explains browser storage and tracking choices, while this Privacy Policy explains the wider account records connected with those signals, including login safety, session continuity and analytics checks.
LEGAL REFERENCE
n88 Privacy Policy For Pakistan
n88 keeps this Privacy Policy focused on what we collect, why we collect it and how your account data is protected while you use our Pakistan-facing casino and...
Pakistan account dataJazzCash contextEasypaisa contextRaast records
How Our Privacy Policy Applies
This Privacy Policy explains how we handle personal data connected with your n88 account in supported regions of Pakistan, where local law permits access to our services. We collect details you provide when you create an account, verify your profile, contact us, adjust security settings or use wallet references linked to JazzCash, Easypaisa, SadaPay and Raast. We also receive technical records such
as device type, browser signals, login time, IP region and fraud-prevention flags. We use these records to run your account, protect access, meet legal requests, detect misuse and answer privacy questions. We keep data only for the period needed for account, security, tax, dispute or legal reasons, then delete or anonymise it where practical.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
DATA CHECKS
Policy Checks We Run
We write and maintain this Privacy Policy from the operator side, using the same account flows our support and risk teams handle every day. The checks below explain...
Plain language check
We avoid legal wording that hides the point. Each Privacy Policy update is checked so you can understand what data...
Local rail mapping
We map privacy wording to Pakistan wallet references, including JazzCash, Easypaisa, SadaPay and Raast. The policy explains why transaction IDs...
Access control
Your records are available only to staff roles that need them for support, security, verification or legal handling. We log...
Retention schedule
We connect each record type to a retention reason, such as account operation, fraud checks, dispute handling or tax record...
Vendor screening
When service providers process data for hosting, verification, analytics or messaging, we check contract terms and access controls. They may...
Change log
Policy changes are dated and checked before publication. When a change materially affects how we collect, use or share data...
POLICY LINKS
Consistency Across Related Policy Pages
Our Privacy Policy does not stand alone. It should read consistently with the pages that cover cookies, account terms, security controls and promotions, because the same account data may appear in more...
Terms page
The terms describe account duties and service rules. This Privacy Policy explains the personal data we need to apply those rules, verify account control and respond to lawful requests.
Security page
Security wording covers passwords, device checks and account protection. This Privacy Policy explains which security records are collected, how long they may be kept and who may access them internally.
Promotion rules
Promotion pages may require eligibility checks. This Privacy Policy explains how we use account status, location signals and transaction history to apply those checks fairly and reduce duplicate or abusive claims.
KYC wording
Verification wording explains document or identity checks. This Privacy Policy explains how those records are stored, restricted and deleted when retention reasons no longer apply.
Support terms
Support pages explain response routes. This Privacy Policy explains how chat transcripts, email threads and account messages become records that help us resolve privacy requests and protect your account.
Withdrawal checks
Withdrawal wording may mention verification steps. This Privacy Policy explains the personal data behind those checks, including wallet references, identity matches and risk flags used to prevent misdirected transfers.
Visible Privacy Page Elements
We structure this Privacy Policy so you can scan it before creating an account and return to exact sections later. The page uses short labels, dated...
Date marker
The date marker shows when this Privacy Policy was last changed. If you return after an update, you can quickly judge whether the wording may affect data handling on your account.
Account examples
Examples refer to real account events, such as verification, wallet references, login records and support messages. That keeps the policy connected to n88 rather than vague legal text.
Rights wording
Rights sections explain how you can ask to access, correct or delete data where law allows. We also explain when a record must be kept for legal or security reasons.
Sharing labels
Sharing labels separate service providers, legal requests, fraud checks and business operations. This helps you see why data may move without suggesting that every partner receives every record.
Security cues
Security cues explain encryption in transit, restricted staff access and account verification before disclosure. We include them in the Privacy Policy because protection measures affect how your data is handled.
Contact anchors
Contact anchors point you to the correct privacy route instead of a general question path. This reduces delay when you ask for access, correction, deletion or data-use clarification.
Questions About n88 Privacy
We collect account details, contact data, verification records, wallet references, device signals, login history and support messages. We collect only what is needed to operate your account, protect access and meet legal duties.
Yes. When your account uses JazzCash, Easypaisa, SadaPay or Raast references, we may store transaction IDs, timing, status and matching details. We use them for account reconciliation, support and misuse prevention.
You can ask for access to personal data linked to your account where local law permits. We may verify account control first and remove data about other people before sending a response.
You can ask us to correct inaccurate account details, contact records or verification fields. Some changes need proof, especially when they affect identity checks, wallet matching or account-security decisions.
Some records may remain after closure for dispute handling, fraud prevention, tax records, legal requests or security checks. When those reasons end, we delete or anonymise the data where practical.
We may share data with providers that support hosting, verification, messaging, analytics, security and transaction processing. They process data for our account operations and must follow contract limits on use.