How We Handle Your Privacy
pk966 keeps privacy choices close to your account flow, so you can see how your data is collected, used, stored, and requested. Before you open an account, read...
Our Privacy Position in Pakistan
Our privacy posture starts with only collecting the account data we need to run pk966, keep access secure, and process requests where local law permits. When you open an account, we may record contact details, login activity, device signals, game session records, and transaction references linked with JazzCash, Easypaisa, SadaPay, or Raast. We do not sell your account data. We share it
only with service partners who help us run security checks, payment routing, support, and legal requests. You can ask us to access, correct, or update your account data, and we will respond through the contact path linked to your account after identity checks are complete. This policy also explains retention periods, cookie use, and how we handle privacy requests from Pakistan.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
How We Check Policy Accuracy
We treat the Privacy Policy as an operating document, not a decorative page. Our team checks it against account screens, support scripts, cookie behaviour, and payment reference handling so the wording matches...
Account flow check
We compare policy wording with the data fields you complete when opening your account. If a field changes, the privacy wording is checked before the page is refreshed.
Cookie record
Cookie and device-signal wording is matched with the scripts we run for login security, session stability, and fraud checks, so the policy reflects actual site behaviour.
Wallet reference check
JazzCash, Easypaisa, SadaPay, and Raast references are described as transaction identifiers, not wallet access. We check this wording whenever routing or verification steps change.
Support training
Our support team uses the same privacy terms shown on this page, so you hear consistent wording when asking about account data, correction requests, or retention periods.
Retention schedule
We connect each data category with a retention reason, such as account security, transaction records, dispute handling, or legal requests where local law permits access.
Change record
Material privacy edits are tracked with the date, reason, and section affected. That helps us explain what changed when you ask about an updated policy term.
Aligned Privacy Pages Across pk966
Your privacy rights should not change from one legal page to another. We keep related pk966 pages aligned, so the Privacy Policy, cookie wording, account terms, and support...
| Cookie wording | Cookie language stays aligned with this Privacy Policy, including login security, session tools, preference storage, and analytics used to keep the site stable across devices. |
|---|---|
| Account terms | Account terms explain conduct rules, while this policy explains data handling. We keep both pages linked so you can see why certain checks require account records. |
| Security page | Security wording supports this policy by explaining password care, login alerts, and device checks. Privacy wording covers what data is collected during those checks. |
| Support scripts | Support replies are matched to this policy, so your questions about access, correction, retention, or data sharing receive the same privacy meaning across contact channels. |
| Payment references | Wallet references in other pages stay limited to transaction matching. This policy explains how those references may be stored, checked, and protected with account records. |
| Promotion records | If we record eligibility or account status for a site offer, this policy explains how that record is used, stored, and removed when no longer needed. |
| Legal requests | Any page mentioning lawful disclosure is kept consistent with this policy. We only share account data for valid service, security, or legal reasons where required. |
Privacy Layout You Can Read
The Privacy Policy is arranged so you can scan rights, data categories, sharing reasons, and contact steps without hunting through unrelated copy. We use short sections...
Visible update date
The page shows when the Privacy Policy was last changed, so you can tell whether the wording has moved before you continue with account access.
Plain section labels
Each privacy section uses direct labels for collection, use, sharing, retention, cookies, and contact. That keeps the legal wording easier to scan on mobile.
Rights summary
Your access, correction, and update options are gathered in one area. We explain what we need from you before we can act on a request.
Sharing explanation
We separate internal use from service-partner sharing, so you can see when data supports account security, transaction matching, support, or lawful request handling.
Cookie clarity
Cookie wording explains session tools, device checks, and preferences in plain English. We avoid mixing cookie use with unrelated lobby copy or promotional language.
Contact placement
Privacy contact paths sit near the policy sections they affect, helping you ask for access, correction, or deletion without searching around the whole site.