LEGAL REFERENCE

Privacy Policy for your 988 wan account

988 wan keeps account data, lobby activity, security checks and payout verification covered in one Privacy Policy, so you know what we collect before you open your account...

Account dataSecurity checksPakistan payment contextSupport contact paths
988 wan Privacy Policy for your 988 wan account

How our Privacy Policy applies

Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.

CONTACT ROUTES

Ask us about your privacy rights

If you want to ask what data we hold, request a correction, question a payment reference or raise a privacy concern, contact...

Account message centre Send privacy requests from inside your account area...
Email privacy request If you cannot access your account, email our...
Payment reference query For JazzCash, Easypaisa, SadaPay or Raast privacy questions...
POLICY CHECKS

How we keep policy wording current

We write this Privacy Policy from the work we do on 988 wan each day: account access, payment verification, support handling and lobby security. Our internal checks focus...

Account flow matching

We compare policy wording with the actual account fields you see, including contact detail, password reset paths and verification prompts...

Payment data mapping

We map how Pakistan wallet references enter our systems, who can view them and why they are kept. That includes...

Live session privacy

Live table streams are delivered through provider systems, while your account record keeps session references needed for security and settlement...

Support script checks

Our support responses are checked so staff ask only for details needed to verify your request. Full identity documents or...

Retention controls

We keep account and transaction records only for operational, security and legal reasons that apply to the service. When data...

Plain English pass

We avoid dense wording where a direct explanation works better. The aim is that you can read the policy, understand...

PAGE ALIGNMENT

Privacy wording across related pages

Our Privacy Policy connects with other legal pages on 988 wan, but it has a separate job. Terms explain account rules, cookie wording explains browser storage, and support pages explain contact handling...

01

Terms page link

Where our Terms describe account duties, this Privacy Policy explains the data used to support those duties. The two pages should read together without repeating the same wording.

02

Cookie wording split

Cookie wording covers browser storage, session IDs and preference tools. This Privacy Policy covers personal details tied to your account, including login records and security signals.

03

Support page match

Support pages tell you how to reach us; this page explains how messages, attachments and account checks may be handled after you contact the 988 wan team.

04

Payment page boundary

Payment pages describe available rails and account wallet steps. This policy explains the privacy side, including transaction references, verification access and limited sharing with payment service partners.

05

Security page boundary

Security wording explains login protection and account safety tools. This policy explains the related data, such as device signals, login records and suspicious access checks.

06

Promo page boundary

If promotional messages are offered, the promo page explains the offer terms. This policy explains how contact preferences and related account data may be handled.

07

Language consistency

We use clear Pakistani English across legal pages so your rights, account duties and privacy choices do not depend on complicated wording or unfamiliar legal phrasing.

Privacy layout you can scan

This page is arranged so you can move from broad policy purpose to specific account situations without searching through unrelated copy. Each block explains a visible...

Clear opening summary

The opening section states the policy purpose before legal detail begins. You can quickly see that the page covers account data, security checks, payment references and support contact records.

Local context chips

Short chips name Pakistan payment rails only where they matter to privacy. They remind you that wallet references are handled as account records, not as public lobby data.

Contact card block

The support cards separate account messages, email requests and payment reference queries. That layout helps you choose the lowest-data route for the privacy question you want answered.

Data purpose cards

The trust section uses small cards to connect each data category with a purpose. This avoids burying security, support and live-session details in one long legal paragraph.

Related page comparison

The comparison block shows where this policy ends and other legal pages begin. That keeps cookie, account rule and support wording from being mixed into privacy explanations.

Question block

The FAQ focuses on practical privacy concerns, including access, correction, verification and retention. Each answer gives a direct action without adding unrelated lobby promotion.

Common Privacy Policy questions

We collect the details needed to create and protect your account, including contact fields, login records, device signals, support messages, transaction references and limited gameplay records used for settlement and security checks.

JazzCash and Easypaisa references are treated as account transaction data. We use them to verify wallet activity, resolve payment queries and keep records required for operational or legal reasons in supported regions.

Yes. The policy covers account data linked to live casino sessions, such as session references and security checks. It does not mean we control every provider video stream or studio system.

Yes. Contact us from your account area and explain what needs correction. We may ask for limited verification before changing details that affect access, payments or account recovery.

Withdrawal records help us confirm where funds were sent, resolve disputes, check account safety and meet legal duties where local law permits. Access is limited to staff or partners who need it.

Use the account message centre when possible, or email support if you cannot log in. Keep the request specific, include your registered contact detail and avoid sending extra documents unless requested.