Privacy Policy for Your Account
188pkr puts account data, payment traces and device signals into one clear Privacy Policy, so you know what we collect before you open your account. We explain the...
How We Handle Privacy Data
This Privacy Policy explains how 188pkr handles the data linked to your account, access sessions, payment records and service messages where local law permits. We collect only what is needed to create and protect your account, process requests, confirm identity, keep transaction logs, respond to privacy messages and maintain site security. Pakistani payment names may appear in records when you use JazzCash,
Easypaisa, SadaPay or Raast. We keep records only for business, security, legal and dispute-handling needs, then reduce or remove them when retention is no longer required.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
How Our Policy Stays Clear
We write this Privacy Policy from our own operating flow, not as a generic legal page. The wording reflects account creation, login security, Pakistani payment receipts, withdrawal verification, service messages and support...
Account flow mapping
We connect each policy statement to a real account step, such as registration fields, login checks, password recovery or profile edits. That keeps the policy tied to actions you can recognise.
Payment record clarity
When JazzCash, Easypaisa, SadaPay or Raast appears in a transaction record, we explain why the reference exists. The policy separates payment proof from gameplay history and general account data.
Security signal limits
Device, browser and session signals help us protect your account from unusual access. We describe these signals as security data, not as hidden profiling for unrelated messages.
Support access rules
Our help team can see only the account details needed to answer your request. Privacy questions that need deeper checks move through controlled paths rather than casual chat replies.
Retention checks
Records are kept for account, security, legal and dispute needs, then reduced when they no longer serve those purposes. We describe the retention reason instead of giving vague storage claims.
Local wording
We use clear Pakistani English and name local rails directly, so you can connect the policy to payment records you know. The policy avoids legal fog where plain wording works.
Consistent Privacy Across Our Pages
Our Privacy Policy sits beside related account pages, so the same data handling meaning follows you across 188pkr. Cookie wording, account terms, verification messages and support replies should...
| Account terms | Account terms explain what you agree to when using 188pkr, while this Privacy Policy explains how related data is handled. The two pages should use the same account and identity wording. |
|---|---|
| Cookie page | Cookie wording covers browser storage and session tags, while this policy explains the wider data purpose. Together, they show how access signals help keep your account functioning securely. |
| Verification prompts | When we ask for identity or payment proof, the prompt should match this policy’s data purpose. We avoid asking for extra material unless security, account matching or dispute handling requires it. |
| Support scripts | Support replies should mirror this policy when explaining privacy steps. If you ask why a record is needed, our answer should align with account safety, request handling or legal retention. |
| Promo messages | If you receive service or promotional messages, the privacy basis should be clear. This policy explains message data, preference handling and how account contact details are used by 188pkr. |
| Payment receipts | Receipts from JazzCash, Easypaisa, SadaPay or Raast may create transaction references. This policy explains how those references help match payments, settle queries and protect account records. |
| Access logs | Login and device logs appear across security pages and account tools. This policy explains why those logs exist, how they support protection, and when they may be checked. |
Privacy Layout You Can Scan
We organise the Privacy Policy so you can find the part that matters without reading unrelated material. The page separates collection, use, sharing, storage, access requests...
Collection summary
The collection section lists the main data groups we handle, such as account fields, device signals, session logs and transaction references. Each group is tied to a reason you can understand.
Use explanation
The use section tells you why data is needed, from account access to security checks and support replies. We avoid mixing privacy reasons with broad product wording that does not help you.
Sharing boundary
The sharing section explains when service partners may process data for hosting, payments, support or security. It also makes clear that partner access should stay within the service purpose.
Storage section
Storage wording covers why certain account and transaction records remain after a session ends. We connect retention to security, legal, operational and dispute needs rather than leaving it vague.
Access request route
The request route explains how you can contact us about account data. We may verify your identity first, because privacy access must protect your account from the wrong requester.
Security wording
Security language explains how access logs, device checks and account safeguards support privacy protection. These controls help us detect unusual activity while keeping the policy focused on data handling.