Terms link
Our terms explain account rules, while this policy explains data use behind those rules. We keep the two pages aligned so privacy wording is not repeated loosely.
LEGAL REFERENCE
Privacy Policy for your bd188 account
bd188 keeps your privacy terms for account access, lobby activity and Pakistan payout checks in one place, so you know what data we collect before you open your...
Account dataCookie choicesPakistan supportSecurity checks
How we handle your data
We collect only the data needed to create your bd188 account, keep access secure, run account checks, answer support questions and process requests linked with supported regions. That may include your name, contact details, device signals, login records, cookie choices, transaction references and messages you send us. When you use JazzCash, Easypaisa, SadaPay or Raast, we may receive reference codes and status
updates, not your full wallet secret details. We use this data to confirm account ownership, detect unusual access, respond to privacy requests and keep records required for local compliance where local law permits.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
SUPPORT PATHS
How to ask about privacy
Privacy questions should reach the team that can check account ownership without exposing extra data. We keep support paths clear so your request goes to the right queue, whether you need a copy of account data, a correction, a cookie change or a query about wallet references.
Team online
Account email
Email us from the address on your account and include the account ID only. We may ask for a light identity check before sharing data or changing privacy choices.
Live chat
Use chat for quick privacy routing, such as cookie questions or data correction steps. Our team will not ask for wallet PINs, passwords or private app codes.
Request log
When you send a privacy request, we record the date, channel and outcome. That log helps us track open cases without repeating sensitive details in each reply.
POLICY CHECKS
How we keep this policy accurate
We write this Privacy Policy from how bd188 actually handles account data, not from generic wording. Each update is checked against support flows, payment reference handling, cookie behaviour and account-security practice, so...
Operator wording
We describe our own account and privacy process in plain English. If a support step changes, we adjust this page so your data rights remain clear.
Local rails
JazzCash, Easypaisa, SadaPay and Raast references are handled as transaction markers. We do not publish or store wallet secrets in the public policy text.
Security checks
Login records, device signals and session data help us spot account access that looks unusual. These checks support privacy because they protect account control.
Cookie records
We separate cookies used for sign-in, security and preference storage. Where choices are offered, your selection is tied to your browser or account session.
Access requests
When you ask for account data, we confirm the request belongs to you before sending anything. That step protects your privacy and reduces mistaken disclosure.
Policy updates
If our data handling changes, we refresh this page and keep the wording practical. The date and content should match the current account flow.
PAGE MATCHING
How this policy stays consistent
This Privacy Policy sits beside our other legal pages, but it has one job: explaining personal data handling. We align wording across pages so account creation, cookie use, transaction references and support...
Cookie wording
Cookie text connects with this policy because browser storage can identify a session. We keep cookie categories clear and avoid mixing them with account permissions.
Security wording
Security language is matched across the site so you see the same approach to login records, password resets, device checks and account access alerts.
Wallet references
Where payment rails appear, this policy focuses on transaction references and verification status. It does not turn wallet details into public account content.
Support records
Support pages may explain response paths, but this policy explains what data is logged when you contact us and why that record may be retained.
Region wording
Access wording uses supported regions and where local law permits. That keeps privacy statements tied to practical availability rather than broad promises.
Update style
When legal text changes, we keep section labels, request paths and definitions consistent. That makes it easier for you to compare current wording with earlier copies.
What you can see on this page
The Privacy Policy layout is built for quick reading without hiding key clauses. We separate account data, cookies, security, support requests and local transaction references so...
Short badges
The hero badges show the main privacy areas at a glance: account data, cookie choices, Pakistan support and security checks. They help you scan before reading deeper.
Clear sections
Each section has a narrow privacy purpose, so data collection, support routing and policy updates do not blur together. That structure keeps the wording easier to act on.
Request prompts
Support cards explain how to contact us without sending extra sensitive details. We point you toward account email or chat depending on the privacy request.
Security cues
Lock, shield and session references show where security activity touches personal data. These cues explain why some records are needed for account protection.
Local context
Pakistan rails are named only where they affect privacy, such as reference codes and verification status. We avoid asking for wallet secrets through policy channels.
Question block
The FAQ answers common privacy concerns in short form. If your issue needs account checks, the answer points back to support paths rather than exposing details.
Privacy Policy questions before you join
We may collect your name, contact details, login records, device signals, cookie choices, support messages and transaction references. Each item is linked to account access, security, support or required record keeping.
Identity checks help us confirm that privacy requests come from the account owner. We use limited checks before sharing data, correcting records or changing account privacy settings.
No. For JazzCash, Easypaisa, SadaPay and Raast activity, we may receive reference codes or status markers. We do not ask for private wallet PINs or app secrets.
Cookies may keep your session active, remember preferences, support security checks and measure site performance. Where choices are available, your setting is stored against your browser or account session.
Yes, you can contact support from your account email. We will confirm ownership first, then explain what data can be shared and any limits that apply locally.
We may share data with service providers, payment processors or advisers when needed for account operation, security, support or legal duties. We do not sell your account data.