Terms page
Our Terms explain account rules, while this Privacy Policy explains the data used to run those rules. If a rule needs verification, we state the data purpose here.
th 7 explains exactly how we collect, use, store and protect the data tied to your account, device, wallet activity and support chats. Before you open your account...
This Privacy Policy applies when you access th7.onl, open an account, verify your profile, make wallet requests, use support, or browse our lobby where local law permits. We collect only the data needed to run your account, process local wallet activity, protect access, answer privacy requests and keep records required for fraud checks or legal duties. Your phone number, email, device signals,
login history, wallet reference numbers and support messages may be used for these purposes. We do not sell your personal data. When we share data with payment, security or hosting partners, we limit it to what they need to perform that specific task for th 7.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Privacy questions need a clear route, not a generic reply queue. We give you separate contact paths for access requests, correction requests, deletion requests and account-security concerns, then match your request to the account details you provide before taking action.
Use [email protected] when you want access, correction, or deletion help. Include your account email and phone number so we can match the request without asking for extra data.
If you ask through chat, our team moves privacy matters to a secure ticket. We never ask for full wallet PINs, card secrets, or one-time codes there.
For login or device concerns, contact support and mention privacy in the subject. We check recent access records before changing data or closing a request.
Our Privacy Policy is written from the way th 7 actually operates. We describe account checks, wallet references, security logging and support handling in practical terms, so you know what happens to...
Each data category is linked to a clear purpose, such as account access, wallet records, fraud checks, support replies or legal duties. We avoid collecting data without an operational need.
Only trained team roles can view sensitive account records. Support can see enough to help you, while wallet and verification details stay restricted to authorised operational queues.
JazzCash, Easypaisa, SadaPay and Raast references are stored as transaction records, not open wallet access. We use them to trace requests and resolve mismatched account details.
We log device and session signals to spot unusual access. These records help us secure your account, investigate disputes and reduce unauthorised activity across supported regions.
When privacy rights are requested, we verify that the request belongs to you. This protects your account from another person asking for changes or copies of data.
We keep records only for operational, dispute, security and legal timelines. When a record is no longer needed, we remove it or separate it from direct account identity.
This page connects with other th 7 legal pages, but it has one job: explain privacy. Where another page explains account use, cookies or payments, this page explains the personal data behind...
Our Terms explain account rules, while this Privacy Policy explains the data used to run those rules. If a rule needs verification, we state the data purpose here.
Cookie wording covers browser storage and similar tools. This Privacy Policy connects those tools to session security, preferences and analytics that help us maintain account access.
When you update your profile, we separate the account change from the privacy record. The policy explains what is kept, why it is kept and who can access it.
Wallet pages describe transaction steps. This policy explains how JazzCash, Easypaisa, SadaPay and Raast references are stored, matched and used for support or dispute checks.
Security wording explains protection controls. The Privacy Policy explains the personal data behind those controls, including login signals, device identifiers and unusual access checks.
The contact page routes common questions. Privacy requests follow stricter identity checks, because access, correction and deletion actions can affect your account records.
Where local law permits, we use regional signals to manage availability and compliance tasks. This policy explains what those signals are and how long we keep them.
We structure this Privacy Policy so you can find the part that affects your account without reading unrelated material first. Each visible marker points to a specific privacy...