Privacy Policy for Your 788win Account
Live Baccarat, Andar Bahar and Aviator sit behind one 788win account, and this Privacy Policy explains how we handle the data connected to that access. Open your account...
How We Handle Your Data in Pakistan
788win handles personal data for account access, security checks, support and transaction matching in supported regions of Pakistan. We collect details you give us, device and login signals, and records created when JazzCash, Easypaisa, SadaPay or Raast activity needs to be connected with your account. We use that data to confirm requests, protect access, process withdrawals, manage consent and answer privacy questions.
We do not sell your personal data. Sharing is limited to service partners that help run account security, customer care, analytics, payment record handling and legal duties. Access may vary where local law permits, and we may retain records when required for dispute handling, fraud prevention or accounting. You can contact us if you want a copy, correction or deletion request assessed
against those duties.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
How We Keep This Policy Current
We treat this Privacy Policy as an operating document, not a static page. When account flows, wallet checks or security tools change, we check whether the wording still matches how data moves...
Named policy owner
We assign policy ownership inside 788win so changes are not left to chance. Each edit is checked against account flows, security tools and Pakistan access wording before the page is refreshed.
Change records
Policy edits are logged with the reason for the change, the affected data category and the channel involved. That helps us explain what shifted when you ask about an older version.
Data minimisation
We ask only for data needed to run account access, fraud checks, support replies and payment record matching. If a field is not needed for those purposes, we avoid adding it.
Role access
Access to identity files, payment receipts and account history is restricted by role. Staff see the parts needed for their work, while sensitive actions create internal security events.
Local wording
Pakistan wording is checked for local payment names, region phrasing and plain English. We use JazzCash, Easypaisa, SadaPay and Raast examples only where they explain privacy handling.
Request verification
When you request a change or deletion, we check identity markers before acting. This protects your account from someone trying to alter privacy settings without your permission online.
How Our Policies Stay Aligned
Your privacy choices connect with other legal pages, but this page stays focused on data handling. We align wording across account terms, cookie use, payment records and support...
| Account terms | Terms describe account use; this page explains the data behind that use. We keep both pages aligned so consent, verification and account safety do not conflict during access. |
|---|---|
| Cookie page | Cookie wording matches this privacy page, but it focuses on browser storage, device IDs and session tools. Here we explain how those signals join your account record securely. |
| Account rules | Account rules cover conduct and access, while this page covers the data used to apply those rules. We avoid conflicting language around verification, contact details and retained records. |
| Support terms | Support terms explain how to contact us; this page explains how those messages are stored. We separate service handling from privacy rights so your request lands in the right queue. |
| Contact consent | Promotional contact rules are kept beside consent wording, not hidden in game copy. You can ask us to adjust messages without changing the core account record we need to keep. |
| Security wording | Security pages describe login protection; this policy names the data involved, such as IP signals, device fingerprints and failed access attempts, with reasons tied to account safety checks. |
| Transaction records | Payment terms describe transactions; this policy explains how receipts, payer names and status messages may be matched to your account where local law permits. That separation keeps money rules and privacy choices clear. |
Visible Policy Touchpoints Across the Page
The privacy page is built so you can locate the data point you care about without reading unrelated lobby copy. We use short headings, clear contact cards and...