Privacy Policy
Orbe Browser ("Orbe", "we") operates orbebrowser.com and the Orbe antidetect browser. This policy explains what we collect, why, and your choices. We keep data collection to the minimum needed to run the service.
Information we collect
- Account email. Used to create your account, sign you in, and send service emails.
- Google sign-in data. If you choose "Sign in with Google", we receive your Google account's email and a stable account identifier (the Google "sub"). We request only the
emailandprofilescopes. We do not access your Gmail, Drive, contacts, or any other Google data. - Device verification data. When you verify a computer or phone for your account, see Device verification below.
- Minimal security logs. IP address, browser user-agent, and timestamps of sign-ins and key actions, used to secure your account and detect abuse.
- Earlier payment records. Orbe no longer takes payments. If you made a payment before Orbe became free, we keep that record for accounting. We never take custody of your wallet or private keys.
What stays on your device, and what our server keeps
Each profile's cookies, browsing history, saved logins, site data and downloads stay on your own computer. We do not upload your browsing content.
Each profile's fingerprint is issued by our server, and the server keeps a record of it linked to your account ID: the fingerprint settings themselves (for example browser version, screen, graphics, fonts, time zone and language), a coarse description of the computer it was issued for (operating-system version, GPU maker, memory), the country it was set up for, the profile's ID in the app, when it was issued, any problem reports the app sends about it (you can turn reports off in the app's settings), and whether it uses one of your slots for a proxy from another provider (not the proxy address or password). We keep this to issue the profile, keep it consistent, and make sure the same fingerprint is never issued twice.
When you delete a profile in Orbe, or release profiles on the Profiles page, the record is marked as released and its proxy slot is freed; the record itself is kept so the fingerprint is not issued again. Deleting your account does not remove these records; they remain linked only to the account ID, not to your email.
Device verification
When you verify a computer or phone for your account (in the browser or the Orbe app), the page or app reads a few hardware values: the graphics (WebGL) vendor, renderer name and limits, the number of CPU cores, the memory size, the screen size and pixel ratio, the color depth, and the operating system and Chrome version. It does not read your files, your browsing, or your installed fonts.
- Linked to your account we keep: a one-way keyed code (HMAC) made from your account ID together with the graphics renderer, CPU cores, memory and operating-system class; a coarse device class (GPU maker and architecture, operating-system class, memory class, screen class) and a label made from it; a one-way keyed code of this browser's or app installation's random ID, used to limit how many accounts can be linked to one computer; whether it was verified in the browser or the app; and the dates it was first and last seen. The raw hardware values are not stored with your account. You can remove a device under Devices; it is then marked as removed and no longer counts toward your devices, and the record is deleted when you delete your account.
- Not linked to your account we keep the hardware values themselves, keyed only by a one-way code of the installation's random ID, with the month they were received — no account, email or IP address. We use them to keep browser profiles realistic. They are deleted 24 months after they were last received.
- In the browser, the random installation ID is kept in a cookie named
orbe_hw(about 13 months). - Orbe app for Windows (version 1.0.19 and later). When the app connects to orbebrowser.com, it sends a machine code (the
X-Orbe-Machineheader) together with the app installation's random ID. The machine code is a one-way hash made on your computer from its network adapter (MAC) address, computer name and operating system; these values themselves are never sent and cannot be recovered from the code. We use it only to verify a computer the first time it signs in to your account: it is kept with that device's record, and its first 8 characters label the device in the verification email. The app sends these headers only to orbebrowser.com, never to other sites.
How we use information
- To provide, maintain, and secure the service and your account.
- To authenticate you (including via Google sign-in).
- To send service emails: email verification, sign-in alerts for a new device, and account notices. You always receive account-security emails.
What we do not do
We do not sell your personal data, and we do not use it for advertising.
Sharing
We share data only with the providers needed to run the service — for example our email delivery and, if you use Google sign-in, Google — and where required by law. We do not share your data with anyone else.
Security & retention
Data is encrypted in transit (HTTPS). Passwords and tokens are stored hashed, never in plain text. We keep account data while your account exists and for a short period afterward as needed for security and legal obligations.
Your rights
You can access your account data from your dashboard and delete your account at any time under Account in your dashboard, or by emailing support@orbebrowser.com. Deleting your account removes your account data from our systems, except the profile fingerprint records described above (kept linked only to the account ID) and earlier payment records kept for accounting.
Contact
Security or data reports only (privacy, account deletion): support@orbebrowser.com.
Changes
We may update this policy; we will post the new version here with an updated date.