Your 2jet privacy terms
2jet keeps your privacy choices visible before you open your account and while you use our lobby from Pakistan. This policy explains what account data we collect, why...
How our privacy policy works
This Privacy Policy applies when you access 2jet in supported regions and where local law permits. We collect details you provide, such as name, contact data, account settings, payment references, device signals, session logs, and support messages. We use that data to create and protect your account, process withdrawals, keep records required for platform security, respond to your requests, and improve the
way our privacy controls work. We do not sell your personal data. Some service providers help us with hosting, fraud checks, payment routing, analytics, and customer care, and they receive only the data needed for that task. When you ask us to correct or remove data, we check the request against account safety, transaction records, and applicable legal duties before acting.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
How we keep policy clear
Our privacy text is written from the account flow we operate, not from a generic template. We check it against login behaviour, payment references, support records, cookie use...
Account flow mapping
We connect each privacy clause to an actual account step, such as registration, login, profile edits, withdrawal checks, or support...
Payment data limits
Wallet and bank references are handled as transaction records, not as open access to your financial apps. We store what...
Device security signals
We may read device type, browser data, IP patterns, and login timing to spot unusual access. These signals help protect...
Cookie control wording
Our cookie wording explains functional, analytics, and preference use in plain English. You can adjust browser settings, though some account...
Support record care
Messages to support can include contact details, screenshots, or account context. We keep those records only as needed for the...
Update cycle
When our data handling changes, we update this page rather than hiding changes in scattered account screens. The current wording...
Privacy across our pages
This page works beside our terms, cookie wording, account help text, and promotion rules, but it stays focused on personal data. If another page describes a feature, this...
Privacy layout you can scan
We designed this privacy page so you can find the data point you care about without reading unrelated service copy. The layout separates collection, use, sharing...
Clear section labels
Each block uses a plain label so you can move from account data to cookies, support records, or privacy rights without guessing where a subject is hidden in the page.
Short privacy badges
The hero badges name the main privacy areas before the longer text begins. They help you confirm that account data, cookie choices, security checks, and local contact paths are covered.
Local wording
Pakistan payment references are named where they affect privacy records, including JazzCash, Easypaisa, SadaPay, and Raast. This keeps the policy tied to the account flow you actually see.
Actionable contact cues
Contact cards explain which route fits which privacy request. That saves time when you need account correction, access help, payment reference checks, or a written response from our team.
Plain data categories
We avoid vague labels where possible and name the practical data categories, such as profile details, device signals, payment references, session logs, and support messages connected to your account.
Change awareness
When privacy handling changes, this page is where we clarify the update. You can return here to see how current account, support, and security data practices are described.