Terms page
Our Terms describe account rules, while this policy explains the personal data used to run those rules. If a term needs identity, payment or security data, this page explains why.
LEGAL REFERENCE
Privacy Policy for your j95s account
j95s puts your account, game, device and Pakistan payment privacy terms in one clear policy, so you know what we collect before you open an account. Read how...
Pakistan account dataCookie choicesPayment record handlingSupport privacy
How we handle Pakistan account data
This Privacy Policy explains how j95s collects, uses, stores and shares data linked to your account in supported regions of Pakistan. We use your data to create your account, protect access, process identity checks, settle game records, answer support requests and maintain records required by local law where local law permits. Payment references from JazzCash, Easypaisa, SadaPay, NayaPay and Raast may be
matched with your account so withdrawals, refunds and account checks can be handled accurately. We do not sell your personal data. We may share limited data with payment processors, identity checks, security tools, game providers and support systems when they need it to deliver the account service you ask us to provide.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
PRIVACY HELP
Privacy contact routes at j95s
You can contact us about this Privacy Policy from inside your account or before you join. Tell us what you need changed, checked or explained, and include the account email or mobile number you used with j95s. We will verify you before sharing account data, because privacy requests must reach the right person.
Team online
Privacy email
Send privacy requests to [email protected] with your account email, mobile number and a clear request. We use this route for access, correction, deletion and data-use questions tied to this Privacy Policy.
Live chat handoff
Start in live chat when you need quick routing. Our chat team can confirm your account details, create a privacy ticket and pass it to the team that handles policy requests.
Account centre
Inside your account, the privacy area lets you update contact details, check consent choices and request help. We ask for verification before any sensitive account data is shown or changed.
POLICY CHECKS
How we keep this policy accurate
Our Privacy Policy is maintained by the j95s team that works with account security, support, product and local payment operations. When a data flow changes, we update the policy text rather than...
Version dates
We place an update date on the policy so you can see when the wording changed. Material changes are highlighted through account messages or page banners when they affect your choices.
Data mapping
Before policy text is changed, we map the account data involved, why it is needed and which teams or processors touch it. That keeps the wording tied to real account flows.
Security input
Our security team checks privacy wording against account login controls, device checks and session monitoring. This helps the policy explain protection steps without exposing sensitive system details.
Payment alignment
When JazzCash, Easypaisa, SadaPay, NayaPay or Raast handling changes, the policy is checked for matching privacy wording. We separate payment records from marketing choices and support history.
Support feedback
Questions sent to support help us spot unclear privacy wording. We rewrite sections when you ask the same thing often, especially around deletion, verification and account record retention.
Plain English
We avoid legal clutter where a clear sentence works. The policy names the data, the purpose and the contact route so you can act without reading dense contract language.
PAGE CONSISTENCY
How this policy stays consistent
The j95s Privacy Policy sits beside other account pages, but it has a separate job. Terms explain account use, cookie text explains browser storage, and this page explains personal data. We cross-check...
Cookie page
Cookie text covers browser storage and tracking choices. This Privacy Policy connects those cookies to wider account data, including device signals, consent choices and session security checks.
KYC wording
Identity checks have their own short wording, but the privacy basis remains here. We explain why documents may be requested, how they are checked and how access is controlled.
Security page
Security content describes login protection and account safeguards. This policy explains the related data use, such as device checks, IP records, session logs and suspicious-access alerts.
Payment terms
Payment terms explain transaction rules. This Privacy Policy explains how payment references, wallet names, bank rails and withdrawal checks are linked to your j95s account records.
Promo terms
Promo terms may mention eligibility, but this policy explains the data used for that check. We keep promotional messaging separate from privacy consent and account-contact choices.
Account closure
Closure wording explains how to end account access. This policy explains what data may still be retained afterward for disputes, payment records, security and local legal needs.
Policy layout you can scan quickly
We designed this Privacy Policy page so you can find the data point you care about without hunting through unrelated copy. The page separates collection, use...
Short summary blocks
Each major privacy area starts with a short summary before the detailed wording. That helps you understand the purpose first, then read the exact account data involved.
Purpose labels
We label privacy purposes such as account setup, security, support and payments. Clear labels make it easier to see why j95s asks for a detail at a specific moment.
Retention timeline
The page explains that some records are kept only while your account is active, while others stay longer for payment checks, disputes, security logs or legal record needs.
Consent controls
Where we rely on your choice, we show how to adjust it. Account messages, cookie settings and contact preferences are explained without mixing them with core service data.
Contact strip
Privacy contact routes stay visible near the policy sections that need action. You can ask for access, correction or deletion help without leaving the page confused.
Change markers
When we update policy wording, we mark the date and keep language direct. Larger changes may appear in your account area so you can read them before continuing.
Privacy questions before you join
We collect details needed to create and protect your account, such as name, mobile number, email, login data, device signals and verification records. We also keep game and transaction records linked to your account activity.
We use wallet or rail references to match payments with your account, check withdrawals and resolve support queries. The Privacy Policy treats those records as account data and limits access to teams that need them.
We share limited data with service providers that help run accounts, payments, identity checks, security tools, games and support. They receive only what they need for that task and must handle it under agreed controls.
Yes. Contact us through the account centre, live chat route or privacy email and tell us what needs correction. We verify you first, then update eligible account details or explain why a record must remain.
Retention depends on the data type and the reason it was collected. Some records end with account use, while payment, dispute, security and legal records may be kept for longer where local law permits.
Cookies help us keep sessions active, remember choices and protect account access. Where cookies are optional, we explain your choices and link them to the wider privacy wording for device and session data.