How jeopk protects your privacy
jeopk puts this Privacy Policy in plain en-PK English so you can see what account data we collect, why we need it, and how privacy choices work before...
How our Privacy Policy applies
This Privacy Policy explains how jeopk handles personal data when you use our site in supported regions of Pakistan where local law permits access. We collect only the details needed to create and protect your account, run identity checks, process support requests, maintain payment records, and keep the lobby secure. Payment references may include wallet names, transaction codes, timestamps, and status updates,
but we do not ask you to share wallet PINs or banking passwords. We also use cookies, device signals, and session records to keep your account flow stable and to detect unusual access. If the policy changes, we update the page date and keep the wording clear enough for you to compare what changed.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Checks behind this Privacy Policy
We treat the Privacy Policy as an operating document, not a loose statement. The wording is checked against account creation, security monitoring, support handling, cookie use, and Pakistan...
Plain Language
We write privacy wording for quick reading on mobile screens. Legal terms are kept short, and each section explains the...
Pakistan Context
The policy reflects local account flows, including JazzCash, Easypaisa, SadaPay, and Raast references. We name these only to explain privacy...
Access Controls
Account data is limited to staff roles that need it for checks, support, and security. Internal access is logged, and...
Change Record
When privacy wording changes, we keep the page date visible and adjust related policy pages where needed. That helps you...
Cookie Checks
Cookies are checked against actual site behaviour, including login sessions, fraud signals, and preference storage. We avoid vague cookie wording...
Retention Windows
We keep account records only for business, security, legal, or dispute needs. When a record no longer has a valid...
Aligned wording across policy pages
Your privacy rights sit beside other jeopk policy pages, so we keep definitions and contact paths aligned. That consistency matters when one page explains account conduct, another explains...
Visible markers inside this policy
This page is designed so privacy details are easy to scan before you join or update your account. The layout highlights what data is collected, why...
Scope Badges
The hero badges show the main privacy areas first: account data, cookies, Pakistan payment context, and security checks. They help you decide which policy section to read next.
Purpose Blocks
Each policy block links a data type with a clear purpose, such as account access, identity checks, fraud detection, support handling, or record keeping for disputes.
Contact Strip
The contact strip separates privacy requests from general support. It tells you where to send access, correction, deletion assessment, and cookie questions without exposing private wallet details.
Local Examples
Pakistan examples are included only where they clarify privacy handling. Wallet names, transaction references, and session timing help explain records without turning the policy into a sales page.
Change Cues
Date cues and aligned wording across policy pages help you notice when privacy language has changed. We aim to make updates visible instead of hiding them in long paragraphs.
Choice Signals
Where choices exist, the policy points to the correct place to act, such as account settings, cookie settings, or privacy email, after any required identity check.