Privacy Policy for your k99 account
k99 keeps your privacy choices, account data and Pakistan payment records in one clear Privacy Policy, so you know what we collect before you open an account in...
How we handle your account data
On k99, privacy starts with the account details you give us, the device signals created when you access the site, and the transaction records tied to your chosen Pakistan payment rail. We use that data to create your account, protect access, process cash-in and withdrawal requests, answer support messages, and meet checks that apply where local law permits. Some records may be
kept for audit, dispute handling, fraud control, or tax and reporting duties in supported regions. We do not write the Privacy Policy as a blanket consent form. It explains what we collect, why we need it, how long we usually keep it, and how you can ask us to correct, access, or remove eligible data.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
How we keep policy text dependable
We keep this Privacy Policy practical by matching it to the way k99 actually works in Pakistan. The wording is checked against account forms, support flows, payment records, session logs, and withdrawal...
Operational drafting
Our policy wording follows the account journey we operate each day, from phone verification to payment matching. We avoid vague promises and describe the real records created when you use k99.
Payment record mapping
JazzCash, Easypaisa, SadaPay, and Raast records are treated as transaction data, not public profile content. The policy explains why references, amounts, timestamps, and status changes may be stored.
Access control
Only staff with a work need can view sensitive account fields. We use role-based access, session controls, and internal logging to reduce unnecessary exposure of your personal data.
Retention checks
Some records are short-lived, while payment and dispute data may need longer retention. The policy separates routine storage from legal or fraud-control reasons that require longer keeping.
Request handling
When you ask for a copy or correction, we confirm identity before acting. That step protects you from someone else trying to change or collect your account records.
Change tracking
We keep the policy aligned with live account screens and support scripts. If a privacy term changes, we mark the page so you can see what is different.
One standard across privacy pages
Your privacy rights should read the same wherever you meet them on k99. We connect this page with our cookie text, account terms, and support replies so the...
| Account terms link | Our account terms describe eligibility, access, and conduct. This Privacy Policy sits beside those terms and explains the data we collect to apply them fairly in supported regions. |
|---|---|
| Cookie text match | Cookie wording explains browser storage and session tools. This page adds the wider privacy context, including why we use device signals for account security and site performance. |
| Payment wording | Payment pages may show JazzCash, Easypaisa, SadaPay, and Raast fields. This policy explains how related references and status records are stored after you submit them. |
| Support scripts | Support replies should not ask for more data than needed. Our privacy wording helps agents request only the account details required to solve your privacy or security matter. |
| Identity checks | If a withdrawal or account change needs identity confirmation, this policy explains the reason. The aim is to protect your account while collecting only relevant proof. |
| Change notices | When privacy wording changes, we keep the page date and linked text aligned. You can revisit this page to see the current version before continuing. |
| Regional access | Access may depend on supported regions and where local law permits. This policy uses the same regional wording as our account pages to avoid mixed messages. |
What you see on this page
This Privacy Policy is built to be scanned before you create or manage a k99 account. The layout highlights the data categories, reasons for use, request...
Clear opening badges
The badges near the heading point to account data, Pakistan scope, and request routes. They help you spot the privacy areas that may affect your next account action.
Plain data categories
Sections separate identity details, contact data, device signals, and transaction records. That structure makes it easier to see which data comes from you and which is created by site use.
Purpose-first wording
Each clause explains the reason for collection before naming the related record. You can see whether data supports login safety, payment matching, support replies, or legal duties.
Request route markers
Contact paths are placed close to the rights wording, so you do not need to search through account menus. We show how to ask for access, correction, or deletion.
Update date area
The page keeps a visible change area for privacy wording. If we adjust data handling language, that marker helps you notice the change before continuing with k99.
Readable clause blocks
Long legal points are broken into shorter blocks with direct headings. The goal is simple reading on mobile while still preserving the detail needed for privacy decisions.