LEGAL REFERENCE

Privacy Policy for your 222k account

222k keeps your account, lobby access and Pakistan payment data under one privacy policy, so you can see what we collect before you open an account. We explain...

Account dataPayment recordsDevice signalsPrivacy requests

Explore the Lobby Read FAQ

How our privacy policy applies

This privacy policy describes how we collect, use, store and share data when you access 222k in supported regions of Pakistan, where local law permits. We collect account details you provide, login activity, device and browser signals, wallet references, support messages and transaction status data linked to payment rails. We use that data to run your account, verify requests, secure access, process

wallet activity, detect misuse and answer privacy questions. We do not sell your personal data. We keep records only for operational, legal and security needs, then remove or anonymise them when they are no longer required.

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

CONTACT ROUTES

Ask us about your privacy rights

Use these routes when your question is about this privacy policy, account data or records linked to your wallet activity. We may...

POLICY CHECKS

Privacy controls behind the wording

Our privacy text is tied to how our systems actually work. We align the policy with account screens, wallet records, support forms and security checks, then adjust wording when a process changes...

Clear collection points

We name the places where data enters 222k, including account forms, login checks, wallet status screens and support messages, so the policy reflects actual collection moments.

Purpose matching

Each data type is linked to a reason, such as account access, payment status, fraud prevention, security alerts or privacy request handling, not a vague catch-all statement.

Access control

Staff access to account data is limited by role. Privacy queries, wallet checks and security cases use different access levels, reducing unnecessary exposure inside our operations.

Record retention

We keep privacy and transaction records for operational, legal and security needs. When a record is no longer needed, we remove it or separate it from personal identifiers.

Local context

The policy refers to Pakistan payment rails and supported regions because privacy handling can depend on local account flows, wallet references and lawful access requirements.

Change tracking

When privacy wording changes, we update the page date and keep the new text aligned with account screens, support scripts and wallet record handling.

How this policy fits our pages

This privacy policy should read consistently with other legal pages on 222k. Each page has a different job, but privacy wording must stay aligned wherever account data, wallet...

Cookie page

Cookie wording should match this policy when it describes device identifiers, browser signals and session tools used to keep your account access stable and secure.

Terms page

Terms wording should not expand data use beyond this privacy policy. If account conduct creates security checks, the related data handling remains described here.

Security page

Security wording should support this policy by explaining login protection, device checks and suspicious activity handling without creating a separate privacy standard.

Wallet page

Wallet wording should connect JazzCash, Easypaisa, SadaPay and Raast references to transaction status, verification needs and record retention described in this policy.

Support page

Support wording should tell you how to contact us, while this policy explains how support messages and identity checks are handled after contact.

Account page

Account wording should match this policy on profile details, login history, communication choices and correction requests submitted from inside your account area.

Promo page

Promo wording should not change how privacy works. If a campaign needs account checks, the same data purpose and retention rules in this policy apply.

Policy layout you can scan

We design this privacy page so you can find the data point you care about without hunting through unrelated copy. The structure separates collection, use, sharing...

Plain headings

Section headings use direct privacy language, so you can move from account data to wallet records or contact routes without guessing what each block covers.

Short chips

Context chips call out local wallet rails and account data groups. They are labels only, helping you see which privacy topic a paragraph connects to.

Policy dates

When we change this privacy policy, the visible date should help you confirm whether you are reading the current version used by our account team.

Request wording

Privacy request text explains what we need from you and why. That helps us verify ownership without asking for details unrelated to the request.

Security cues

Security sections explain encryption, staff access and login checks in practical terms, so privacy protection is connected to the way your account is handled.

Local examples

Pakistan payment references appear only where they explain privacy handling, such as transaction status, wallet identifiers or verification records connected to your account.

Questions about 222k privacy handling

We collect account details you submit, login and device signals, wallet references, transaction status data, support messages and security records needed to operate your account in supported regions.

Wallet records help us match JazzCash, Easypaisa, SadaPay and Raast activity to your account, confirm transaction status, handle disputes and meet operational or legal record needs.

No. We do not sell your personal data. We share data only where needed for account operation, payment processing, security checks, service providers or lawful requests.

Contact us from your registered email or logged-in account. Tell us what data you want to access, and we may verify ownership before sending any account record.

Yes, you can ask us to correct inaccurate account details. Some records, such as transaction logs, may be preserved as historical records while we add corrected account details.

We keep data for operational, legal, security and dispute-handling needs. When those reasons end, we delete records or separate them from details that identify you.

We update the visible policy date when wording changes. For material privacy changes, we may also use account messages or email where that contact route is available.