Versus Terms
Terms set the account rules; this Privacy Policy explains the data behind those rules. For example, a security hold may need login records, identity files, and payment reference history.
LEGAL REFERENCE
How pk995 Handles Your Privacy
Before you open your pk995 account, this Privacy Policy shows what personal data we ask for, why we need it, and how you can question or correct it...
Account data explainedPakistan reference checksSupport privacy pathsSecurity log clarity
Policy Scope for Pakistan Accounts
Our Privacy Policy covers data gathered when you create an account, verify your profile, enter the lobby, contact support, or use JazzCash, Easypaisa, SadaPay or Raast references. We separate account identity, contact details, device signals, transaction references, chat records, and security logs so each data type has a clear reason. Access is provided only in supported regions and where local law permits,
so location checks may be used to confirm that the service can be shown to you. We do not sell your account data. Sharing is limited to partners that process verification, fraud screening, hosting, payments, analytics, or legal requests, and those partners receive only the data needed for that task. Updates appear here with the effective date.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
POLICY CHECKS
How We Keep Wording Accurate
Privacy wording should match what happens inside pk995, not sit apart from the account flow. Our checks compare policy text with login screens, verification prompts, support scripts, cookie tools, and Pakistan payment...
Named ownership
Policy ownership sits with the pk995 operations team, not an outside directory. That means account data, security logs, and support handling are described from the same workflows our staff use each day.
Change tracking
Each policy edit is logged with a date, reason, and owner. We check whether it affects account creation, verification, security alerts, cookies, or Pakistan payment references before publishing.
Partner limits
Service partners receive data only for assigned work, such as hosting, identity checks, fraud screening, message delivery, or payment reference matching. Contracts require restricted access and no unrelated reuse.
Local context
The policy names JazzCash, Easypaisa, SadaPay and Raast because those references appear in Pakistan account flows. That makes privacy wording more useful than generic banking language for you.
Security scope
We describe device, IP, session, and login records because they help protect your account against misuse. These records support investigation when a payment reference or profile change is disputed.
Plain language
We avoid legal fog where a direct sentence works. The policy explains what we collect, why we collect it, who may receive it, and how you can ask questions.
CONNECTED POLICIES
How This Policy Fits Others
Your privacy rights connect with other pk995 policy pages, but this page stays focused on personal data. The Terms explain account rules, the Cookie Policy covers browser storage, and the KYC wording...
Versus Cookie Policy
The Cookie Policy focuses on browser storage and preference tools. This Privacy Policy explains how cookie data connects with online account security, session history, analytics, and your choices.
Versus KYC Terms
KYC wording covers document checks and identity matching. This Privacy Policy explains why those files are collected, who checks them, how long they may be kept, and how corrections work.
Versus Support Rules
Support rules explain conduct in chat. This Privacy Policy explains how chat records, attachments, timestamps, and identity checks are stored when you ask us about your account privacy.
Versus Offer Terms
Offer terms describe reward conditions. This Privacy Policy explains the account data used to record eligibility, prevent duplicate claims, and answer your questions about any visible reward entry.
Versus Security Pages
Security pages explain protection steps. This Privacy Policy explains which device signals, IP records, password reset events, and session markers may be processed to keep access controlled.
Single account trail
Across policy pages, we use one account trail where possible. That helps us answer privacy requests without mixing your data with another person or creating duplicate records unnecessarily.
Policy Page Elements You Can Scan
The Privacy Policy page is built so you can scan the data points before opening an account. We place summary badges, contact paths, local context chips...
Summary badges
The hero badges call out account data, Pakistan references, and security logs before any long clause appears. They help you see the policy scope quickly without leaving the privacy page.
Data categories
Each clause separates identity, contact, device, payment reference, and support records. Clear categories make it easier for you to ask a specific question instead of sending a broad request.
Contact blocks
Privacy contact routes are displayed as cards, not buried at the end. You can pick email, chat, or account centre based on the type of data concern.
Local chips
JazzCash, Easypaisa, SadaPay and Raast chips appear where payment references are discussed. They show that the policy addresses Pakistan account flows rather than vague international wording.
Change marker
When we update the Privacy Policy, the effective date and amended clause area are shown near the relevant text. That helps you spot what changed before you continue.
FAQ anchors
FAQ answers are written around real privacy requests, such as correcting profile data or asking about retention. They are placed after the policy sections so you can act with context.
Privacy Questions Before You Join
We collect data needed to create and protect your account: contact details, login records, device signals, verification files, support chats, and payment references from JazzCash, Easypaisa, SadaPay or Raast where used.
Location checks help us show access only in supported regions and where local law permits. They also help detect account sharing, unusual logins, and payment references that do not match your normal pattern.
No. We do not sell your account data. Sharing is limited to partners that help with hosting, verification, fraud controls, support tools, analytics, payments, or lawful requests only.
Send a request from your registered email or use the account centre where available. We may ask for identity proof before changing phone numbers, payment references, or verification data.
Retention depends on the record type. Security logs may be shorter, while finance, verification, or dispute records may need to stay longer because of operational or legal duties in supported regions.
Yes, you can ask us to remove data linked to your account. Some records may remain where finance, security, dispute handling, or legal duties require limited retention.