Privacy policy
Explains what personal data we collect, why we use it, how long records may remain and which requests you can make about your account information.
This Privacy Policy explains how tc777b collects, uses, stores and protects information connected with your account in Pakistan. We keep the policy focused on practical choices, including account...
tc777b collects details you provide when opening or maintaining an account, such as your name, contact details, date of birth, login credentials and records needed for account verification. We also receive technical data, including device type, IP address, browser settings, session times and security events, to protect access and maintain accurate service records. Where local law permits, we may use this data
to process account requests, assess unusual activity, answer support messages, meet legal duties and improve privacy controls. Payment references from JazzCash, Easypaisa, SadaPay and Raast may be linked to transactions, but sensitive authentication credentials remain with the relevant payment provider. We retain records only for as long as needed for the stated purpose, legal obligations, dispute handling or security. You may contact
us to request access, correction or clarification, subject to lawful verification and applicable Pakistani requirements.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
We wrote this policy around the records our service actually needs to operate an account. That includes authentication events, support history, transaction references and device signals used for security. We do not...
We record login and session events to help confirm that account access matches expected activity. These records can support security checks when a new device, location or password event appears.
When verification is required, we use the submitted details for account protection and legal checks. Access to these records is limited to authorised processes, with requests handled through your account contact route.
JazzCash, Easypaisa, SadaPay and Raast references help us match account activity without requesting your provider password or personal authentication code. Provider-side security remains managed by the relevant payment service.
Messages, case dates and resolution details help us answer repeated questions without asking you to start from the beginning. We retain these records only for service, security or lawful operational needs.
Browser, device and connection signals help identify automated abuse, suspicious sessions and broken account flows. We use these signals for protection and service stability rather than for unrelated personal profiling.
If our handling practices change, we will update this page and show the effective date or a clear account notice where appropriate. The latest wording explains which version applies to your activity.
Privacy questions often overlap with account access, security and transaction records, but each policy page has a separate purpose. This page explains personal data handling, while related pages may describe account rules...
Explains what personal data we collect, why we use it, how long records may remain and which requests you can make about your account information.
Sets out the conditions connected with opening, maintaining and using an account. It may refer to privacy duties but does not replace this data-handling explanation.
Focus on passwords, access events, device checks and urgent account protection. They describe protective action rather than the wider purposes for retaining personal data.
Concern account entries and payment references linked with JazzCash, Easypaisa, SadaPay or Raast. This policy explains how related personal data is handled around those records.
Help us resolve your request and may contain account details supplied during contact. This policy covers how those conversations are used, stored and accessed.
A changed date or notice indicates that wording has been updated. We encourage you to read the current page when your account activity or local requirements change.
You can ask about access, correction, deletion or processing where applicable. We may verify your identity first so a private account record is not shared incorrectly.
The policy layout is built to help you find the part that matches your question quickly. Short labels identify the data purpose, while the supporting text explains the...