Privacy Policy for tu 45 accounts
tu 45 puts your account privacy in clear terms before you open an account: what we collect, why we collect it, and how long we keep it. This...
How we handle your data
This Privacy Policy explains how tu 45 handles personal data connected with your account, lobby access, transaction checks and support requests in supported regions of Pakistan. We collect details you provide, such as your name, contact data and account credentials, plus technical records such as device type, IP region, session activity and security alerts. When you use JazzCash, Easypaisa, SadaPay or Raast,
we record transaction references, timing and status so your account balance and withdrawal checks can be matched accurately. We do not sell your personal data. We share limited data only with service partners who help us verify access, process transactions, protect accounts or respond to privacy requests, and we keep those partners bound to defined handling rules.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Privacy contacts for your account
If you want to ask about your data, update account details or request a copy of records we hold, contact us through the route already linked to your tu 45 profile. We check the request against account ownership before sharing any data, because privacy contact is only useful when it protects the right person.
Account email
Send us your account email, last login time and a short privacy request. We use those details only to locate your profile and send a response through the same channel.
Live chat privacy queue
Open chat from your logged-in account and ask for privacy help. Our team can confirm the request path, explain needed proof and avoid exposing account data inside an open chat window.
Transaction reference help
For JazzCash, Easypaisa, SadaPay or Raast privacy queries, share only the reference code and date. We do not ask for wallet PINs, full card data or private app passwords.
How we keep policy wording current
Our privacy wording is maintained by the team that handles account security, transaction matching and Pakistan support contact. That matters because the policy should match the actual account...
Account-flow alignment
We map the policy against the real join, login and withdrawal screens, so the data we name here matches the...
Security wording check
We describe device checks, session logs and unusual-access alerts in plain language. This helps you understand why we keep technical...
Pakistan support input
Our support team flags recurring privacy questions from Pakistan accounts, including wallet references and identity checks. Those patterns help us...
Partner access limits
Where a service partner helps with verification, hosting or transaction status, we limit access to the data needed for that...
Retention checks
We keep account, security and transaction records for as long as needed for service, legal handling and dispute response, then...
Plain English edits
We write privacy changes in clear Pakistani English, with direct examples from account access and local transaction flow, so you...
Aligned with every tu 45 policy
This Privacy Policy works beside our account terms, cookie wording and promo rules, but it stays focused on personal data. If another page explains what you may do...
| Account terms connection | Our account terms explain access rules; this policy explains the personal data used to create, secure and maintain that access, including verification details and login records tied to your profile. |
|---|---|
| Cookie wording connection | Cookie wording covers browser storage and measurement tools. This page explains how those technical signals can connect with your account, security checks and privacy choices on tu45.net. |
| Promo rules connection | Promo rules may mention eligibility checks. This policy explains the data used for those checks, such as account status, region signals and transaction records, without changing promo conditions. |
| Withdrawal process connection | Withdrawal checks use identity, wallet and transaction references to protect account ownership. This policy explains why we keep those records and when support may ask for matching details. |
| Security page connection | Security wording covers account protection steps. This policy adds the privacy layer, including device records, login alerts and the limited sharing needed to monitor unsafe access patterns. |
| Support page connection | Support channels help resolve account questions. This policy explains how chat, email and ticket data are stored, who can access them and how they support your privacy requests. |
| Regional access connection | Access may depend on supported regions and where local law permits. This policy explains how region signals are processed for account safety, availability checks and service records. |
Visible privacy cues across the page
We design this legal page so you can find privacy details without hunting through unrelated copy. The layout uses short labels, local context chips and direct contact cards...