Add to Chrome

Privacy policy

Last updated August 18, 2026

Tabsa is a local tool. There is no account to make, no server to talk to, and nothing about you to collect — so most of this page is about what does not happen.

What Tabsa stores

Your bundles, the tabs in them, the descriptions you write, and your settings. All of it lives in your own browser, in IndexedDB, on the device you are using. It is never uploaded, and Tabsa has no way to read it from anywhere else.

What Tabsa does not do

  • No account, no sign-in, no identifiers of any kind
  • No analytics, no telemetry, no crash reporting
  • No advertising, and nothing sold or shared with anyone
  • No network requests at all — Tabsa contacts no server, including ours

The permissions it asks for

Two, and each one does exactly one thing you can see.

  • tabs — to read the titles and addresses of the tabs in your window, so a bundle can mirror it, and to open and close tabs when you ask.
  • favicon — to show each saved page’s icon from the copy Chrome already has. This is why a tab list never asks a third party what a site looks like.

Page content

Tabsa never reads the content of your pages. It sees a tab’s title and address, which is what the tab strip shows you, and nothing more.

Backups you make

Export writes a file to your computer. Where that file then goes is up to you — Tabsa does not send it anywhere and cannot see it again unless you import it.

This website

tabsa.app is a static site with no analytics and no cookies. The uninstall survey is the only page that sends anything anywhere, and only if you choose to submit it.

Changes

If this ever changes, the date at the top changes with it, and anything that would send data off your device would be opt-in and asked for plainly.

Getting in touch

Questions about any of this go to [email protected]