LEGAL REFERENCE

Privacy Policy for your 788 wine account

788 wine keeps your privacy choices, account records and Pakistan payment references in one clear policy, so you can open an account knowing what data we collect and...

Pakistan privacy scopeAccount data handlingJazzCash record careEasypaisa support context
788 wine Privacy Policy for your 788 wine account

How our Privacy Policy applies here

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

PRIVACY HELP

Contact paths for privacy requests

If you want to ask about privacy, correction, removal or a copy of your account data, contact us through the channel that matches the issue. We route privacy requests separately from general lobby help, so your message reaches the people who can check account records, payment references and login activity without exposing extra details. Keep your account name handy and avoid sending wallet secrets.

Team online

Privacy email

Send account-data questions to our privacy mailbox with your 788 wine account name and the detail you want checked. We may ask for identity proof before sharing or changing records.

Live chat ticket

Use live chat for urgent privacy access questions, such as suspicious login activity or an incorrect phone number. The agent can create a private ticket without asking for wallet PINs.

Account case

Open an account ticket when your request needs payment-reference checks for JazzCash, Easypaisa, SadaPay or Raast. We keep the thread tied to your profile for audit clarity.

POLICY CHECKS

How we keep wording accurate

We write this Privacy Policy from the way 788 wine actually handles account records. Each update is checked against support logs, payment reference flows, login security and Pakistan...

Plain language

We avoid legal fog where we can, so you can see what data is collected, why it is used and...

Process matching

Policy wording is matched to real account flows, including phone checks, password resets, payment reference matching and support contact handling...

Staff access

Only assigned staff can open sensitive account records, and access is tied to support duties, payment checks or privacy requests...

Change log

When privacy wording changes, we keep internal records showing the reason, the date and the account process affected, so updates...

Security checks

Login alerts, device patterns and payment-reference checks help us spot account access issues while limiting how much personal data staff...

Local context

Pakistan payment rails are named in this policy because they create reference records. We explain those records without asking you...

How this policy fits our legal pages

This Privacy Policy connects with our other legal pages so your account expectations stay consistent. The terms explain account use, the cookie page explains browser storage, and this...

Terms link
Our terms describe account rules; this Privacy Policy explains the data behind those rules, including login records, identity checks and contact history connected to your profile.
Cookie page
The cookie page deals with browser storage, while this policy covers personal data such as account details, support requests and security records tied to your access.
Security wording
Security language stays aligned with the Privacy Policy, so account protection, staff access and suspicious login checks are described with the same data scope.
Support terms
Support contact rules match this policy by explaining why we may ask for identity proof before discussing account records or payment-reference history.
Payment references
Where payment pages mention JazzCash, Easypaisa, SadaPay or Raast, this policy explains how related reference data may be stored and checked.
Account closure
If your account closes, this Privacy Policy explains which records may be retained for security, audit, dispute handling or legal reasons in supported regions.
Update timing
When another legal page changes a process involving personal data, we check this Privacy Policy so both pages describe the same account handling.

Visible privacy cues across the page

We design the Privacy Policy page so you can find the data point you care about without reading unrelated copy. Headings separate account data, payment references...

Clear section labels

Each heading names the privacy topic directly, so you can move from collection to storage, sharing, retention and contact rights without guessing what a section covers.

Short context chips

Chips near the policy highlight Pakistan payment references and account checks, helping you see where JazzCash, Easypaisa, SadaPay and Raast data may appear.

Request-ready cards

Contact cards explain which route to use for privacy questions, correction requests and account-data copies, so your message reaches the right team faster.

Retention cues

Retention wording explains why some records stay after a transaction or account change, especially when security, audit or dispute checks may still apply.

Access reminders

We remind you not to send wallet PINs, full card details or unrelated documents when asking about privacy, because less shared data means lower exposure.

Mobile reading

The policy is structured for quick phone reading, with compact paragraphs and clear cards that keep privacy choices visible on smaller screens.

Questions about your privacy rights

We collect account details, contact data, login records, device signals, support messages and payment references needed to run your account, protect access and answer privacy requests.

JazzCash and Easypaisa references help us match account funding or withdrawal checks to your profile. We store reference details, but we do not need your wallet PIN.

Yes. Contact us through the privacy channel with your account name and request type. We may verify identity before sharing records connected to your profile.

Retention depends on the record type. Some data is kept for account access, security checks, dispute handling, audit needs or legal duties in supported regions.

Access is limited to assigned staff who need the record for support, security, payment-reference matching or a privacy request. We track access for accountability.

Send a privacy request with the detail that needs correction. We may ask for proof before changing phone, name or payment-reference data on your account.