Security

A tab manager sees every address you have open. TabCompass is designed so that as little of that as possible ever leaves your computer, and nothing leaves it readable.

The extension

  • No host permissions and no content scripts. TabCompass can't read or change the pages you visit. It works only with tab titles and addresses.
  • No remote code, no analytics. Without sync it makes no network requests at all.
  • Incognito tabs are never read, stored or synced.
  • The optional AI assistant sends tab titles and site names, only when you click, straight to the provider you configured with your own key. Chrome grants access to that one provider only. Tab titles are written by websites, so the model's answers are treated as untrusted: they're checked against your tabs and only ever shown as suggestions you apply yourself.
  • Settings and the extension's own pages only accept requests from TabCompass itself.
  • Insights history (which tabs were opened, used and closed) stays in the profile's local database for 30 days and is never synced or exported. With sync on, a profile shares only daily totals (how many tabs were opened, closed, unloaded and archived) and memory figures, inside its encrypted snapshot, so Insights can add up all your profiles.

Encryption

  • A random vault key (AES-256-GCM) encrypts everything that is synced.
  • The vault key is wrapped with a key derived from your passphrase using PBKDF2-SHA256 with 600,000 iterations and a random salt. The server stores only the wrapped key, so it can't decrypt anything.
  • Every payload is compressed and sealed with AES-GCM. Its associated data binds it to your account, its type and its id, so the server can't swap one profile's data for another's.
  • On each profile, the vault key is kept as a non-extractable key that page scripts can't read.
  • Passphrases must be at least 12 characters, because anyone who obtained the server's data could try to guess them offline.

What the server sees

The server sees The server never sees
An HMAC of your email, used as the account id Addresses, titles, profile names, computer names
Your email, only while it sends the sign-in link Your passphrase or the vault key
Random device ids, data sizes and timestamps Which sites you visit

Sign-in emails are sent through an email provider (Brevo), which keeps delivery logs that include the recipient address. The server's logs never contain emails, tokens or request bodies, and its web logs record paths without query strings.

Sign-in

  • Sign-in uses an emailed link plus a code you compare. The link opens a page that shows the code and asks you to press Confirm, so email scanners that open links can't sign anyone in.
  • Links work once and expire after 15 minutes. Sessions are random 256-bit tokens, stored on the server only as hashes, and end after 90 days without use.
  • The sync connection authenticates with its first message, so tokens never appear in addresses or logs.

Remote switching

When you choose a tab in another profile, an encrypted command is relayed to that profile. It can only bring a tab to the front, is rejected after 30 seconds, and can't be replayed.

Limits

5 sign-in emails per hour per address, 10 sign-in requests per minute per network address, 50 profiles and 50,000 archived tabs per account, and size limits on every message.

Reporting a problem

Found a vulnerability? Email support@tabcompass.com with "Security" in the subject. Please give us a chance to fix it before disclosing it publicly. The code is open source under the AGPL-3.0.