LEGAL REFERENCE

Privacy Policy For Your prk365 Account

This Privacy Policy explains how prk365 handles personal data when you open an account, use our casino, slots or sportsbook areas, contact support, or request account services. We...

Clear data purposesPakistan-focused wordingAccount securityYour privacy choices
Explore the Lobby Read FAQ
prk365 Privacy Policy For Your prk365 Account

How We Handle Personal Data

We collect details you provide during account creation, such as your name, mobile number, email address, date of birth and identity material requested for account checks. We also receive technical data including device type, browser details, IP address, session activity and security events. We use this data to create and maintain your account, process authorised account transactions, prevent misuse, answer enquiries, meet

applicable legal duties and improve privacy controls. Payment references from JazzCash, Easypaisa, SadaPay, NayaPay or Raast may be retained to match a request with your account, while full wallet credentials are not stored by us. We restrict access to personnel and service providers who need it for defined tasks, apply retention periods based on purpose and legal requirements, and remove or anonymise

data when it is no longer needed. Access may be limited in supported regions where local law requires it.

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

PRIVACY CONTACTS

Reach Us About Your Data

You can contact prk365 when you want to ask how your data is used, request a correction, question an account check or...

Privacy email Send a privacy request through the contact address...
Account chat Use our in-account support chat for questions about...
Verification help If an identity check affects your request, our...
OUR PRIVACY PRACTICE

What Shapes This Policy

Our privacy approach follows the way prk365 actually operates: account access, regional availability, payment matching, security monitoring and customer assistance each create different data needs. We separate these...

Purpose-based collection

We ask for account details when they serve a stated purpose, such as opening access, confirming ownership, handling a transaction...

Security records

Login times, device signals and unusual access patterns can help us identify account takeover attempts. These records support protective action...

Payment references

When you use JazzCash, Easypaisa, SadaPay, NayaPay or Raast, we may receive a reference, amount, status and related account identifier...

Support records

Messages, attachments and case outcomes may be kept so we can resolve repeat questions, protect account ownership and demonstrate how...

Regional controls

Your country, network signals and account details may be used to apply access rules for supported regions. Where local law...

Policy accountability

We keep this page aligned with our current data practices and may update it when services, legal duties or security...

How This Policy Fits Together

This page is the central privacy statement for prk365 account activity, but some services may show a short notice at the moment data is collected. Those notices work...

Account creation
The account notice explains the details needed to create access, confirm your mobile number and protect ownership. This policy adds the wider context, including storage, sharing, retention and your available requests.
Payment activity
A transaction prompt may identify the data needed to match JazzCash, Easypaisa, SadaPay, NayaPay or Raast activity. This page explains the privacy handling around those references after the request is submitted.
Security events
A security message may tell you that an access check is taking place. This policy explains why device, network and session signals can be used to detect suspicious activity and protect your account.
Support conversations
The support notice applies when you send a message or attachment. This policy explains how case records may be accessed, retained and connected with earlier requests to resolve an account issue.
Regional access
A location or availability notice may apply where local law limits access. This policy describes the related data use without changing the legal conditions that apply in your supported region.
Policy updates
When this policy changes, the updated wording will show the new effective date. A service notice may also appear if the change affects a data request made during account use.
Your requests
A request submitted through support is handled under this policy even when it concerns a particular feature. We may confirm identity first, then respond within a period allowed by applicable law.
PAGE FEATURES

Privacy Details At A Glance

We designed this policy page to make important privacy points easier to locate without turning them into dense legal blocks. Each visual element points back to a specific...

Purpose cards Short cards separate account, security, support and transaction purposes so...
Local terms References to Pakistan, supported regions and local wallet services make...
Request path The contact area shows where to send a privacy question...
Security focus Account protection is presented beside data handling because login signals...
Update marker The effective-date treatment helps you identify whether you are reading...
Plain language We use direct Pakistani English for the main explanations and...

Questions About Your Privacy

We may collect your name, mobile number, email address, date of birth, account credentials, identity material requested for checks, device details, network signals, support messages and transaction references linked to your account.

Identity details help confirm account ownership, protect against misuse, address suspicious access and meet applicable legal duties. We request the document category needed for the stated check and restrict access to authorised personnel.

No. When you use JazzCash, Easypaisa, SadaPay, NayaPay or Raast, we may retain transaction references and status details needed for reconciliation. Your wallet password, PIN and one-time code should never be shared with us.

Yes. Contact us through the listed privacy email or in-account chat, identify the record that needs correction and provide suitable account context. We may verify ownership before changing personal details.

Retention depends on the record’s purpose, security needs, dispute handling and applicable legal duties. We remove or anonymise data when it is no longer needed, unless a lawful reason requires continued storage.

We may share limited data with service providers that help operate account, security, support or transaction processes, and with authorities where legally required. Partners receive access suited to their defined task.

The current page will show its effective date. If an update materially changes how your data is handled, we may also use an account message or another available contact channel to draw your attention to it.