LEGAL REFERENCE

Privacy Policy for your pk3 account

Live casino tables, slots and sportsbook access all rely on the same account record, so this Privacy Policy explains how pk3 handles your data before you open an...

Account data useJazzCash contextSupport privacyDevice checks
Explore The Lobby Read FAQ
pk3 Privacy Policy for your pk3 account

How we handle your data

This Privacy Policy describes how pk3 collects, uses, stores and shares data connected to your account where local law permits. We collect details you give us, such as name, mobile number and support messages, plus technical records created when you access the lobby, request account help or use Pakistani payment rails. We use that data to run account access, confirm transactions, protect

sessions, answer privacy requests and meet legal duties that apply in supported regions. We do not sell your account record. Where service providers help us with hosting, verification, messaging or transaction handling, we limit what they receive to the work they perform for pk3.

Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.

PRIVACY HELP

Privacy help when you need it

You can contact us about this Privacy Policy before or after opening your account. We ask for enough detail to confirm control...

Email privacy desk Email our privacy desk from the address linked...
Live chat route Open live chat and ask for privacy support...
Account requests For account closure or copy requests, send one...
POLICY CHECKS

How our policy stays current

Our Privacy Policy is written from the way pk3 actually operates: account access, live table sessions, slot records, sportsbook entries, payment receipts and support tickets. We check policy...

Policy owner

A named internal owner keeps this Privacy Policy aligned with how our account, live casino, slots and sportsbook areas handle...

Change record

When we adjust wording, we record the reason, the date and the affected clause. That helps us answer your privacy...

Payment mapping

JazzCash, Easypaisa, SadaPay and Raast references are checked against the data we actually receive, such as sender name, mobile number...

Access checks

Your login records, device signals and session status are covered because they protect account access. We describe these data points...

Plain English

We write the policy for Pakistan in clear English, not legal theatre. Where a clause has a technical term, we...

Support loop

Questions sent to support are tracked back into policy edits when wording causes confusion. That keeps the page useful for...

Consistent privacy terms across pk3

This page works with our other legal pages without repeating them. The Privacy Policy focuses on personal data, while related pages explain account conduct, cookies, promotions and contact...

Terms pageOur account terms explain what you may do on pk3. This Privacy Policy instead explains which personal data supports those account rules, such as login records, identity checks and contact history.
Cookie pageThe cookie page deals with browser storage and measurement tags. This Privacy Policy connects those records to account security, device recognition and the choices available when cookies are not essential.
Promotions pagePromotion rules may mention eligibility and account status. This page explains how pk3 uses your account data to apply those rules without exposing your personal record to unrelated areas.
Payment termsPayment terms explain transaction steps and timing. This Privacy Policy explains the data trail behind those steps, including wallet references, bank rails, support screenshots and verification checks.
Security pageSecurity text focuses on protecting access. The privacy wording explains the data used for that protection, including login time, device details, IP signals and changes to account credentials.
Support pageSupport pages show how to reach us. This Privacy Policy explains how we handle the messages, attachments and contact numbers you share when asking for account or privacy help.
Regional accessWhere access depends on supported regions, the related page explains availability. This Privacy Policy explains how we may use location signals and account records to apply those access rules.
VISIBLE CUES

Privacy cues across the page

We design the Privacy Policy page so you can scan the data story quickly before going deeper. Headings, chips and cards separate account data from payment references, device...

Clear section labels Each section label names the privacy subject before the paragraph...
Local context chips Short chips call out JazzCash, Easypaisa, SadaPay and Raast only...
Short request paths Contact cards separate email, chat and account requests. That helps...
Data purpose wording We pair data types with reasons, such as session protection...
Device-aware wording Mobile and desktop access can create different signals. The policy...
Update visibility When this Privacy Policy changes, we make the new wording...

Privacy Policy questions we answer

We collect the details needed to create and protect your account, such as name, mobile number, login records and contact details. We may also record device signals and region checks where local law permits.

Those names appear because payment references can become part of your account record. We may store transaction IDs, sender details, timing and support screenshots to match funds and answer account questions.

We share limited data only when a service helps us run account access, hosting, verification, messaging or transaction handling. Each provider receives only what it needs for that task.

We keep records for as long as needed for account operation, legal duties, dispute handling and security checks. When data is no longer needed, we delete it or reduce it where practical.

Yes, you can contact privacy support from the email or number linked to your account. We confirm control first, then explain what data can be shared and any lawful limits.

Support messages are routed through controlled tools, and sensitive fields may be masked when a case moves between teams. We use the messages to answer your request and maintain account safety.

We update the page wording and keep the current version visible. If a change affects how pk3 uses your data, our support team can point you to the relevant section.