LEGAL REFERENCE

Privacy Policy for your pk365 account

pk365 online keeps your account, KYC, session and payout data in one privacy flow, so you can see what we collect and why before you open an account...

Pakistan data handlingKYC claritySession controlsPayout checks
pk365 online Privacy Policy for your pk365 account

How we handle your personal data

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

CONTACT ROUTES

Where to ask privacy questions

If you want to ask about this Privacy Policy, update account details, or question a data entry connected to payments or identity checks, contact us from inside your account where possible. Logged-in messages help us match your request to the correct record without asking you to repeat sensitive details.

Team online

Account inbox

Use the message area after sign-in for privacy requests tied to your profile, KYC file, login history or payout checks. We can connect the request with your account trail more safely there.

Email contact

If you cannot access your account, email our privacy contact with your registered phone or email, not full card, wallet PIN or ID images unless we specifically ask through a secure route.

Live help handoff

Our live help team can route privacy questions to the right internal desk. They may confirm basic account markers before escalating, so your data request reaches staff with the correct access level.

DATA CARE

Checks behind this policy wording

We write this Privacy Policy around how our service actually works: account opening, KYC checks, wallet references, device security, game session records and support contact. Each policy update...

Operational wording

Our policy terms are mapped to real account steps, including sign-in, verification, wallet linking and payout approval. That keeps the...

Access control

Internal access to personal data is limited by work role. Support, payments and risk staff see only the records needed...

Payment references

JazzCash, Easypaisa, SadaPay and Raast records may be kept as transaction references. We use them to match account activity, resolve...

Device signals

We may record device type, browser, IP address and session timing to detect unusual access. These signals help us protect...

Policy updates

When we change this Privacy Policy, we adjust the page date or message you through account channels where the change...

Local wording

We use clear Pakistani English and name the payment rails you recognise. That helps you understand how privacy terms connect...

How this page aligns with our terms

This Privacy Policy works beside our account terms, cookie wording and support rules. Each page has its own job, but we keep definitions aligned so you do not...

Account terms
Our account terms explain your use of pk365 online, while this policy explains how personal data supports that use. The two pages share wording for account records and verification.
Cookie wording
Cookie wording covers browser storage, device markers and preference tools. This Privacy Policy explains the wider data picture, including how those signals may support security and service operation.
KYC process
Identity checks may include name, date of birth, contact details and documents requested for verification. This policy explains why those records are collected and how access is limited.
Payment records
Wallet and bank references are treated as account records, not public profile details. We use them for transaction matching, payout checks, reconciliation and support when you raise a query.
Security logs
Security logs may include login time, IP data, failed access attempts and device changes. These records help us investigate account concerns and reduce unauthorised access risks.
Support history
When you contact us, we may keep the conversation, account markers and resolution steps. This helps us answer follow-up questions without asking for the same details again.
Retention rules
We keep records only for business, legal, security or dispute reasons. When data is no longer needed, we remove it or reduce it where our systems allow.
PAGE MARKERS

What this privacy page makes clear

This page is built to help you decide whether to share personal data with pk365 online. Instead of burying key points, we separate collection, use, storage, sharing and...

Clear data categories We separate account data, identity data, device data, transaction references...
Plain purpose wording Each use of personal data is tied to a purpose...
Sharing boundaries The policy explains when service partners may handle data for...
Account control route You can ask to correct details, question a record or...
Security explanation We describe how login records, device signals and internal access...
Pakistan context The page names Pakistan payment rails where relevant and uses...

Questions about your data rights

We may collect your name, contact details, login records, device signals, KYC material, wallet references, transaction history and support messages. The exact data depends on how you use your account.

Identity details help us confirm account ownership, manage payout checks, reduce fraud and meet record duties that apply to our service. We request them only when needed for those purposes.

No. We do not sell your personal data. We may share limited records with service partners that help with hosting, verification, payments, security checks or support delivery.

JazzCash and Easypaisa references may be used to match transactions with your pk365 online account, confirm payout status, resolve payment queries and maintain audit trails required for account operations.

Yes. Contact us through your account inbox or privacy email and explain what needs correction. We may ask for verification before changing sensitive details linked to identity or payouts.

We keep data for as long as needed for account operation, legal records, security checks, disputes and payment reconciliation. When retention is no longer needed, we remove or reduce records where possible.

This Privacy Policy applies to pk365 online, but access, data handling and payment availability can differ by supported regions and local law. We may adjust processes to meet applicable requirements.