LEGAL REFERENCE

Privacy Policy for your 889game account

889game keeps your privacy choices, account records and Pakistan wallet details under one clear policy, so you know what we collect before you open an account. Read this...

Account data explainedJazzCash contextEasypaisa contextRaast checks
889game Privacy Policy for your 889game account

How we handle your data

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

CONTACT ROUTES

Reach us about privacy

You can ask us about data access, correction, deletion, account closure records, consent choices or security concerns through the routes below. To protect your account, we may ask for matching details before acting on a request. We will not ask for your password, wallet PIN or full card-style credentials.

Team online

Privacy email

Use [email protected] for requests about access, correction, deletion or consent. Include your account email or phone, not passwords or wallet PINs, so we can match the request safely.

Account message

After logging in, you can send a privacy message from your account centre. This route helps us link your question with profile records without asking for extra personal detail.

Security concern

If you notice unknown access or an unexpected data change, contact us straight away. We can check session records, device markers and recent wallet references tied to your account.

POLICY CHECKS

How this policy stays accurate

Our privacy wording is maintained against the account flow you actually see on 889game.app. We compare the policy with registration fields, login protection, wallet reference screens and support forms before changes go...

Account-field mapping

We check policy wording against live collection points before updates. If a new field is added during account setup, we update the relevant section before rollout for you.

Wallet reference checks

JazzCash, Easypaisa, SadaPay and Raast references are treated as transaction records. We explain why they are held, who can see them and when retention applies.

Security logs

Login time, device type, IP range and session activity help us detect account misuse. The policy describes this collection because it directly affects account safety.

Partner limits

Service partners receive only task-specific data, such as hosting, payment matching or support tooling. Contracts restrict reuse, onward sharing and access outside the agreed purpose.

Change tracking

When we revise this page, we keep internal records of the reason, affected sections and live-date. That helps our team answer your privacy questions consistently.

Plain English

We write this policy in clear Pakistani English, avoiding legal clutter where possible. If a term affects your rights, we explain it close to the relevant action.

PAGE ALIGNMENT

Aligned privacy pages across 889game

Privacy promises must stay consistent wherever you read them on our site. We align this page with account terms, cookie wording, security messages and wallet disclosures, so one page does not say...

01

Account terms

Our account terms explain eligibility and account control, while this Privacy Policy explains the data behind those checks. We keep the two pages aligned during updates.

02

Cookie wording

Cookie wording covers browser storage and analytics tags. This Privacy Policy connects those tools to purposes such as security, preference saving and service performance checks.

03

Security messages

Login alerts and password prompts refer to practical safeguards. This page explains the related data records, including session markers, device signals and access history.

04

Wallet screens

Wallet screens show transaction references for JazzCash, Easypaisa, SadaPay and Raast. The policy states how those references support matching, support handling and audit records.

05

Support scripts

Support replies must match this policy when answering privacy questions. We train our team to avoid asking for unnecessary data during identity checks.

06

App prompts

If the app asks for device permissions, the prompt must reflect a real purpose. This policy explains the related data use before permissions affect your account.

07

Promo board

Where you check the promo board, we may use account status and region data. This page explains that use without turning privacy wording into promo copy.

Privacy cues across the page

We place privacy cues where data is collected, not hidden away at the end of the page. You will see short labels near account forms, wallet...

Form labels

Registration and profile fields use short labels that explain why details are needed. The full meaning stays here, where you can read the policy in context.

Wallet chips

JazzCash, Easypaisa, SadaPay and Raast chips may show privacy context near transaction references. They remind you which records are used for matching and support.

Session alerts

When a new login or unusual session appears, we may display an account alert. This policy explains the data used to trigger that notice.

Consent controls

Where optional communications are offered, you can adjust choices inside your account. We record those choices so your preferences are applied across future messages.

Help links

Privacy links appear close to support forms, especially where identity checks are needed. That keeps the reason for verification visible before you send details.

Policy date

A visible effective date helps you see when the policy last changed. Major updates are reflected in the page text before they affect your account.

Privacy questions before you join

We collect account details you provide, login and device records, support messages, preference choices and transaction references. Each category is linked to account operation, security, support or legal record-keeping.

Wallet references help us match account transactions, trace support questions and maintain audit records. We do not need your wallet PIN, and you should never send it to us.

We share limited data with service partners only when needed for hosting, security, payment matching, analytics or customer care. Partners are restricted from using it for unrelated purposes.

Yes. Send a request through privacy email or your account message area. We may verify your identity first, then respond with the data we can lawfully provide.

We use access controls, session monitoring and device checks to reduce unauthorised account use. Login records are visible only to teams that need them for security or support.

Retention depends on the record type and legal need. Account, transaction and security records may be kept longer than general support messages, especially where audit duties apply.