LEGAL REFERENCE

Privacy Policy for Your 789 com Account

789 com connects your account, slot rooms, live casino access and sportsbook records under one privacy policy, so you know what we collect before you open an account...

Pakistan account privacyJazzCash record careEasypaisa data handlingRaast flow checks
Explore the lobby Read FAQ
789 com Privacy Policy for Your 789 com Account

How Our Privacy Policy Applies

This Privacy Policy explains how 789 com collects, uses, stores and shares account data linked to your activity on 789com.life. It covers identity checks, login signals, lobby actions, wallet references, support chats and security records connected with your account. We use this data to run your account, protect access, process permitted transactions, handle support requests and meet legal duties in supported regions.

We do not sell your personal data. When you use JazzCash, Easypaisa, SadaPay, NayaPay or Raast, we store transaction references and status updates, not your full banking credentials. Access may depend on where local law permits, and this policy may change when our service or legal duties change.

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

PRIVACY HELP

Contact Paths for Privacy Requests

If you need help with privacy rights, start from the support channel inside your 789 com account so we can match the...

Live chat privacy queue Use live chat for quick privacy questions about...
Email privacy request Email us when you need a written privacy...
Account security route If you think your account access or personal...
DATA CARE

Privacy Checks Behind the Policy

Our privacy wording is shaped by how our product actually works: account creation, mobile login, live table access, slot sessions, sportsbook slips and Pakistan wallet confirmations. We keep the policy practical, so...

Operational source checks

We align the policy with real account flows, including registration fields, password resets, payment reference checks and support tickets. That keeps each privacy statement connected to data we actually process.

Limited payment storage

For JazzCash, Easypaisa, SadaPay, NayaPay and Raast, we store transaction identifiers, account status and timing records needed for reconciliation. Full banking credentials are not part of our stored account profile.

Session security records

We record login time, device signals, browser type and rough location markers to detect unusual access. These records help us protect your account and investigate support requests.

Support transcript controls

Support chats and emails may contain personal details you share with us. We keep those records for case handling, quality checks and legal needs, with access limited to trained team members.

Policy change checks

When account tools, wallet flows or security controls change, we check whether the privacy wording still matches the service. Material changes are reflected on this page with updated wording.

Access request handling

When you ask about your data, we verify your identity before replying. This protects you from another person trying to obtain account details through a privacy request.

Consistency Across Our Legal Pages

This Privacy Policy works alongside our terms, cookie wording and account rules, but it has a narrower job. It focuses on personal data: what we collect, why we...

Terms page link
Our terms explain account rules and service access, while this page explains personal data handling. If both pages mention verification, the privacy angle is about collected records and lawful use.
Cookie wording match
Cookie text covers browser storage and similar tools. This Privacy Policy connects those signals to wider account security, analytics, session management and fraud prevention records.
Wallet wording match
Payment help text may explain how a transfer moves. This policy explains the personal data around that transfer, including reference numbers, status updates and support history.
Account security match
Security pages describe how you protect access. This policy explains how we use login records, device signals and verification messages to identify and reduce account misuse.
Support wording match
Support pages tell you where to contact us. This policy explains how support chats, screenshots, emails and case outcomes are stored, shared internally and retained.
Regional access match
Other legal pages may mention supported regions. This page explains how location signals can be used to apply access rules and respond to legal obligations.
Retention wording match
Account pages may show recent activity. This policy explains retention periods in practical terms, including why some records remain after closure for accounting, security or legal needs.
PAGE MARKERS

Visible Privacy Layout Elements

We design this policy page so privacy details are easy to scan before you join or continue using your account. The layout separates collection, use, sharing, retention and...

Plain headings Each heading points to a specific privacy topic, such as...
Local context chips Short chips name Pakistan rails such as JazzCash, Easypaisa, SadaPay...
Account-first wording We describe privacy from your account journey rather than using...
Sharing boundaries The policy separates internal handling, payment processor references, security checks...
Retention cues We identify why records may be kept, including dispute handling...
Request prompts Contact prompts tell you what to include and what not...

Questions About Your Privacy

We collect details needed to run your account, such as registration fields, login records, device signals, contact history, wallet references and activity records. We use them for access, support, security and legal duties.

No. For JazzCash, Easypaisa, SadaPay, NayaPay and Raast, we store transaction references, status updates, timing and account matching details. Your full banking credentials are not stored in your 789 com profile.

Device and login data help us recognise normal access, detect unusual sessions and protect your account. These records may include browser type, device markers, login time and rough location signals.

Yes, you can contact support with a privacy access request. We verify your identity before responding, because releasing account records without checks could expose your data to another person.

We keep records only as long as needed for account operation, transaction reconciliation, support history, security checks and legal requirements. Some records may remain after closure where retention is required.

Support messages are available to trained staff who need them to handle your case, check quality or resolve account issues. We do not make your support history public.

Yes, we may update it when account tools, security controls, wallet flows or legal duties change. The current version on this page explains the privacy approach in effect.