Privacy Policy for your ko222 account
ko222 keeps account, device, payment and lobby activity data under one clear Privacy Policy for Pakistan, so you know what we collect before you open an account.
How we handle your personal data
This Privacy Policy explains how ko222 collects, uses, stores and shares your personal data when you create an account, verify access, use the lobby, contact support or make a transaction where local law permits. We collect only the data needed to run your account, process requests, protect access, meet legal duties and improve page reliability. Payment references may include JazzCash, Easypaisa, SadaPay,
NayaPay and Raast transaction markers, but we do not publish your wallet number inside the lobby. Some checks use device, browser and location signals from supported regions to reduce account misuse. You can ask us to correct records, explain a privacy decision or close data that we no longer need.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
How we keep this policy accurate
Our Privacy Policy is maintained by the ko222 operations team that handles accounts, payments, security checks and support replies. We update wording when collection points change, when Pakistani wallet flows require clearer...
Policy ownership
A named internal owner keeps the Privacy Policy aligned with account screens, wallet prompts, verification messages and support scripts, so you see the same data language across ko222.
Change control
When we change how data is collected, the policy text is checked against the live page flow before publication. That includes forms, login alerts and transaction screens.
Payment mapping
Wallet references are mapped to the data we actually receive from JazzCash, Easypaisa, SadaPay, NayaPay or Raast, instead of broad wording that hides the record type.
Security language
Security terms are written around real controls we use, such as password resets, device checks, session logs and restricted access for staff handling privacy cases.
Support feedback
Questions sent to support help us spot unclear privacy wording. If several account holders ask the same thing, we rewrite that clause in simpler English.
Retention checks
We check retention wording against operational need, legal duties and fraud prevention records, so account data is not described as kept longer than our process requires.
One privacy standard across ko222 pages
Your privacy expectations should not change because you move from the account page to the cashier, live lobby or support area. We keep the same privacy language across...
| Account page | The account page uses the same privacy terms for name, email, phone and login data. Any extra verification step is explained near the field that asks for it. |
|---|---|
| Cashier page | The cashier privacy wording focuses on transaction references, wallet identifiers and reconciliation records. It connects back here so you can see why the data is processed. |
| Live lobby | Live lobby privacy text covers session records, device checks and provider handoffs. It does not replace this policy; it narrows the explanation for that area. |
| Sports section | Sports activity may create market, stake and settlement records linked to your account. The same retention and security principles from this policy apply there. |
| Promotions area | If you enter a promotion, ko222 may record eligibility, opt-in time and reward status. That data is treated under this Privacy Policy and account terms. |
| Support centre | Support pages repeat the same identity-check stance before staff discuss private records. This keeps your account data safer when a case moves between teams. |
| Cookie notice | The cookie notice gives extra detail about browser storage, analytics and session tools. It works beside this policy, rather than creating separate privacy rules. |
Privacy layout elements you can see
We designed this Privacy Policy page so you can scan the parts that affect your account before you join. The visible layout highlights collection points, request routes, retention...