How 2jet Handles Your Privacy
Your 2jet account creates privacy records when you open the lobby, verify access, contact us, or use Pakistan payment references such as JazzCash, Easypaisa, SadaPay and Raast. This...
What This Privacy Policy Covers
This Privacy Policy applies when you use 2jet.bet, open an account, move through security checks, contact our team, or request account actions in supported regions. We collect only the records needed to run your account, confirm access, process service requests, prevent misuse, and meet duties that apply where local law permits. Payment names in this policy are used as context for account
records; we do not publish your wallet identity on public pages. Some data is created automatically, such as device type, session timing, language choice, and login signals. Other data comes from you, including profile details, contact messages, verification material, and payment reference text you submit for account handling.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Ask Us About Your Data
If you want to ask how your personal data is handled, contact us from the same account you use on 2jet whenever possible. That helps us match your request with the correct profile without asking for extra detail. We may need a security check before sharing account-specific records, changing contact details, or acting on a privacy request.
Account inbox
Send privacy questions through your logged-in account inbox so our team can confirm the profile, read past support history, and reply without asking you to repeat sensitive details.
Live chat privacy queue
Use chat for short privacy questions about account data, session records, or verification steps. We may move detailed requests to email when written confirmation is safer.
Email request
Email suits formal privacy requests, including data access or correction queries. Include your account name, registered contact, and the request type, but avoid sending wallet PINs.
How We Keep Policy Records Accurate
Our privacy process is written around the way 2jet actually operates: account access, verification, support handling, and payment reference checks. We check this policy against live account flows so the wording stays...
Account flow mapping
We map each privacy statement to an account screen, support action, or security check, so the policy reflects data you may actually provide while using 2jet.
Payment reference handling
JazzCash, Easypaisa, SadaPay, NayaPay and Raast references are treated as account records. We use them for matching, support checks, and transaction queries only.
Access control
Privacy records are limited to staff roles that need them for account support, verification, risk checks, or service operation. Access is logged and reduced when no longer needed.
Device signal care
Device and session signals help us recognise account access patterns, protect sessions, and diagnose login issues. We do not use these records to expose your identity publicly.
Update routine
We refresh the policy when account checks, support routing, or payment reference handling changes, so you can compare the page with your current 2jet experience.
Request handling
Privacy requests are checked against account ownership before action is taken. This protects your profile from someone asking for changes without proper authority.
How Our Policy Pages Stay Aligned
This privacy page works with our other legal pages, but it has its own purpose. It explains data collection, use, storage, sharing, and your request paths. Terms pages...
Policy Layout You Can Read Quickly
We organise this policy so you can move from the main privacy promise to the exact record type you care about. Short labels, local context, and...
Plain section labels
Headings use direct language so you can find account data, sharing, retention, and request rights without reading through unrelated service copy or promotional wording.
Local examples
Pakistan examples are included where they clarify privacy handling, such as wallet reference text, Raast labels, or support checks linked to your account.
Short record groups
We group data by purpose: account setup, access checks, support contact, transaction matching, and service security. This makes retention and use easier to understand.
Action paths
Privacy choices are linked to contact paths, so you know whether to use account inbox, chat, or email for access, correction, or deletion questions.
Change clarity
When wording changes, we keep the update visible inside the policy area, helping you see whether a privacy process has been adjusted.
Account-first wording
We write from the account flow you actually use, covering sign-in checks, profile records, support contact, and payment references rather than abstract data categories.