Collection
This policy explains the personal details and technical signals we may collect. It does not create a new request for data beyond what your account or a specific transaction requires.
LEGAL REFERENCE
Privacy Policy For Your kk v lq Account
This Privacy Policy explains how we collect, use, protect and retain information connected with your kk v lq account in Pakistan. It covers account access, identity checks, payment...
Clear data usePakistan contextAccount choicesSecure handling
How We Handle Personal Data
We collect details you provide when opening or maintaining an account, including your name, contact details, date of birth, login credentials and verification records. We also receive transaction references from supported rails such as JazzCash, Easypaisa, SadaPay and Raast, while payment providers retain their own records under their terms. Technical data may include IP address, browser type, device identifiers, session events and
security signals. We use these details to provide account access, process requested transactions, prevent misuse, answer support requests, maintain service security and meet legal obligations where local law permits. We retain records for as long as needed for these purposes, then delete or anonymise them when practical. You may ask about access, correction or deletion, subject to legal and security limits. Questions
about this policy can be sent through our listed support paths.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
WHY THIS POLICY
Practical Signals Behind Our Approach
This policy reflects the data flows we operate every day: account creation, sign-in protection, payment matching, transaction checks and customer support. We describe those flows in plain Pakistani English so you can...
Account Records
Your profile data helps us connect sign-in activity, requested services and support history. We limit internal access to roles that need the record for account operation, security or legal handling.
Payment Matching
JazzCash, Easypaisa, SadaPay and Raast references help us match a requested transaction with your account. We do not ask you to share a provider password or private security code.
Security Signals
Device, browser and network signals help us identify unusual access patterns. These checks can trigger an additional confirmation when account activity differs from your normal sign-in pattern.
Verification Steps
When identity confirmation is needed, we use the submitted details to compare account ownership and transaction context. Verification records remain restricted and are retained only for a valid operational or legal reason.
Support Records
Messages with support may be stored so we can follow an issue from first contact to resolution. We use the conversation for service handling, security checks and continuity across related requests.
Regional Access
We use location and network indicators to apply access controls for supported regions. These signals do not replace your responsibility to check whether access is lawful where you are located.
POLICY CONSISTENCY
What This Policy Covers Differently
Privacy questions often overlap with account, transaction and security matters, but this page stays focused on personal data. The distinctions below show where this policy applies and when another account process may...
Use
We use stored details to provide access, protect accounts, handle support and meet legal duties. We do not describe unrelated advertising purposes as part of this policy.
Sharing
Data may be shared with service providers when they help process payments, host systems, verify identity or secure access. Their handling remains subject to their own published terms.
Retention
Retention depends on the record type, security need and applicable legal duty. When a record no longer serves a valid purpose, we seek deletion or anonymisation where practical.
Your Requests
You can ask about access, correction or deletion through support. We may limit a request where fulfilling it would expose another person, weaken security or conflict with a legal duty.
Policy Changes
If our data practices change, we may update this page and show a clearer notice at account entry. The updated date and revised wording should be checked before continued use.
Third Parties
A payment provider, identity service or device service may handle data under its own terms. This page explains our role and cannot replace the terms of those separate services.
Key Privacy Details At A Glance
The layout of this policy is designed to help you find practical answers without searching through unrelated account material. Each panel points to a distinct privacy...
Purpose First
We connect each requested detail with a stated purpose such as access, security, transaction handling or support. This helps you understand why a field or signal may appear during account activity.
Local Context
Pakistan account flows may involve JazzCash, Easypaisa, SadaPay or Raast references. We describe those references as transaction data, not as permission to access your private provider credentials.
Choice Points
You can ask what we hold about you, request a correction or seek deletion where the law and account security allow. Support may need to confirm ownership first.
Security Layer
Sign-in records, device signals and verification events help us investigate suspicious access. These controls are used to protect your account and may lead to an extra confirmation step.
Plain Language
We avoid technical wording where a direct explanation works better. The policy separates collection, use, sharing, retention and requests so each privacy decision has a clear place.
Updated Access
This page remains available as a reference for your account journey. When material wording changes, we may draw attention to the updated section before you continue using the service.
Privacy Answers For Your Account
We may collect account details, contact data, verification records, transaction references, support messages and technical signals such as device, browser, network and sign-in activity.
Identity details help us connect an account to its owner, protect access, investigate unusual activity and handle legal or transaction duties where local law permits.
No. We use transaction references supplied through the relevant payment flow. You should never send a provider password, PIN or one-time code to our support team.
You may contact support to ask what personal data we hold about you. We will verify account ownership and may withhold details that could expose another person or weaken security.
Yes, you can request correction or deletion where applicable. Some records may need to remain for security, transaction history or legal duties, and we will explain any relevant limit.
Retention varies by record type and purpose. We keep data while it supports account operation, security, support or legal duties, then seek deletion or anonymisation when practical.
We may update this page when our data practices change and may present a notice at account entry. Check the revised wording and updated date before continuing where the change matters.