Last updated: November 2, 2026

Short version: TabVault keeps your archive in your own browser. There is no TabVault account, no analytics, no ads, and nothing is sold. Data leaves your browser only when you connect Notion, Obsidian, Google Sheets or DuckDB — and then it goes straight to that service.

What TabVault stores, and where

• URL, title and icon of tabs you archive; your tab-group names; when you archived them — to list, search and reopen your archive. Stored in your browser (IndexedDB).
• Notes, tags and stars you add — so you can organize your archive. Stored in your browser.
• Page description, preview image, word count, JavaScript memory use — only if you turn on "page details", for richer archives and memory estimates. Stored in your browser.
• Settings, and access tokens for services you connect — to remember your choices and write to your own Notion database or spreadsheet. Stored in your browser (extension storage, never synced).

The developer of TabVault does not receive any of this data.

When data leaves your browser

Only if you connect a destination, and only to that destination:

• Notion — archived tabs are written to the Notion database you choose, through Notion's API. If you use "Connect Notion", a small TabVault server exchanges Notion's one-time approval code for an access token and passes it straight back to your browser; it stores nothing and keeps no logs of content.
• Google Sheets — archived tabs are written as rows to a spreadsheet TabVault creates in your Google Drive. TabVault requests only the drive.file permission, so it can access that spreadsheet and nothing else in your Drive.
• Obsidian — notes are written to your vault through the Local REST API plugin on your computer, or saved as files in your Downloads folder.
• DuckDB — rows are sent to the TabVault bridge running on your own computer, or saved as files in your Downloads folder.

Each service's own privacy policy applies to data you send there.

Google user data

TabVault's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. TabVault uses Google access only to create and update your own TabVault spreadsheet. It does not read other files, does not use Google data for advertising, and does not let humans read it.

Permissions

TabVault reads open tabs to archive and manage them, keeps your archive locally, and runs optional scheduled jobs you turn on (sleep idle tabs, auto-archive). Access to page content is optional and only requested when you enable page details; you can turn it off in Settings at any time.