Terms link
Where account rules require identity or payment checks, this policy explains the related personal data. The wording is aligned so you can understand both the rule and the data use.
LEGAL REFERENCE
How j18 handles your privacy
j18 places account privacy, lobby access records and Pakistan payment data in one clear policy, so you know what we collect before you open your account. Read it...
Pakistan privacy scopeAccount data handlingJazzCash Easypaisa contextSadaPay Raast context
Our Pakistan privacy policy posture
This Privacy Policy explains how j18 collects, uses, stores and shares personal data connected with your account, device, location, security checks, live casino sessions, sportsbook activity and payment verification in supported regions of Pakistan. We use the data to run your account, confirm access, process account requests, detect misuse and answer privacy questions. Payment names such as JazzCash, Easypaisa, SadaPay and Raast
appear here only to explain privacy context around transaction references, sender details and verification records. We may work with processors for hosting, security, analytics, payment routing and customer care, but we keep their access limited to the work they perform for us. Where local law permits, you can ask us to access, correct or delete eligible records linked to your account.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
POLICY CARE
How we keep policy text accurate
We maintain this Privacy Policy as an operating document, not a decorative page. When we change account flows, payment verification, device security or support routing, the policy is...
Flow mapping
We map each policy clause to a real account step, such as login, identity checks, session records or withdrawal verification...
Processor checks
Hosting, security, analytics and payment partners are listed internally against their purpose. We avoid giving processors broader access than needed...
Change log control
Policy edits are recorded with the reason for change, affected data category and date applied. This helps us explain what...
Pakistan context
We write for Pakistan account flows, including JazzCash, Easypaisa, SadaPay and Raast references. This keeps privacy wording close to the...
Access discipline
Staff access to personal data is role-based. Support can view enough to answer your request, while deeper security logs are...
Plain language
We avoid legal clutter where a direct phrase works. The policy explains collection, use, sharing, retention and rights in language...
PAGE CONSISTENCY
Consistency across related privacy pages
Our Privacy Policy works with other legal pages without sending you in circles. Terms describe account rules, cookie wording explains browser storage, and this page explains personal data handling. When one page...
Cookie wording
Cookie language covers browser storage, device signals and preference records. This Privacy Policy connects those signals to account security, session continuity and privacy request handling.
Payment references
Payment pages may show JazzCash, Easypaisa, SadaPay or Raast labels. This policy explains which transaction references may be stored and why they support account verification.
Security records
Security pages describe access controls, while this policy explains the personal data behind login alerts, device checks and fraud prevention. The two pages should not conflict.
Retention phrasing
Retention wording stays consistent across legal pages. If a record must be kept for account safety or lawful handling, we state the purpose rather than hiding it.
Rights process
Request paths are described in one voice across legal pages. You should not need a separate rulebook to ask for access, correction or deletion of eligible data.
Regional access
Where access is limited to supported regions, related pages use the same phrasing. This helps you understand privacy handling without mixed wording about availability.
VISIBLE CUES
Privacy layout cues you can see
The policy page is laid out so you can scan the privacy points that matter before creating an account. We separate collection, use, sharing, retention and your request...
Clear date marker
A visible date marker shows when the Privacy Policy was...
Scope cards
Scope cards identify the data areas covered by the policy...
Request shortcuts
Privacy request shortcuts point you toward email, chat or the...
Data category labels
Labels separate identity, contact, payment reference, technical and support data...
Sharing markers
Sharing markers show when processors may receive limited data for...
Retention prompts
Retention prompts explain why some records remain after an account...
Privacy policy questions before joining
We collect the details needed to create and protect your account, such as contact data, login records, device signals and verification checks. Extra records may appear when you contact support or request account changes.
Yes. The policy explains privacy handling for transaction references linked with JazzCash, Easypaisa, SadaPay and Raast. We use those references to verify account activity, resolve queries and maintain payment records.
Session records help us operate your account, confirm activity, manage disputes and protect the platform from misuse. We do not need more personal data than is relevant for those account purposes.
Yes, you can ask us to correct eligible account data. We may first verify your identity through account signals or payment references, because changing private records without checks could expose your account.
Only the teams needed to handle the request should see it. Support may capture the request, while privacy or security personnel may handle deeper account records depending on the issue raised.
Retention depends on the record type and purpose. Some data stays while your account is active, while security, transaction or legal records may remain longer where needed for account protection or lawful handling.