LEGAL REFERENCE

Privacy Policy for your account

we9999 game keeps one privacy policy for account data, device checks, live casino session logs and Pakistan wallet records, so you can see how your details are handled...

Account dataDevice checksSession recordsPakistan wallet context
we9999 game Privacy Policy for your account

How our privacy policy works

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

CONTACT ROUTES

Reach us about privacy requests

Privacy questions deserve a route that is easy to follow. Use the contact path connected to your account whenever possible, because it...

Account inbox Send privacy requests from the inbox inside your...
Email support If you cannot access the account area, email...
Live chat handoff Our live chat team can receive privacy questions...
POLICY CHECKS

How we keep this policy current

Our privacy wording is checked against how the service actually runs. When our account flow, wallet reconciliation, device checks or support routing changes, we update the policy language so it reflects the...

Account flow mapping

We map each account step to the data it creates, from mobile number entry to session records. This helps us keep the policy tied to real screens you see while using we9999 game.

Wallet record checks

JazzCash, Easypaisa, SadaPay and Raast references are treated as transaction records, not marketing lists. We keep them linked to account safety, reconciliation and support enquiries only.

Security access logs

Login time, device type, IP region and failed access attempts may be stored to protect your account. These records help us investigate unusual activity and confirm that privacy requests are genuine.

Support case handling

Support messages may contain personal details, so we limit who can open privacy cases. Team access is based on work need, and case history is kept for dispute handling.

Partner boundaries

Some technical partners help with hosting, analytics or verification. We share only the data needed for assigned work, and we expect those partners to keep it separate from their own purposes.

Plain language checks

We write privacy terms in direct Pakistani English so you can understand what is collected, why it is used and how to reach us if a record looks wrong.

PAGE CONSISTENCY

Where this policy sits

The privacy policy works alongside our other legal pages, but it has its own job. It explains personal data handling, not game rules, promotions or account conduct. If another page mentions verification...

01

Terms page

Our terms set account conduct rules, while this privacy policy explains the data attached to those rules. If conduct checks create records, this page explains how those records may be used.

02

Cookie page

Cookie wording deals with browser storage and similar tools. This privacy policy connects those signals with wider account data, including device checks, session records and support case references.

03

Promo page

Promotional pages may show account rewards or campaign entries. This privacy policy explains how related eligibility records are handled, corrected and retained when they connect back to your account.

04

Security page

Security content explains account protection steps. This privacy policy covers the personal data behind those steps, such as access logs, verification responses and suspicious activity checks.

05

Wallet help

Wallet help explains how a request is processed. This privacy policy explains what transaction references, names, mobile numbers and reconciliation records may be stored during that handling.

06

Support page

Support content shows how to contact us. This privacy policy explains how support messages are stored, who may read them and when we may keep case history.

07

Regional access

Access wording can vary by supported region and local law. This privacy policy explains how location signals and account eligibility checks may be used when access is requested.

Layout cues that explain privacy

We place privacy cues where they help you make a decision. The page uses short badges, plain headings and direct contact routes so you can find...

Short policy badges

The badges near the opening section highlight the main record types: account data, device checks, session history and Pakistan wallet context. They help you scan the privacy scope before reading deeper.

Plain section labels

Each section label is written to signal its privacy role, from data use to contact paths. We avoid vague wording so you know whether a section affects access, storage or support.

Contact cards

The contact cards separate account inbox, email and live chat routes. That layout helps you choose the route that shares the smallest amount of personal data needed for your request.

Consistency table

The comparison area explains how this policy connects with other legal pages. It keeps privacy duties separate from account rules, wallet help and promotional wording, which reduces confusion.

FAQ placement

Common privacy questions sit at the end so you can resolve practical concerns after reading the main policy. Each answer stays focused on data collection, use and contact rights.

Local context chips

JazzCash, Easypaisa, SadaPay and Raast appear as context chips because wallet records can carry personal data. The chips show which Pakistani rails may create account-linked records.

Privacy questions before you join

We collect details you provide, such as mobile number, account name and login credentials, plus device and session records needed to operate access, protect balances and respond to account privacy requests.

Wallet records can include personal data such as mobile references, transaction IDs and timing. We use them to reconcile JazzCash, Easypaisa, SadaPay and Raast activity linked to your account.

No. We do not sell your personal data. Limited partners may process assigned records for hosting, verification, fraud screening or analytics, but they must use those records only for that assigned work.

Send the request through your account inbox where possible. Tell us which record looks wrong, provide the correct detail, and we will check whether the change is allowed under record duties.

Retention depends on the record type. Security logs, wallet references and support cases may be kept while needed for account safety, dispute handling, legal duties and active service checks.

We will assess which records can be deleted and which must be retained for legal, security or transaction reasons. If full deletion is not possible, we explain the remaining record category.