Terms of Use
Our terms cover your relationship with ok2222; this page covers the data behind it. Read together, they set out what you have agreed to and how we handle your details.
LEGAL REFERENCE
How We Handle Your Data at ok2222
Your ok2222 account runs on data you share with us, and this page sets out how we collect, store and use it across Pakistan. We cover sign-up particulars...
Account DataPayment RecordsCookie ChoicesAccess Requests
Where This Policy Applies
This policy covers the ok2222 service you reach through ok2222.games, from the lobby and your wallet to the messages we send you. Where local law permits, we handle your data under the rules in force where you live, so your protections in Pakistan follow local practice rather than one global standard. If a provincial rule asks for something different from what this
page sets out, that rule takes precedence and we will flag it when it touches your account. The chips below name the rails we settle through, because each returns only a limited slice of transaction data, and that slice falls under this policy too. We update this page whenever a rail, a rule or a feature changes, and the version here governs
your account today.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
WHO WRITES THIS
Who Writes and Checks This Page
We maintain this page with the teams that run ok2222 day to day: payments, account security and support. When we add a rail, a market or a new...
Payments Team
The people who reconcile JazzCash, Easypaisa, SadaPay and Raast settlement files every day write the clauses about transaction records, because...
Security Engineers
Engineers who run login, device checks and session timeouts draft the security clauses, then walk each line back against what...
Support Leads
Support leads go over the contact paths each quarter, because they see which questions arrive most often and where the...
Second Reader
A second reader from outside the drafting team checks each revision for plain language, accuracy against our internal logs and...
Dated Revisions
Every revision is dated and stored, so you can ask what changed between the version you accepted at sign-up and...
Local Practice
We follow the data-protection expectations that apply where you live, and we say plainly when a local rule asks for...
CONSISTENT ACROSS PAGES
How This Policy Sits With Our Other Pages
We keep our terms, this policy and the payments page saying the same things, so you never have to reconcile two documents against each other. Where wording overlaps, this page decides how...
Payments Page
That page lists settlement times for JazzCash, Easypaisa, SadaPay and Raast. Here we explain the transaction records those rails return to us and how long we keep them.
Cookie Notice
Cookies get their own short notice because they change more often than the rest of this policy. It names each tag we set and how you switch the optional ones off.
Security Page
Login checks, device recognition and password resets are described there. Here we cover only the data those checks create and the period we hold it for audit purposes.
Complaints Route
If you believe we have mishandled your data, the complaints route takes precedence over the general support queue, and we confirm in writing that your case is logged.
Language Versions
We publish this policy in English for Pakistan. Should a translation ever conflict with the English wording on this page, the English text is the one we stand behind.
Update Notices
Material changes reach you by email and by a banner inside your account before they take effect, so the policy you agreed to is never swapped out quietly beneath you.
What Sits at the Head of This Page
We laid this page out so the parts you need most arrive first. It opens with the revision date, then runs from how we collect data...
Revision Date
The page opens with the date of the last revision, so you can tell at a glance whether anything has moved since your previous visit or your account sign-up.
Plain Summary
A short summary sits above the full clauses, written in everyday English for Pakistan. It never replaces those clauses, but it tells you what each one deals with.
Jurisdiction Line
One line states that local law governs wherever it permits, which matters if a rule in your province asks for handling different from our standard process on your account.
Data Table
A single table sets out what we collect, why we hold it and how long it stays. Account details, transaction references and device logs each get their own row.
Rights Panel
Your access, correction and deletion options appear in one panel with the route for each. It links straight to the request form instead of making you hunt for it.
Contact Block
The closing block lists the privacy email, the chat hours and the address for written requests, so you never reach the end without knowing where to send a question.
Data Questions From Pakistani Accounts
Your name, date of birth, contact details and the identity documents needed to verify you, plus the transaction references JazzCash, Easypaisa, SadaPay or Raast send back when you move money.
Only with the partners needed to run your account: payment rails, identity-check services and the hosting that keeps the lobby online. We do not sell your details, and each partner is bound by contract.
Transaction records stay for the period local rules require for audit, usually several years after your last activity. Device logs are held far shorter, and account details go once a verified deletion request completes.
Yes. Write from your registered email asking for a data copy, and we confirm receipt, verify your identity and send the file in a readable format within the window local law sets.
Closing stops new collection and takes your profile out of the lobby, but records tied to settled transactions stay for the audit period. You can leave a deletion preference when you close.
We email every account before a material change takes effect, and the revision date at the head of this page moves each time. Smaller wording fixes are made without notice but are always dated.