LEGAL REFERENCE

th77 Privacy Policy for Pakistan

th77 keeps your account, lobby, device and payout privacy details in one plain policy for Pakistan. Before you open an account, you can see what data we collect...

Pakistan privacy scopeAccount data usePayout record handlingRequest channels
th77 th77 Privacy Policy for Pakistan

How We Handle Your Data

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

CONTACT ROUTES

Privacy Contact Paths at th77

If you want to ask about access, correction, deletion, or retention, use the same account details you used with th77 so we...

Privacy email Send your privacy question with your account name...
Account chat Use in-account chat when you can still access...
Payment record checks For JazzCash, Easypaisa, SadaPay or Raast privacy questions...
POLICY CHECKS

How We Keep This Policy Clear

We write this policy from the operator side, using the same flows you see inside th77: account creation, device login, lobby activity, payment reference checks, support tickets, and...

Account field mapping

We connect each privacy clause to a real account field, such as phone, email, device ID, session data, or payout...

Local rail handling

JazzCash, Easypaisa, SadaPay and Raast references are stored for reconciliation, fraud checks, and support follow-up. The policy separates those records...

Access control

Internal access to privacy records is role based. Support can see what is needed to resolve your request, while sensitive...

Retention tracking

We keep different record types for different periods depending on account status, transaction disputes, security alerts, or lawful duties. The...

Security logging

Login attempts, device markers, IP details, and session timestamps help us detect account misuse. These logs are treated as privacy...

Policy change record

When the wording changes, we update the date and keep the new text aligned with current th77 account flows. Major...

How Our Policy Pages Stay Aligned

The Privacy Policy sits beside our other legal pages, but it has a separate purpose: it explains data handling. Where another page mentions access rules, promotions, wallet use...

Terms page linkTerms explain your account relationship with th77. This policy explains the data behind that relationship, including identity fields, session logs, support messages, and transaction references tied to your account.
Cookie page linkCookie text covers browser storage and analytics tags. This Privacy Policy connects those tags to broader privacy purposes, such as session continuity, security checks, and service measurement.
Promotion rules linkPromo rules may require account checks before rewards appear. This policy explains the data use behind those checks, including eligibility markers, duplicate-account signals, and support records.
Wallet terms linkWallet terms describe transaction handling. This policy explains the privacy side of payment references, including why JazzCash, Easypaisa, SadaPay and Raast identifiers may be retained.
Security page linkSecurity text explains account protection steps. This policy explains the personal data used for those steps, such as login logs, device signals, verification codes, and suspicious activity flags.
Support policy linkSupport rules cover response handling. This policy explains how support conversations, attachments, timestamps, and request outcomes may be stored so your issue can be handled with proper context.
Account closure linkClosure terms explain how access may end. This policy explains which records may remain after closure, especially security logs, transaction references, dispute material, and lawful retention files.
VISIBLE MARKERS

Privacy Page Elements You Can Check

This page is built so you can scan privacy points before opening your th77 account and return later when you need a specific answer. The layout highlights scope...

Scope badge The page states that the policy applies to th77 account...
Data category cards Account details, device records, transaction references, support messages, and security...
Sharing reasons Where sharing is needed, the policy explains the reason, such...
Retention cues Retention wording explains why some records stay longer than others...
Request prompts The contact section tells you what to include and what...
Update date The policy area shows when privacy wording changes. We use...

Privacy Policy Questions Answered

We collect details needed to create and secure your account, such as contact fields, login records, device markers, verification status, and support history. Extra records may be created when you use wallet rails.

We use payment references to match account activity, resolve disputes, check suspicious behaviour, and support payout requests. We do not need your wallet PIN, app password, or full screenshots showing hidden codes.

Yes, you can request correction when account details are inaccurate. We may verify your identity first, then update editable fields while keeping required security logs and transaction references intact where needed.

Limited technical data may pass to game or platform providers so sessions load, errors are diagnosed, and results are recorded. We do not share more than needed for the relevant account function.

Retention depends on the record type and reason. Support messages, security logs, payout references, and dispute files may follow different periods because each has a different operational or lawful purpose.

Contact us through privacy email or in-account chat, include your account identifier, and describe the request clearly. Never send wallet PINs, one-time codes, full identity scans, or unrelated screenshots.