Privacy Policy
The page you are reading now: what we collect, why we collect it, how long it stays, and the deletion route you can use at any point.
This privacy policy spells out, in plain English, what we collect when you open a pkvip account, how we use it, and the controls that stay in your...
We write this policy for account holders in Pakistan and for anyone reaching pkvip from a supported region where local law permits access. Where local rules differ from ours, we apply the stricter standard and say so inside the clause itself rather than in a footnote. What we hold falls into three groups: what you give us when you register, what your
activity in the lobby generates, and what our payment partners return once a transaction settles. JazzCash, Easypaisa, SadaPay, NayaPay and Raast each pass back a reference number and a status, never a wallet credential. Clauses stay short, every change carries a date, and we never hide a shift of purpose inside a routine wording tidy-up. When a clause stops matching how we
actually operate, we rewrite it instead of leaving it standing.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
We treat this page as a document we have to live with, so it is checked on a fixed schedule and edited whenever operations change. Drafts come from the team that handles...
Every clause has a named team behind it, so a question about retention or transaction records lands with people who actually run that part of the platform.
We publish an effective date and keep earlier versions reachable, letting you compare what a clause said when you registered with what it says today.
JazzCash, Easypaisa, SadaPay, NayaPay and Raast references are stored against your account for reconciliation, and the policy states exactly how long each lasts.
Account pages and chat run over encrypted connections, and session tokens expire when you sign out. The policy lists what we encrypt and what we choose not to hold.
Access to account records follows role, so a support adviser sees your ticket history without seeing full transaction identifiers. Each lookup is written to an internal log.
When a clause shifts in a way that affects you, we flag it in your account dashboard before the new wording takes effect, with a line explaining what moved.
Our policy pages are drafted from one shared clause library, so the privacy policy, the account terms and the cookie notice agree with each other instead of clashing at the edges. Use...
The page you are reading now: what we collect, why we collect it, how long it stays, and the deletion route you can use at any point.
Covers the rules of holding a pkvip account, eligibility across supported regions, and what happens when you ask us to close your profile.
Explains the small files that keep you signed in, remember your language choice, and show us which lobby pages load slowly on your device.
Sets out how JazzCash, Easypaisa, SadaPay, NayaPay and Raast references are recorded, matched to your account, and retained for reconciliation.
Describes sign-in protection, session handling and the internal access limits that decide which colleague can open which part of your record.
Shows how to switch off promotional messages while keeping service notices, so a policy change still reaches you after you opt out.
Walks through what we can remove, what local record-keeping rules require us to hold on to, and how long the process usually runs.
A policy only helps if you can find the clause you came for. So this page carries an effective-date strip under the headline, a sticky index down the...