Terms connection
The Terms page explains account rules, while this Privacy Policy explains data use behind those rules. When an account check is mentioned there, this page clarifies what data may be processed.
LEGAL REFERENCE
Your privacy at 788 win
788 win keeps your account data, identity checks and contact choices under a clear Privacy Policy before you open the lobby. Read how we collect, use, store and...
Pakistan privacy scopeAccount data useSecurity checksContact choices
How this policy applies in Pakistan
This Privacy Policy explains the data we collect when you access 788win.mobi, create an account, verify your profile, use support, or request a payout check. We process details such as your name, mobile number, account login, device signals, transaction references and service messages so we can run your account, protect access, meet records duties and answer privacy requests. For Pakistan, payment references
may connect with JazzCash, Easypaisa, SadaPay, NayaPay or Raast, but we do not publish your private wallet details on public pages. Where local law permits, we may share limited data with security, payment and hosting partners that help us operate this site.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
CONTACT ROUTES
Reach us about privacy choices
Privacy questions should reach a team that can identify your account and answer without exposing extra details. We ask for the minimum proof needed before discussing profile data, login history or payment references, and we keep the conversation linked to your request.
Team online
Privacy email
Use the privacy email shown inside your account area for access, correction or deletion requests. Include your registered mobile number and a short request so we can match the account without asking for unrelated files.
Live chat handoff
Start with account support if you are already logged in and need privacy help. The chat team can move the case to our privacy queue after confirming the account session and request type.
Record request path
If you need a copy of account data, ask for a record request through support. We will confirm identity, gather the relevant data set and explain any legal reason certain records must remain stored.
POLICY CHECKS
How we check this policy
We keep the Privacy Policy tied to how 788 win actually works, not to empty legal wording. Product, support and security teams compare the wording with account screens, wallet references and device...
Account flow match
We check privacy wording against the account opening path, login prompts and profile fields. If a field asks for mobile, name or location signal, the policy must explain why that data is needed.
Security alignment
Our security checks use login time, device type, IP range and risk signals to spot account abuse. The policy states this clearly so you know why access may trigger extra verification.
Payment reference care
JazzCash, Easypaisa, SadaPay, NayaPay and Raast references are handled as account records. We use them for matching transactions, payout checks and dispute handling, not for public display or unrelated contact.
Support training
Support staff receive privacy scripts that limit what can be asked in chat. They should request only what helps confirm your account or solve your privacy request, then log the case outcome.
Change history
When we change the Privacy Policy, we keep internal records of what changed and why. Major updates are written in plain English so you can see how the policy affects your account.
Vendor checks
Hosting, analytics, security and payment partners are assessed for the data they receive from us. We share only the parts needed to run the service, detect abuse or complete requested account actions.
PAGE CONSISTENCY
Privacy across related policy pages
Our Privacy Policy sits beside other legal pages, but it has a separate job: explaining personal data. We keep cross-links consistent so you can move from terms, cookies or account rules back...
Cookie connection
The cookie page deals with browser storage, analytics tags and session signals. This Privacy Policy explains how those signals become part of account security, site performance and access records.
Payment record link
Wallet pages may show JazzCash, Easypaisa, SadaPay, NayaPay or Raast references for account activity. This policy explains how those references are stored, matched and restricted inside our systems.
Support wording match
Support pages ask you to share case details carefully. This Privacy Policy explains why support may need identity checks before changing profile details, sharing records or discussing transaction references.
Security page fit
Security wording focuses on safer access, while this policy covers the personal data used for that purpose. Login patterns, device signals and verification records are treated as privacy data.
Promo board limits
If we show account offers inside the site, privacy rules still apply. We explain how contact preferences and account activity may affect what you see without exposing private details publicly.
Regional access wording
Other pages may mention supported regions for Pakistan. This Privacy Policy explains how location signals, language settings and access checks may be processed where local law permits.
What you see on this page
This page is built so you can scan the Privacy Policy quickly while still finding the details that matter. We use short chips, direct headings and...
Plain headings
Each heading focuses on one privacy action, such as collection, storage, sharing or support. That structure helps you find the paragraph that applies to your account question without reading unrelated site copy.
Local context chips
Short chips name Pakistan data contexts such as JazzCash, Easypaisa, SadaPay, NayaPay and Raast. They remind you that wallet references are privacy records connected with account checks.
Request-ready wording
Privacy request sections tell you what to send and what not to send. We prefer registered mobile details and a short request, rather than extra documents that are not needed.
Security labels
Security labels explain why device, IP and login signals may be collected. We connect each label to account protection so the data purpose is clear before any extra verification appears.
Update cues
When wording changes, we present it as an update to privacy duties, account data or support contact paths. We avoid vague legal filler so changes are easier to understand.
Mobile reading
The page is arranged for small screens on 788win.mobi, with short cards and compact answers. You can check privacy wording while using mobile data without opening long nested documents.
Privacy Policy questions answered
We collect data needed to create and manage your account, including name, mobile number, login details, device signals, location indicators, support messages and transaction references connected with supported Pakistan payment rails.
Device type, session time, IP range and login patterns help us detect unusual account access. We use these signals for security checks, fraud control and account recovery, not for public display.
JazzCash and Easypaisa references are stored as account records so we can match transactions, check payout requests and answer disputes. We limit access to staff or partners who need the reference for that task.
Yes. Contact support from your registered account or the privacy email and explain what should be corrected. We may ask for proof before changing sensitive details such as mobile number or identity fields.
You can request deletion, and we will assess what can be removed. Some records may need to remain for security, dispute handling, payment matching or legal duties in supported regions.
We share limited data with hosting, security, analytics, support and payment partners when needed to operate 788win.mobi. Each sharing purpose must relate to account service, protection, records or your request.
Use account settings or contact support to adjust service messages where available. Some account and security messages may still be sent because they are needed for access, verification or privacy request handling.