LEGAL REFERENCE

How 788w Handles Your Privacy

788w keeps privacy choices, account checks and Pakistan wallet records in one plain policy so you know what we collect before you open your account. Read how we...

Pakistan privacy scopeAccount data controlsWallet record useCookie choices
Explore Lobby Read FAQ
788w How 788w Handles Your Privacy

Our Privacy Position For Pakistan

Our Privacy Policy explains how 788w collects, stores and uses account data when you create access, verify your profile, contact us or use wallet rails available in supported regions. We ask for details that help us keep your account reachable, match transaction records, answer service requests and protect access from unauthorised use. We do not sell your personal details. We may share

limited records with service partners such as payment processors, verification tools, hosting providers and support systems when that sharing is needed for the account service. Where local law permits, we also keep records that help us answer lawful requests, resolve disputes and maintain security logs. You can contact us about access, correction or deletion requests, and we will respond through the channels

listed on this page.

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

HELP ROUTES

Privacy Contact Paths At 788w

Privacy requests should reach the right team without making you repeat your details. We use separate contact paths for account access queries, wallet record questions and data rights requests. When you write to us, include your account identifier, registered mobile number and the request type, but never send passwords or one-time codes.

Team online

Live chat privacy request

Use chat when you need quick help finding privacy settings or checking which account details are visible to our support desk. We may ask security questions before discussing account-specific data.

Email data request

Send email for access, correction or deletion requests that need a written trail. Our privacy team checks the account match first, then replies with the next step and expected handling window.

Wallet record query

Choose this path when your question involves JazzCash, Easypaisa, SadaPay or Raast records connected to your account. We compare transaction references without exposing unnecessary wallet details.

CHECKED WORDING

How We Keep The Policy Current

We write this policy from the way our service actually handles accounts, support requests and wallet records. Each update is checked against the forms you complete, the security...

Operational source

The policy is based on account screens, verification steps, wallet record flows and support tools we operate. That keeps the...

Change checks

When we adjust forms, security prompts or support workflows, we check whether the Privacy Policy needs revised wording. Material changes...

Local wallet context

The policy names Pakistan payment rails where records may be matched to your account. We explain the purpose of that...

Security logging

We keep access logs, device signals and account action records to detect unauthorised activity. Those logs are limited to security...

Support training

Our support team is trained to discuss privacy requests without exposing passwords, one-time codes or full wallet details. Identity checks...

Data rights handling

Requests for access, correction or deletion are routed to a privacy queue. We verify the account match, assess any retention...

Consistency Across Our Policy Pages

This Privacy Policy connects with other legal pages on 788w, but it keeps a separate purpose. Terms pages explain account rules, while this page explains personal data handling...

Terms page link
Our Terms page explains account conduct and service rules. This Privacy Policy only explains what personal data we collect, why we use it and how requests are handled.
Cookie wording
Cookie text deals with browser storage, session tools and preference signals. The Privacy Policy connects that storage to wider account data handling and consent choices.
Security page match
Security wording explains protections such as login checks and monitoring. This page explains the personal records behind those protections, including access logs and device signals.
Support page fit
Support pages tell you how to reach us. This policy explains what data we may use during a support conversation and how we confirm account ownership.
Wallet record wording
Wallet content names supported Pakistan rails for account transactions. The privacy page explains how related references are stored, matched and used for dispute handling.
Update consistency
When one legal page changes, we check linked wording across the policy set. This reduces conflicting language around data use, retention and contact routes.
Plain language aim
We avoid dense legal phrasing where a direct sentence works. You should be able to see what data is involved and why it is needed.
CLEAR MARKERS

Privacy Page Layout Cues

We design this privacy page so you can scan it before sharing account details. The layout separates what we collect, why we use it, who may process it...

Plain headings Each section uses short headings that tell you what privacy...
Local context chips Chips for JazzCash, Easypaisa, SadaPay and Raast show where wallet...
Request-first layout Contact routes sit near the policy details so you can...
Data purpose blocks Policy blocks are organised around purpose: account access, security, support...
Retention signals Where records must be kept for disputes, security or lawful...
Rights prompts The page highlights how to ask for access, correction or...

Privacy Questions Before You Join

We collect details needed to create and protect your account, such as contact data, login records, device signals, support messages and wallet references linked to JazzCash, Easypaisa, SadaPay or Raast.

Wallet references help us match account activity with Pakistan payment rails, resolve disputes and confirm that records belong to the right account. We do not ask for wallet passwords or one-time codes.

Yes. You can ask for access to personal data connected with your account. We first confirm identity, then share the record we can provide under applicable retention and security requirements.

You can request correction when account details are inaccurate or out of date. We may ask for supporting proof before changing fields that affect identity, wallet matching or account security.

Cookies help keep sessions active, remember preferences and understand basic site performance. Some cookies are needed for account access, while optional analytics choices can be managed where controls are available.

Support messages are available to trained staff who need them to answer your request, verify account ownership or resolve a dispute. We limit access and do not require secret login codes.

Send a deletion request through email or the privacy contact path. We verify the account, remove data that no longer needs retention and explain any records we must keep.