LEGAL REFERENCE

Privacy Policy for your account

pak365.com keeps your privacy choices close to the account flow, so you know what we collect before you open your account. This Privacy Policy explains how we handle...

Account data explainedCookie choices includedJazzCash contextSupport record handling
Explore The Lobby Read FAQ
pak365.com Privacy Policy for your account

How we handle your details

This Privacy Policy applies when you use pak365.com where local law permits. We collect details you provide during account opening, security checks, payment matching and support conversations. We also record technical signals such as device type, browser language, session timing, IP range, cookie identifiers and page actions so we can keep your account accessible and investigate unusual access. Payment references from JazzCash,

Easypaisa, SadaPay and Raast are used to match transactions with your account ledger; we do not publish those references inside lobby pages. Where we use service partners for hosting, analytics, payment routing or support tools, we share only the fields needed for that service and keep access tied to role permissions.

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

CONTACT PATHS

Where to ask privacy questions

Your privacy requests should reach a person who can trace account records without asking you to repeat sensitive details in open chat. We separate general account help from privacy requests, then verify account ownership before sharing or changing personal data. If you contact us, include your account email or phone and the request type, not full card numbers or wallet PINs.

Team online

Live chat privacy queue

Use live chat for quick privacy questions about cookies, account access or payment reference matching. Our team may ask for a short identity check before discussing account-specific records or changing contact preferences.

Email request channel

Send longer privacy requests by email when you need a written trail. We use your message to locate account records, confirm ownership and reply with the action taken or the reason more detail is needed.

Account security escalation

If you think another person accessed your account, contact support immediately. We can check login history, device changes and payment reference activity, then limit account access while the issue is examined.

POLICY CHECKS

How we keep this policy current

We write this Privacy Policy from the way pak365.com actually operates, not from a blank template. The policy is checked against account forms, payment screens, cookie tools, support...

Account form mapping

We map each field shown during account opening to a privacy purpose, such as identity matching, account recovery or contact...

Payment reference checks

JazzCash, Easypaisa, SadaPay and Raast references are treated as account records. We use them to match payment activity, resolve disputes...

Cookie control alignment

Cookie choices are linked to the tools that place them, including analytics, session security and preference storage. We avoid vague...

Role-based staff access

Support and operations staff see account data according to their work role. A chat agent does not need the same...

Change record discipline

When we adjust privacy wording, we keep an internal change record showing what changed and why. That helps our team...

Local wording check

We write for Pakistan in clear English, using familiar wallet names and account terms. That keeps the policy readable when...

How privacy connects across policies

This Privacy Policy does not sit alone. It works with our cookie policy, account terms, support procedures and payment explanations so you do not get conflicting answers about...

Cookie policy link
The cookie policy gives more detail on browser storage, while this page explains why cookie data matters for account security, preferences and measurement. The two pages use the same cookie categories.
Account terms link
Account terms explain how your account may be used, while this page explains how related personal data is collected and protected. We keep rule wording separate from privacy purpose wording.
Payment page link
Payment pages name the available rails, while this policy explains how payment references become account records. We connect those references to security, reconciliation and support without repeating wallet instructions.
Support page link
Support pages show contact channels, while this policy explains what happens to the details you send through them. Chat logs, emails and attachments are handled as account support records.
Security page link
Security wording explains access protection, while this privacy page explains the related data signals. Login time, device changes and IP ranges help us spot account access that does not look normal.
Promo board link
Promo board pages may use account eligibility data, while this policy explains how those checks are made. We use account status and activity records without exposing private details to public areas.
Live casino link
Live casino pages display tables and sessions, while this policy explains what session records are kept. Game activity records help account history, dispute handling and operational checks.
LAYOUT MARKERS

Visible markers on this privacy page

We designed this privacy page so key data points are easy to find before you open an account or ask support for help. The layout separates account data...

Short privacy badges The opening badges summarise the data areas covered on this...
Plain section labels Each section label uses direct privacy wording rather than broad...
Context chips The chip row uses familiar Pakistan payment names only as...
Request-focused cards Support cards explain where privacy requests should go and what...
Connected policy blocks Comparison cards show how this privacy wording connects with related...
FAQ placement The privacy FAQ sits at the end so direct answers...

Privacy Policy questions answered

We collect account details you provide, such as contact data, login credentials and verification fields. We also record session activity, device signals, cookies, support messages and payment references needed to operate your account.

Payment references help us match JazzCash, Easypaisa, SadaPay and Raast activity to the correct account. They also support reconciliation, withdrawal checks, dispute handling and account security when a transaction needs to be traced.

We share limited data with service partners that support hosting, analytics, payment routing, security and support tools. Each partner receives only the fields needed for that service and must handle them under access controls.

Cookies help keep you signed in, remember preferences, protect sessions and measure page performance. Where choices are available, we show cookie controls so you can manage optional tracking without breaking core account access.

Yes. Contact support with the account email or phone linked to your profile and describe what needs correction. We verify ownership before changing personal data, payment references or contact details tied to the account.

We keep records for as long as needed for account operation, security, dispute handling and legal requirements in supported regions. Retention periods vary by record type, such as support chat, payment reference or login signal.

No. We do not sell your personal data. We use account and activity records to run pak365.com, protect access, process support requests, match payments and meet operational or legal requirements.