How th9 protects your account data
th9 keeps your privacy choices, account checks and payment records in one clear policy, so you know what we collect before you open your account where local law...
Privacy policy for Pakistan access
This Privacy Policy explains how we collect, use, store and share data connected with your th9 account, device, session activity, support messages and payment records. When you create or access an account, we may process your name, contact details, login signals, verification material, wallet references and transaction status so we can run account security, handle requests and meet record duties that apply
where local law permits. We do not sell your personal data. We share limited data only with service partners who help us operate account access, payment processing, fraud checks, hosting, analytics or customer care. Your choices include asking us to update inaccurate details, seeking access to stored records, or asking how a specific data use applies to you.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Privacy help from our team
If your privacy question needs a direct answer, contact us with the email or account handle linked to th9. We may ask for a secure match before discussing private records, because support threads can include account, wallet or verification details.
Privacy email
Use the privacy contact on th9.onl for requests about access, correction or erasure. Include your account handle and the data concern, but never send full wallet PINs, card images or one time codes.
Account chat
When you contact us through account chat, we connect the thread to your session so our team can check the right record. Chat logs may be kept for dispute handling and security checks.
Wallet query path
For JazzCash, Easypaisa, SadaPay, NayaPay or Raast privacy questions, share only the reference ID and time. We use those details to trace status without asking for secret wallet credentials.
How we keep this policy current
We treat this Privacy Policy as an active account document, not a static page. Our operations, security and support teams check wording against live account flows so the policy matches what you...
Operational ownership
The policy is maintained by the teams that manage account access, wallet reconciliation and support handling. That helps each clause reflect real th9 processes rather than vague privacy wording copied from a template.
Local wording
We write for Pakistan in clear English, using names such as JazzCash, Easypaisa, SadaPay, NayaPay and Raast only where those records may appear in your privacy file.
Security alignment
Login alerts, device checks and password reset records are described in the same way our account tools create them. This keeps your privacy reading aligned with the security screens you actually use.
Limited sharing
Partner sharing is described by purpose, such as hosting, analytics, payment status checks or fraud prevention. We avoid broad wording so you can see why a partner may touch your data.
Change control
When the policy changes, we update the page date and adjust account prompts where needed. Major changes may be shown inside th9 before they affect how your data is processed.
Plain retention
Retention wording explains why some records stay for account disputes, wallet tracing or legal duties. We remove or reduce data when it no longer serves a valid operational need.
Consistent privacy wording across th9
Our related legal pages use the same privacy vocabulary so you do not have to decode different terms. The Privacy Policy remains the main source for data handling...
| Cookie wording | Cookie clauses describe session tools, preference storage and analytics tags in the same language used here. That consistency helps you connect browser settings with account privacy choices on th9.onl. |
|---|---|
| Terms references | If our terms mention verification, disputes or wallet checks, they link those actions to this Privacy Policy. The legal duty may sit elsewhere, but the data handling explanation stays here. |
| Promo records | When campaign pages mention account rewards or eligibility checks, they do not create a separate privacy rule. We treat those records under the same account data and retention clauses shown here. |
| Support scripts | Support responses follow the same limits as this policy: verify the account, discuss only the needed record, and avoid asking for secret wallet credentials or one time codes. |
| Payment references | Wallet names appear only as record context. JazzCash, Easypaisa, SadaPay, NayaPay and Raast references help explain tracing, reconciliation and security checks, not unrelated account promotion. |
| Device language | Device and browser terms stay consistent across login screens, cookie prompts and this policy. That matters when you ask why a session, IP region or device signal was stored. |
| Update notices | Where a connected legal page changes how data is collected or shared, we update this Privacy Policy or point you to the current clause before relying on that change. |
Visible privacy layout cues
We designed the policy page to make privacy choices visible before you send a request or open an account. The layout separates collection, use, sharing, storage and contact...