LEGAL REFERENCE

How p0ki handles your data

p0ki keeps casino, slot and sportsbook privacy terms in one clear place, so you can see how account, device, payment and support data is handled before you open...

Pakistan wordingAccount data scopePayment record contextSupport privacy path
p0ki How p0ki handles your data

Privacy terms for supported Pakistan access

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

HELP CHANNELS

Where to ask privacy questions

Privacy requests need a clear route, not a generic inbox. Use the contact path that matches your account status, and include enough...

Account help area Send us your privacy question from the account...
Email privacy request If you cannot enter your account, email us...
Payment record query For JazzCash, Easypaisa, SadaPay or Raast privacy questions...
CARE CHECKS

How we keep policy wording accurate

We write this policy from the systems we operate, not from a template detached from your account flow. The wording is checked against login screens, payment handling, withdrawal checks, support tooling and...

Policy owner

Our privacy text is maintained by the team that handles account verification, payments and support records. That keeps wording close to the actual screens you use, instead of separate legal wording.

Scheduled checks

We check this page after changes to login, KYC, payment routing or support tools. If a data category changes, we update the policy wording and publish the adjusted date.

Access control

Account records are limited to staff and service partners with a work need. Payment references, identity checks and support messages sit behind permission controls and activity logging.

Local context

Pakistan payment rails create specific records, such as JazzCash sender details, Easypaisa references, SadaPay account markers and Raast transfer IDs. We describe those records in plain English.

Retention checks

We keep records only for account operation, dispute handling, security, legal duties and audit needs. When retention is no longer required, we delete or anonymise data where practical.

Security alignment

The policy reflects security steps you can see, including password controls, device checks and account verification prompts. It also explains less visible safeguards used inside our systems.

How this page fits our legal set

Our Privacy Policy is written to sit beside other p0ki legal pages without conflicting wording. Each page has its own purpose, yet shared terms such as account, payment...

Same definitions
Terms such as account data, payment record and support message keep the same meaning across our legal pages. You should not see one page narrowing a term used more broadly elsewhere.
Cookie link
Cookie wording explains browser storage and measurement tools, while this policy explains the personal data connected to those tools. Together they show how device signals relate to your account.
Account terms
Account rules explain what you may do on p0ki. This page explains what data we collect while operating those rules, including verification, security checks and account communication.
Payment records
Payment terms cover transaction steps, timing and references. This policy explains how related personal data is stored, shared with processors, and used for payment or withdrawal checks.
Support transcript
Support wording explains how you contact us. The privacy page adds how chat messages, email threads and account help requests are stored, accessed and used to solve your issue.
Access controls
Security wording describes account protection. This policy connects that protection to data handling, including staff permissions, login monitoring, device checks and limits on internal access.
Change log
When we adjust legal text, we aim to keep changes visible through dates and clear wording. Privacy changes are separated from account rule changes to avoid confusion.
PAGE MARKERS

Visible privacy markers on this page

This section points out the layout elements we use to make privacy wording easier to act on. The page is built around short headings, local examples, contact paths...

Plain summary The opening section gives a short statement of what this...
Data map We group personal data by account, payment, device, support and...
Choice prompts Where your choices matter, we explain how to contact us...
Pakistan context Examples mention JazzCash, Easypaisa, SadaPay and Raast because those records...
Security labels Security references are placed near the data they protect, including...
Contact strip Privacy contact routes are kept near the policy text, so...

Privacy Policy questions for p0ki

We collect data needed to open and protect your account, including contact details, login activity, device signals, payment references, withdrawal requests and support messages you send through our contact paths.

Your mobile number helps us identify your account, connect local payment records, send important account messages and verify privacy requests. We do not use it to sell unrelated services.

We store payment references, timing and account markers needed to match your transaction with your p0ki balance. Extra screenshot details should be hidden before you send a support request.

Yes. Contact us through the account help area or privacy email, explain what should change, and complete any verification step. Some records may remain unchanged for audit or security reasons.

Retention depends on the record type. Account, payment, security and support records are kept while needed for operations, disputes, legal duties and fraud prevention, then deleted or anonymised where practical.

Yes, it may change when our account flow, payment processing, support tools or legal duties change. We update the wording and date so you can check what is current.