How k11win Handles Your Personal Data
At k11win, your personal data belongs to you — we collect only what we need to run your account, process your deposits through JazzCash, Easypaisa, SadaPay or Raast...
What We Collect and Why We Hold It
When you open an account with k11win in supported regions of Pakistan, we collect your name, contact details, and payment identifiers linked to JazzCash, Easypaisa, SadaPay or Raast transactions. Session logs, device type, and IP address are retained to detect unauthorised access and maintain platform integrity. We do not collect data beyond what your account activity generates, and we do not sell
or rent personal records to external parties. Retention periods align with local financial record obligations where local law permits. You may request a copy of your stored data or ask us to correct inaccuracies by contacting our privacy desk at any time.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
The Standards Behind Our Privacy Commitments
We have built our data practices around six principles so you can verify our approach rather than simply take our word for it. Each commitment below reflects a concrete operational choice we...
Encrypted Storage
All account data — including payment method references for JazzCash and Easypaisa — is stored using AES-256 encryption at rest. Keys are rotated on a fixed schedule independent of account activity cycles.
Access Controls
Internal access to personal records is role-restricted. Staff who handle payment processing cannot view identity documents, and identity verification agents do not see full payment rail identifiers in their interface.
Breach Notification
If a data incident ever affects your account, we will notify you directly within 72 hours and explain what was exposed, what we did to contain it, and what steps we recommend on your side.
Third-Party Limits
Payment processors such as SadaPay and Raast receive only the minimum data needed to complete your transaction. They are contractually bound to the same retention and deletion standards we apply internally.
Cookie Transparency
We use session cookies to keep you logged in and analytics cookies to measure page performance. You can review and adjust cookie preferences from the footer of any page without affecting your account access.
Policy Review Cycle
This privacy policy is reviewed every six months. When material changes are made, we send an in-app notification and post a dated changelog so you can see exactly what changed and when.
How This Policy Aligns Across Our Platform
We apply the same data handling standards site-wide. The table below shows how the commitments in this policy match up with the practices described in our related policy...
| Account Registration Data | Collected at signup and governed by this policy; the same scope applies in our terms of service document. |
|---|---|
| Payment Rail Identifiers | JazzCash, Easypaisa, SadaPay and Raast references are handled identically whether the transaction originates from a deposit or a withdrawal flow. |
| Session and Device Logs | Retention periods stated here match the periods referenced in our cookie policy and account security documentation. |
| Third-Party Processors | Processor obligations described here are mirrored in the data processing addenda referenced in our terms document. |
| User Rights Requests | The seven-day resolution window applies across all request types — correction, access, and deletion — consistently with our support commitment policy. |
| Breach Notification Timeline | The 72-hour notification window stated here is consistent with the incident response commitment outlined in our platform security page. |
| Policy Update Notice | The six-month review cycle and in-app changelog notice described here match the update cadence stated in our terms of service. |
Key Elements Shaping How We Built This Policy
Six deliberate design choices define how our privacy framework feels to use. These are not aspirational statements — each one reflects a specific decision we made when building...