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.
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...
This Privacy Policy applies when you access 889game.app, create an account, manage profile details, contact us, or use supported account services where local law permits. We collect details you provide, device signals that help protect access, transaction references linked to cash-in and cash-out requests, and messages you send to our team. We use that data to operate your account, confirm wallet activity,
prevent unauthorised access, respond to privacy requests, and meet record-keeping duties. We do not sell your personal data. When we use service partners, they receive only the data needed for that task, such as payment matching, security checks, hosting, analytics or customer care.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
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.
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.
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.
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.
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...
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.
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.
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.
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.
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.
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.
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...
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.
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.
Login alerts and password prompts refer to practical safeguards. This page explains the related data records, including session markers, device signals and access history.
Wallet screens show transaction references for JazzCash, Easypaisa, SadaPay and Raast. The policy states how those references support matching, support handling and audit records.
Support replies must match this policy when answering privacy questions. We train our team to avoid asking for unnecessary data during identity checks.
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.
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.
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...
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.
JazzCash, Easypaisa, SadaPay and Raast chips may show privacy context near transaction references. They remind you which records are used for matching and support.
When a new login or unusual session appears, we may display an account alert. This policy explains the data used to trigger that notice.
Where optional communications are offered, you can adjust choices inside your account. We record those choices so your preferences are applied across future messages.
Privacy links appear close to support forms, especially where identity checks are needed. That keeps the reason for verification visible before you send details.
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.