Sessions, not tab bloat.
Save a working context as a named session, suspend it to reclaim memory, and bring the whole thing back exactly as you left it.
- Named sessions
- Memory suspension
- Full-text tab search
Tab Hive
In development — Sessions, not tab bloat.
Nothing hidden in the permissions dialog
Here is every permission Tab Hive requests, why it needs it, where your data goes, and whether any of it involves an account or our servers.
What it asks for, and why
Where your data goes
Tabs and session dataonly if you turn it on
Planned to be stored locally on your device by default, and to leave it only for sessions you choose to sync or share. Final data practices will be published here before launch.
Accounts and what runs on our serversAccount for paid plans
Tab Hive is designed to be fully usable without an account — sessions live in local extension storage and restoring one is a local operation. Syncing a session between your own machines, or sharing one with someone else, cannot be done on the device alone, so those features are expected to require an ExtHive account and to store session data on our servers. This is the intended design; it will be confirmed on this page before launch.
Session syncOpt in
Planned as opt-in. Would store your session list — page titles and URLs — on our servers so your devices match.
Shared sessionsOpt in
Planned as opt-in and per session. Sharing a session necessarily uploads the tabs in it to the people you share it with.
Tab Hive is on the way
Tell us you want it and we will email you the moment it lands in the store. One email, then nothing else.