Account terms
Account terms explain how you use pkr116, while this policy explains the personal data behind that use, including identity details, contact records, login activity, and verification files.
pkr116 keeps your privacy terms in one clear policy for account checks, lobby access, device sessions, and Pakistani transaction records. Read this page before you open your account...
Our Privacy Policy explains the personal data we process when you create an account, verify access, use the lobby, or make transactions through supported regions where local law permits. We may keep your name, contact details, device signals, login history, wallet references, and support messages so we can secure your account, confirm requests, and meet record duties that apply to our service.
We do not sell your personal data. Access to privacy records is limited to staff who need them for account safety, transaction checks, support replies, or legal handling. When a payment rail sends a receipt or reference, we store only what is needed to match it to your pkr116 account and resolve later questions.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
You can ask us about the personal data connected to your pkr116 account through the help area after login or by using the contact route shown on the site. We may ask you to confirm account ownership before we discuss private records. That step protects your identity, wallet history, and support messages from being shared with the wrong person.
Use the privacy request option inside your account to ask what personal data we hold and which records connect with your identity checks, sessions, and Pakistani transaction receipts.
If your phone number, spelling, or wallet reference is wrong, tell us through support so we can check the account trail and correct records where allowed.
Before we share account data, we confirm that the request comes from you. This may include matching contact details, login signals, or recent transaction references.
We keep this Privacy Policy tied to the way pkr116 actually runs accounts, sessions, and local transaction records. When we change a verification step, add a data field, or adjust a support...
Privacy wording is matched against real account steps, including signup data, session logs, verification checks, support tickets, and transaction references linked to JazzCash, Easypaisa, SadaPay, or Raast.
Staff access to personal data is separated by role. Support can handle account questions, while deeper wallet or security checks require tighter access and logged handling.
We record device and browser signals to protect account access, spot unusual logins, and help you recover control if your account is used without permission.
Local rail references are stored to connect a transaction with your account. We use those records for matching, dispute checks, withdrawal verification, and support replies.
Some records must be kept for security, transaction tracing, or legal reasons. When there is no valid need, we aim to remove or anonymise them.
We write this policy in clear Pakistani English so you can see what happens to your data without reading technical wording or unclear legal phrases.
The Privacy Policy works beside our account terms, cookie wording, and support replies. Each page has a separate role, but the privacy message stays consistent: we explain what data is collected, how...
Account terms explain how you use pkr116, while this policy explains the personal data behind that use, including identity details, contact records, login activity, and verification files.
Cookie wording covers small browser files and session tools. This policy connects those tools to wider privacy handling, including device recognition, security checks, and account continuity.
Support messages may include private account details. Our policy explains why we keep those exchanges, how they help resolve requests, and when identity checks are needed.
Transaction screens show wallet activity. This policy explains how related references, receipts, timestamps, and checks are stored for account matching and later query handling.
Security prompts protect account access. The policy explains how login signals, device patterns, and verification attempts may be processed to reduce account misuse.
If you check the promo board, account eligibility may rely on limited profile and activity data. This policy explains that processing without turning it into sales wording.
Access may depend on supported regions where local law permits. Privacy handling still follows this page, including data checks used to confirm eligibility and account status.
This page is arranged so you can scan the privacy terms quickly before you create or continue using your account. The sections move from data collection to support...