LEGAL REFERENCE

How 40k Handles Your Data

40k gives you one Privacy Policy for account data, lobby activity, support messages and payout checks, so you can see how each record is handled before you open...

Pakistan data careJazzCash contextEasypaisa recordsSadaPay checksRaast privacy
Explore Lobby Read FAQ
40k How 40k Handles Your Data

Our Privacy Policy Position

This Privacy Policy explains how 40k collects, uses, stores and shares your personal data when you create an account, enter the lobby, contact us, or request a payout in supported regions. We collect only the details needed to run account access, identity checks, security alerts, transaction matching, support replies and legal record keeping. Payment references may include JazzCash, Easypaisa, SadaPay, NayaPay and

Raast, but we do not ask you to share unnecessary wallet secrets in chat. Where local law permits access, we may work with verification, hosting, analytics and payment service providers that process data under our instructions. We keep records only for the period needed for account operation, fraud prevention, dispute handling and legal duties, then remove or anonymise them when retention is

no longer required.

Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.

CONTACT ROUTES

Privacy Help From Our Team

If you have a Privacy Policy question, we want the route to feel simple and human. Use the contact path that matches...

Account privacy inbox Email our privacy desk when you need a...
Live chat privacy queue Use chat for urgent privacy questions, such as...
Security escalation path If you believe your account details were exposed...
POLICY CHECKS

How We Keep It Reliable

Our Privacy Policy is kept close to the way 40k actually works, not hidden behind vague language. We check it against account screens, wallet flows, support scripts and...

Operational checks

Before we update the Privacy Policy, our team compares each paragraph with real account steps, including login, profile edits, wallet...

Local payment context

We name Pakistani rails where they affect privacy, including JazzCash, Easypaisa, SadaPay, NayaPay and Raast. The policy explains record matching...

Security language

We explain device logs, session records, alerts and access controls in plain words. This helps you understand why some data...

Retention checks

Our retention wording is checked against fraud prevention, dispute handling and legal record duties. When a record is no longer...

Cookie clarity

The policy explains cookies and similar tools used for login stability, language settings, security checks and basic site measurement, with...

Change control

When the Privacy Policy changes, we update the page date and adjust related wording across support replies and account notices...

How This Page Stays Consistent

This Privacy Policy sits beside other 40k legal pages, but it has its own job. It focuses on personal data: what we collect, why we use it, who...

Terms page link
Our Terms page explains account rules, while this Privacy Policy explains the personal data behind those rules, such as identity checks, login records and wallet reference matching.
Cookie page match
Cookie wording stays aligned with the Privacy Policy, so security cookies, preference tools and measurement tags are described with the same purpose, retention and choice language.
Support script match
Support replies use the same privacy wording you see here, especially when you ask for account access, correction, deletion, transaction records or security log checks.
Wallet record match
Where wallet references appear in account screens, this policy explains why 40k keeps matching records for JazzCash, Easypaisa, SadaPay, NayaPay and Raast transactions.
Security page match
Security content explains account protection, while this Privacy Policy explains the data used for that protection, including device signals, failed login attempts and risk checks.
Consent wording match
When we request consent for optional tools, the wording connects back to this Privacy Policy so you can see the purpose, data category and control route.
Contact detail match
Contact addresses and response paths are kept consistent across legal pages, helping you send privacy requests to the right 40k team without repeating your issue.
CLEAR LAYOUT

Privacy Elements You Can Scan

The layout of this Privacy Policy is built for quick reading without hiding the detail. Each visible block has a privacy purpose, from data categories to retention wording...

Summary cards Short cards introduce the main privacy themes before the longer...
Purpose labels Each data category is paired with a purpose label, helping...
Retention table Retention wording is grouped by record type, making it easier...
Rights panel A dedicated rights panel explains how you can ask for...
Cookie banner link Cookie choices are connected to this policy through a visible...
Contact strip The contact strip appears near privacy-heavy sections, giving you a...

Privacy Policy Questions Answered

We collect the details needed to create and protect your account, such as contact data, login records, device signals, verification details and transaction references linked to supported wallet or bank rails.

These names help explain how transaction references may be matched to your 40k account in Pakistan. We use the reference details for reconciliation, support checks, dispute handling and security monitoring.

Yes. Send a privacy request through email or chat, and we will verify your identity before sharing account data that can lawfully be provided without exposing other people or security controls.

Retention depends on the record type. Account, verification, support, transaction and security records may be kept for different periods because fraud prevention, disputes and legal duties require different handling.

We may share data with providers that help operate hosting, verification, analytics, support, payment reconciliation and security tools. They process data for defined purposes under controls set by 40k.

Contact support with the field that needs correction and any proof we request. We check the change against account security needs before updating records covered by this Privacy Policy.

We update the page date and adjust related support wording when privacy terms change. If a change affects how we use your data, we make the update clear on this page.