Account terms link
Account terms explain what you must provide to maintain access. This Privacy Policy explains how we handle those account details after you share them with us.
LEGAL REFERENCE
How n88n Handles Your Privacy
n88n gives you a clear Privacy Policy before you open your account, so you can see how we collect, use and protect your account data, payment records and...
Account data explainedPayment record handlingDevice signals coveredRequest routes listed
Privacy Posture For Pakistan Accounts
This Privacy Policy describes how n88n handles data connected with account creation, login checks, casino access, sportsbook activity, support contact and payment processing in supported regions of Pakistan. We collect only the data needed to run your account, confirm access, process payment records, reduce misuse and respond when you contact us. Where local law permits, we may use identity checks, device signals,
session records and transaction references to keep account activity consistent and traceable. We do not sell your personal data. We may share limited records with payment processors, verification vendors or technical partners when that sharing is needed to operate your account, answer a privacy request or meet a lawful request.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
POLICY CHECKS
How We Keep This Policy Accurate
We maintain this Privacy Policy as an operating document, not a filler page. The wording is checked against account flows, payment handling, login protection and support practice. When we change a process...
Change record
We keep an internal change record for privacy edits, including the reason for each update. That helps our team connect written policy with live account handling.
Plain wording
We write the policy in direct Pakistani English, avoiding legal padding where a clear sentence works. You should understand the data point and its purpose.
Access control
Only assigned operational teams can view sensitive account records. Access is linked to support tasks, payment checks or security work, not casual browsing.
Payment trace care
JazzCash, Easypaisa, SadaPay and Raast references are handled as payment records. We use them to reconcile account activity and respond to valid queries.
Retention checks
We keep records only for operational, security, dispute and legal needs. When a record is no longer needed, we remove or anonymise it where possible.
Regional wording
Privacy wording is checked for Pakistan access and supported regions. If a service is restricted by local law, data handling follows the available account route.
PAGE ALIGNMENT
How Our Policy Pages Stay Aligned
This Privacy Policy works beside our cookie, account and transaction terms. Each page has a different job, but the same data principles apply. We keep language aligned so your rights, our purposes...
Cookie wording match
Cookie wording covers browser storage and tracking tools. This policy links that activity to wider privacy handling, including session records and device signals.
Transaction wording match
Transaction terms describe how payment references move through the cashier. This page explains how those references are stored, used and protected for privacy purposes.
Security language match
Security pages describe login checks and alerts. This Privacy Policy explains which account signals may be used when we detect unusual access or activity.
Support wording match
Support pages tell you how to reach us. This policy adds what we may verify before we discuss account data or respond to privacy requests.
Promo consent match
If you choose to receive account messages, this policy explains the related data use. You can ask us to adjust contact preferences through support.
Lawful request match
Where a lawful request applies, our policy pages use the same standard: share only the records needed, through the correct internal route.
LAYOUT CUES
Privacy Layout You Can Scan
We design the Privacy Policy page so you can find the parts that matter before opening an account. The layout separates collection, use, sharing, retention and request rights...
Purpose strip
The policy opens with a short purpose strip, so you...
Data category cards
We group data into clear categories such as account details...
Sharing markers
When a third party may receive limited records, the policy...
Request route box
A request route box shows how to ask for access...
Security cues
Security cues identify where login checks, session monitoring and fraud...
Date marker
A date marker helps you see when the policy text...
Privacy Policy Questions Answered
We collect account details, contact data, login records, device signals and any verification material needed for access. We use this data to run your account and protect activity.
JazzCash and Easypaisa references are treated as payment records. We use them to match account activity, resolve cashier queries and keep a traceable record for support.
Yes. Send a correction request through our account help route. We may verify your identity first, then update inaccurate details where our records allow the change.
We share limited records only when needed for payment processing, verification, platform security, technical hosting, support handling or a lawful request that applies in a supported region.
Retention depends on the record type and purpose. We keep data for account operation, security, dispute handling and legal needs, then remove or anonymise it where possible.
If login activity looks unusual, we may use device signals, session records or identity checks before restoring access. This protects your account and keeps our response documented.