Account data terms
Names for account details stay aligned across pages, so your email, mobile number, login records, device signals and verification files are described in the same way wherever privacy is discussed.
Your w2k17 account data is handled through clear privacy steps before you open the lobby in supported regions. Read how we collect, use, protect and share account details...
This Privacy Policy explains how w2k17 handles your personal data when you create an account, verify access, browse the lobby, contact us, or use wallet rails where local law permits. We collect only the details needed to run your account flow, protect access, process wallet requests, respond to support cases, and meet operational checks linked to Pakistan. That may include your name,
mobile number, email, login records, device signals, transaction references, chat messages, and verification documents when required. We do not sell your personal data. We share limited data with service partners only when they help us provide account security, wallet processing, fraud checks, hosting, analytics, or customer care under our instructions.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
If you need help with privacy matters, contact us from the same account details you use with w2k17. That helps us match your request safely before we change, export, restrict or remove data linked to your profile.
Use in-account chat for quick privacy questions after login. We can confirm the account, check recent data activity, and route your request without asking for extra copies of details we already hold.
Email us when your privacy request needs documents, longer context, or a written reply. Include your account email and Pakistan mobile number, but never send wallet PINs or one-time codes.
For JazzCash, Easypaisa, SadaPay or Raast references, share only the transaction ID, date and amount. We use those details to locate records without exposing unrelated wallet history.
We maintain this policy as part of our account operations, not as decoration. When data flows change, we check the wording against support practice, wallet handling, security logs...
Our privacy wording is checked against the way w2k17 accounts actually work, including login records, device checks, wallet references, support...
We avoid legal fog where we can. Each section explains what data is collected, why we need it, who may...
Policy language is matched with account-security controls such as session monitoring, password resets, device signals, access alerts and restricted staff...
References to JazzCash, Easypaisa, SadaPay and Raast are included only to explain privacy handling around transaction records, verification checks and...
When we adjust the policy, we keep internal change records so our support team can answer which privacy wording applied...
Access language uses supported regions and where local law permits because privacy rights, data requests and account availability can vary...
Your privacy experience should not change from page to page. We align this policy with our cookie, terms, security and account notices so the same data categories, request channels and wallet references...
Names for account details stay aligned across pages, so your email, mobile number, login records, device signals and verification files are described in the same way wherever privacy is discussed.
Cookie language connects back to this privacy policy by explaining browser signals, session cookies, analytics tags and preference records as data used to run secure account access.
Security notices use the same privacy categories for password resets, device checks, fraud screening and session alerts, helping you understand why some account signals are recorded.
Where another page mentions JazzCash, Easypaisa, SadaPay or Raast, it follows this policy by treating transaction IDs and status logs as account data.
Our support replies use the same privacy request routes as this page, so you are not pushed between different teams for correction, access or removal questions.
Retention wording stays consistent across sibling pages by tying storage time to account operation, dispute handling, security checks, legal duties and wallet record needs.
Policy pages are kept in sync through internal checks, so changes to data handling, contact routes or region wording do not leave older language active elsewhere.
We designed this page so privacy details are easy to find before you open or manage an account. The layout separates data categories, purposes, sharing, storage, rights and...