Registration Flow
Data collected during account opening follows the same minimal-collection rule stated here — no extra fields, no silent opt-ins.
This policy explains exactly what account data kk vs collects, how we use it, and the controls you hold over it. We wrote it for you — not...
This privacy policy applies to all account holders and visitors accessing kk vs through supported regions where local law permits. We collect the minimum data needed to operate your account: your registration details, session logs, and payment identifiers linked to JazzCash, Easypaisa, SadaPay, and Raast transactions. We do not store full payment credentials — only the masked references returned by each payment
rail after a transaction clears. Your data is processed on servers subject to encryption at rest and in transit. We share nothing with third parties unless legally compelled or required to process your withdrawal through the payment provider you selected. You may request a full export of your stored data at any time through our support channel.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Our privacy support team handles data access requests, correction requests, and deletion requests within 5 business days. Reach us through any of the channels below and quote your registered account email for faster routing.
Open the chat widget from your account dashboard to speak with our privacy support team directly. We handle data queries during Pakistan standard business hours, seven days a week.
Send your data request to our dedicated privacy address. Include your account identifier and the specific data action you need — export, correction, or deletion — and we respond within 5 business days.
Our help centre carries step-by-step articles on submitting data requests, understanding what we store, and managing your communication preferences directly from your account settings panel.
We measure our privacy posture against concrete practices you can verify, not marketing claims. Each item below reflects an operational control we keep running on your behalf.
All data moving between your device and kk vs servers travels over TLS 1.3. This applies to login, account updates...
We collect only what is needed to open and operate your account. Fields not required for verification or payment processing...
When you transact via SadaPay, Raast, JazzCash, or Easypaisa, we retain only the masked reference the payment provider returns. Full...
Your account data is accessible only to staff with an operational need. Access logs are audited monthly, and any unusual...
Session logs are purged after 90 days. Closed account records are retained only as long as legal and financial obligations...
You may request full deletion of your account data at any time. Once verified, we action the deletion within 30...
Our privacy commitments are not limited to this page. The same data handling rules apply across every section of kk vs — from account registration through to withdrawal — so you can...
Data collected during account opening follows the same minimal-collection rule stated here — no extra fields, no silent opt-ins.
Payment screens for JazzCash, Easypaisa, SadaPay, and Raast apply the same masking policy described in our details section.
Withdrawal data is handled under identical retention limits — references stored, full credentials never retained.
Your communication preferences and personal details are editable at any time, and changes take effect immediately across all systems.
Cookie and session data collected during browsing follows the 90-day purge cycle regardless of which part of the platform you visited.
If you opt into any communications, your contact data is used only for that purpose and is not shared with unrelated third parties.
Closure requests trigger the same 30-day deletion process described in this policy, applied uniformly to all stored data categories.
Our approach to privacy is structural, not cosmetic. The six principles below describe the design decisions we made when building the account and data layer at...
Every data field in our account system was evaluated against a necessity test. If a field did not serve account operation, identity verification, or payment processing, it was removed from the form entirely.
Data collected for one purpose — say, verifying your Easypaisa withdrawal — is not repurposed for analytics, marketing profiling, or any function beyond the original collection reason.
Our database schema enforces automatic expiry on session records and inactive data fields. Retention is not a policy document promise; it is a scheduled database job that runs without manual intervention.
You can update your registered name, contact address, and linked payment references from within your account settings at any time. We aim to reflect corrections across all systems within 24 hours.
New account features ship only after a data-handling review. Any feature that would expand the data we collect requires a documented justification before it reaches production.
Our internal privacy log records every data access event, every deletion action, and every third-party data transfer. This trail is retained for two years and is available to regulators on request.