LEGAL REFERENCE

How td77 Handles Your Data

td77 keeps this Privacy Policy close to your account flow, so you can see what we collect before you open an account and enter the lobby where local...

Account dataDevice checksJazzCash contextRaast records
Explore Lobby Read FAQ
td77 How td77 Handles Your Data

Our Privacy Position For Pakistan

This Privacy Policy explains how we collect, use, store and share data connected with your td77 account in supported regions of Pakistan. We use your details to create access, protect your sign-in, confirm age eligibility under applicable rules, process identity checks, handle withdrawals, respond to support requests and keep transaction records required by service providers. Payment references may include wallet names, masked

numbers, timestamps, transfer IDs and status updates from rails you choose. We do not sell your personal data. We limit internal access to teams that need it for account, security, finance or support work, and we keep logs so changes can be traced. If a law, bank, wallet partner or authorised authority requires a record, we may retain or disclose the relevant

part only.

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

CONTACT ROUTES

Privacy Help From Our Team

If you want to ask about your data, correct account details or understand a verification request, contact us from inside your td77...

Account chat Use in-account chat for privacy questions tied to...
Email request Send a privacy request by email when you...
Security report Tell us quickly if you see a sign-in...
POLICY CHECKS

How We Keep The Policy Accurate

Our Privacy Policy is written from the way td77 actually handles account and transaction data. We check the wording against current support flows, finance checks and security controls, then adjust it when...

Process ownership

Privacy wording is tied to teams that run account access, wallet checks and support handling. That keeps the page aligned with what happens when you contact us.

Local payment context

We name rails such as JazzCash, Easypaisa, SadaPay and Raast because those labels can appear in transaction records, status checks and withdrawal verification steps.

Access controls

Only authorised staff can view account records needed for their task. Permissions are separated between support, finance and security work to reduce unnecessary data exposure.

Change tracking

Policy edits are logged with date, purpose and owner. When a privacy process changes, we update the relevant wording rather than adding vague promises.

Security alignment

Device checks, login alerts and session records are described because they support account protection. We explain why those records exist and how they help us respond.

Plain wording

We use direct language for Pakistan, avoiding legal clutter where possible. You should understand what data is collected before you share it with td77.

Consistency Across Our Policy Pages

This Privacy Policy works with our related legal pages, but it has its own job: explaining data handling. When another page discusses account rules or cookies, we keep...

Terms link
Our terms describe account rules, while this page explains the personal data behind those rules. The two pages are aligned without repeating every clause.
Cookie wording
Cookie content focuses on browser storage, device signals and session use. This Privacy Policy explains how those signals connect with account security and analytics.
Verification flow
Identity checks may be mentioned in several places, but this page states why documents, phone markers or transaction records may be requested and retained.
Wallet records
Payment pages may show available rails, while this page explains the data trail: masked numbers, transfer IDs, status messages and reconciliation records.
Support handling
Support pages explain contact choices. This policy explains what we can see when you contact us, and why verification comes before account data is shared.
Security wording
Security content may describe sign-in protection. Here we explain the privacy side of logs, device identifiers, suspicious activity checks and restricted staff access.
Update rhythm
When any related page changes a data process, we check this policy for matching wording. That keeps your privacy reading consistent across td77.
VISIBLE SIGNALS

Policy Layout You Can Scan

We design this page so you can find privacy details without digging through unrelated copy. The layout separates collection, purpose, storage, sharing and contact routes, making it easier...

Short badges The badges near the hero show the main data areas...
Clear sections Each section covers one privacy task, so you can move...
Local language We write in clear Pakistani English and use rail names...
Contact cues Support routes are placed inside the policy page because privacy...
Plain data labels We use labels such as login logs, masked wallet number...
Decision support Before you open an account, this layout helps you understand...

Questions About Your Privacy Rights

We collect account details, contact markers, device data, login records, transaction references and support messages. If verification is needed, we may ask for documents or wallet proof relevant to your request.

Payment records help us match your td77 account with transfers made through rails such as JazzCash, Easypaisa, SadaPay and Raast. We use masked details and status markers where possible.

Yes, you can request access to data linked with your account. We verify your identity first, then share the relevant records we can provide under applicable law and provider rules.

Retention depends on the record type. Account, transaction, security and support records may be kept while needed for service delivery, dispute handling, legal duties, fraud prevention and finance reconciliation.

We share limited data with service providers that support payments, security, hosting, analytics or customer help. Each sharing step is connected to your account flow or a legal requirement.

Contact us through your account and explain what needs changing. We may ask for proof before updating phone, wallet or identity details, especially when withdrawals or security checks are affected.