How pk14 handles your privacy
pk14 keeps the Privacy Policy close to your account flow: what we collect, why we use it, and how you can reach us. Before you open an account...
Our privacy posture for Pakistan
We apply this Privacy Policy to personal data connected with your pk14 account, site access, casino session records and support contact, where local law permits. We use your data to run account access, verify requests, process payments, protect the service from misuse and answer privacy questions. We do not write this page as a broad product pitch; it explains privacy handling only.
Pakistani payment references such as JazzCash, Easypaisa, SadaPay and Raast may appear in records when you choose those rails, but the policy focus is the data around the transaction, not the rail itself. Some checks may require identity details, device signals, IP records, timestamps or support messages. We keep retention periods tied to legal duties, dispute handling and account safety needs.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
How to reach us about privacy
Privacy requests should be easy to send and easy for us to trace. We connect your request to the account or contact detail you provide, then ask for enough verification to avoid handing data to the wrong person. Choose the route that matches your current access.
Live chat
Use live chat after login when your privacy question relates to account records, session history or a recent verification step. We may ask for account markers before discussing personal data.
Email request
Email is suitable for access, correction or deletion requests when you need a written trail. Include your registered contact detail, but avoid sending unnecessary identity files first.
Account centre
Your account area may show editable profile fields and recent contact details. Updating those fields helps us keep privacy responses linked to accurate account data.
How we keep this policy reliable
We treat privacy wording as an operating control, not decoration. When site flows change, we check whether this page still matches how account data, device records, payment references and support messages move...
Named policy owner
Internal ownership keeps this Privacy Policy tied to real account processes. Changes are checked against login, verification, support and payment-reference flows before wording is updated.
Data map checks
We map personal data from sign-in, casino sessions, support tickets and payment references. That map helps us explain collection purposes without stretching beyond actual pk14 operations.
Access control
Staff access to personal data is limited by role. Support can handle account questions, while deeper records need additional internal permission and logged handling steps.
Retention alignment
We keep data only for account operation, legal duties, dispute response and service protection. When a record is no longer needed, we aim to remove or anonymise it.
Local wording
The policy uses Pakistan context in plain English, including JazzCash, Easypaisa, SadaPay and Raast references when relevant. We avoid vague wording where specific examples help.
Change record
Material privacy updates are dated so you can see when wording changed. We may also place a notice near account access if a change affects your choices.
How related policy pages stay aligned
Privacy terms do not sit alone. We keep this page aligned with account terms, cookie wording and security notices so you do not see conflicting explanations. If another...
| Terms link | Our account terms explain service rules, while this Privacy Policy explains personal data handling. Where the same flow is mentioned, the privacy explanation stays focused on data use. |
|---|---|
| Cookie wording | Cookie text covers browser storage and similar tools. This policy connects those tools to wider privacy purposes such as login continuity, fraud checks and preference handling. |
| Security notice | Security wording explains safeguards at a higher level. The Privacy Policy adds why certain data, such as device signals or IP records, may support those safeguards. |
| Payment records | Payment pages may mention rails such as JazzCash or Raast. This page explains how related references can appear in account, verification or dispute records. |
| Support scripts | Support replies should match this policy when privacy questions arise. We train teams to avoid giving wider data promises than this page actually supports. |
| Account settings | Profile settings let you change some visible details. This policy explains when changes are instant and when records remain for security, legal or dispute needs. |
| Change notices | If privacy wording changes, related pages should not contradict it. We check linked copy so account decisions are made from consistent data explanations. |
Privacy layout you can scan
We design this privacy page so you can find practical answers without reading unrelated casino copy. The layout separates data categories, reasons for use, request routes and update...