LEGAL REFERENCE

Privacy Policy for your tc77 account

tc77 keeps account setup, live casino activity, sportsbook entries and Pakistan payment records inside one privacy framework, so you can see what we collect before you open an...

Pakistan data handlingPayment record contextAccount privacy controlsSupport chat privacy
tc77 Privacy Policy for your tc77 account

How we handle your data

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

CONTACT PATHS

Where privacy questions go

If you have a privacy request, send it through the channel linked to your account so we can verify you safely. We separate privacy queries from general chat, then pass identity checks, correction requests and deletion requests to the team that handles account records.

Team online

Live chat handoff

Start with live chat when you are signed in. We confirm basic account details, record the privacy topic, and move your request to the data team without asking for payment passwords.

Email privacy desk

Use our privacy email when you need a written trail. Include your account ID, Pakistan mobile number, and the data action you want, but never send card images or app PINs.

Payment query route

For JazzCash, Easypaisa, SadaPay or Raast privacy concerns, support checks the transaction reference first. We only view the records needed to trace the account event.

CHECKED WORDING

Why this policy is maintained

We keep this Privacy Policy practical, not decorative. Our product, support and security teams check the wording against the way tc77 accounts actually work, including login records, device...

Account flow mapping

We match policy wording to each account step, from mobile number entry to verification prompts, so you can see why...

Security log checks

Login time, device type, IP area and failed access attempts help us protect your account. The policy names these records...

Payment trail clarity

Where JazzCash, Easypaisa, SadaPay or Raast references are used, we state the reason clearly: verification, dispute tracing, withdrawal checking or...

Support transcript care

Chat and email records may include sensitive context. We keep them tied to the case, restrict internal access, and remove...

Policy change control

When we update this page, we check whether collection, storage or sharing has changed. Cosmetic edits are separated from changes...

Regional law wording

Access language is written for supported regions and where local law permits. That keeps the policy aligned with Pakistan account...

How related policies stay aligned

Our legal pages use the same account facts but serve different purposes. This Privacy Policy explains personal data handling. Other pages may cover cookies, website terms or promotions...

Cookie page linkCookie wording explains browser storage and device recognition. This privacy page connects that tracking to account security, session continuity and your choices when non-essential tools are offered.
Terms alignmentTerms describe account use and platform rules. This page focuses on the data created by those actions, including identity checks, login records and support messages.
Promotion recordsIf a promotion creates an account entry, this policy explains how that record is stored, checked and retained. The promotion page should not change your privacy rights.
Payment referencesPayment content may name JazzCash, Easypaisa, SadaPay and Raast. This policy explains which related records we process and why they may be kept after settlement.
Support standardsHelp pages may tell you how to contact us. This policy states how those chats, emails and attachments are logged, protected and used for account care.
Security noticesSecurity pages may mention device checks or password resets. Here we explain the privacy side: which signals are processed, who may access them, and how long they matter.
Change messagesWhen another legal page changes, we check this policy for conflicts. If privacy handling changes, the update belongs here and should be easy to spot.

Visible parts of this policy page

This page is arranged so you can scan privacy topics quickly before going deeper. The layout highlights what we collect, why we use it, who may...

Plain summary blocks

Short blocks introduce each privacy topic before legal detail appears. They help you decide whether the section covers account creation, security, payment records or support chats.

Local context chips

Chips name Pakistan routes such as JazzCash, Easypaisa, SadaPay and Raast only as privacy context. They show where transaction references may connect to account records.

Request prompts

Request prompts point you toward correction, access or deletion routes. They also remind you which account details are needed so we can verify you before making changes.

Retention cues

Retention cues explain why some records stay after account activity ends. Fraud checks, dispute handling and financial reconciliation may require limited storage under applicable rules.

Sharing labels

Sharing labels separate internal access from processor access. That distinction matters when support tools, hosting services or payment verification partners touch parts of your account data.

Update date area

The update area tells you when privacy wording last changed. If a change affects data collection or your choices, we aim to make that clear on this page.

Common questions about privacy

We collect account details, mobile number data, login signals, device records, activity history, support messages and payment references needed for verification, security, dispute handling and account services in supported regions.

We use JazzCash and Easypaisa references to confirm transaction status, match payments to your account, trace disputes and support withdrawals. We do not ask for wallet PINs or app passwords.

We share limited data with service providers that help run hosting, security, support and payment verification. They receive only what is needed for that task and must handle it safely.

Yes, where local law permits, you can ask us to correct inaccurate account data. We may need verification first, especially when the change affects identity, payment records or withdrawals.

Retention depends on the record type. Security logs, payment references and support cases may be kept while needed for fraud checks, disputes, account audits or legal record duties.

We use access controls, session checks and device signals to reduce unauthorised access. Internal access to sensitive account records is limited to teams that need it for service or security.

Contact support from your signed-in account or email the privacy desk with your account ID and request type. We verify you first, then respond through a secure channel.