Account terms
Our account terms explain eligibility, access and account duties. This privacy page explains the data side of those same actions, including what we collect and why we need it.
LEGAL REFERENCE
How We Handle Your Data
top1 keeps your account, device, contact and transaction data within a clear privacy flow, so you know what we collect before you open an account. This policy explains...
Account data scopeDevice security checksJazzCash contextRaast transaction records
Policy Position For Pakistan Access
This Privacy Policy explains how we collect, use, store and protect data connected with your top1 account in supported regions of Pakistan. We collect details you give us, such as your name, phone number, email address and account credentials, plus operational data created when you access the lobby, request support, pass checks or use supported payment channels. We use this data to
keep your account accessible, confirm transaction ownership, answer privacy requests, detect unusual account activity and meet record duties where local law permits. We do not sell your personal data. When a payment reference involves JazzCash, Easypaisa, SadaPay or Raast, we keep only the records needed to reconcile your account, respond to queries and maintain an audit trail.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
CONTACT ROUTES
Privacy Requests And Help Paths
If you want to ask about your data, update account details or question a transaction record, contact us through the support route linked to your account. We ask for proof that the request is yours before changing or sharing privacy-related data.
Team online
Account inbox
Send your privacy request from the email or phone number linked to your account. That helps us match the request to your profile without exposing data to another person.
Live support check
Use chat for urgent privacy concerns such as unknown access or a wrong contact detail. We may move sensitive requests to email so a written record stays with your account.
Payment reference help
For JazzCash, Easypaisa, SadaPay or Raast questions, include the reference code and time. We use those details only to locate the matching account record.
POLICY CARE
How We Keep This Policy Accurate
We write this policy from our own operating process, not from a generic template. The privacy wording is checked against account access, payment reconciliation, support handling and security logging so the page...
Operator written
The policy reflects the data points we handle during account creation, login, verification, support contact and transaction checks. We keep the language practical so you can understand each purpose.
Local payment context
Our privacy wording names JazzCash, Easypaisa, SadaPay and Raast because those references may appear in account records. We explain their role without treating them as broad data sharing channels.
Access logging
We record device, browser and connection signals to help identify unusual account access. Those logs support account security and are handled under the same privacy limits as other account data.
Support handling
Support staff see only the account details needed for your request. More sensitive privacy actions need extra checks before data is corrected, disclosed or removed where the law allows.
Retention checks
We keep records only for account operation, dispute handling, security and legal duties. When a record is no longer needed, we remove it or reduce it from active systems.
Policy updates
When our account flow, support tools or payment record process changes, we update the policy wording. The latest version on this page is the version we apply.
CONSISTENT TERMS
How This Policy Stays Aligned
This page sits beside our account terms, cookie wording and support rules. We keep those pages aligned so the privacy promises here match the way your account is opened, checked, accessed and...
Cookie wording
Cookie wording covers browser storage, session handling and measurement tags. This policy connects those technical details to account security, page performance and your privacy choices.
Support rules
Support rules explain how we answer account questions. This policy adds how your identity is checked before privacy data is discussed, corrected or shared with you.
Payment records
Transaction records connect account activity with JazzCash, Easypaisa, SadaPay or Raast references. This policy explains why those records are kept and how they are limited.
Security process
Security wording covers passwords, device checks and unusual activity. This policy explains the data signals behind those checks and how they support account protection.
Regional access
Access may depend on supported regions and local rules. This policy applies when we provide access where local law permits and explains the related account data handling.
Change process
When related pages change, we check whether the privacy wording must change too. That keeps your account rights and our data practices in the same place.
Policy Layout You Can Scan
We designed this privacy page so you can find the data topic you need without reading unrelated copy. The structure moves from collection and purpose to...
Plain section labels
Each heading tells you which privacy topic is being covered, such as contact routes, record keeping or security checks. We avoid vague labels so you can locate the relevant paragraph faster.
Account-first wording
The copy explains data through real account actions: creating access, verifying ownership, contacting support and checking transaction records. That makes the policy easier to connect with your own account journey.
Local context chips
Short chips mention JazzCash, Easypaisa, SadaPay and Raast where payment references matter to privacy. They signal context without turning the policy into a payment page.
Request reminders
Privacy request paths are repeated only where they help you act. We explain which channel to use, what proof may be needed and why identity checks protect your data.
Security cues
Security cues explain device logs, session checks and unusual access signals in privacy language. You can see why data is collected without having to guess from technical terms.
Update clarity
When the policy changes, the page wording is adjusted to match our current account process. We keep the newest policy visible so you know which version applies.
Privacy Questions Before You Join
We collect account details you provide, device and access signals, support messages, verification records and transaction references. The exact data depends on how you create and use your account.
Payment references help us match JazzCash, Easypaisa, SadaPay or Raast activity to your account. We use them for reconciliation, query handling, security checks and audit needs where local law permits.
No. We do not sell your personal data. We use it to operate your account, provide support, protect access, process valid requests and meet record duties in supported regions.
Contact support from the email or phone number linked to your account and state what needs correction. We may request proof before changing contact, identity or payment-related records.
We keep records while they are needed for account operation, security, dispute handling and legal duties. After that, we remove them or limit them from active use where possible.
Only support staff and relevant operations staff can access messages needed to answer your request. Sensitive privacy matters may require extra checks before any account data is discussed.
Yes. The same privacy policy applies whether you access top1 on mobile or desktop. Device signals may differ, but the collection purposes and privacy limits stay the same.