Last updated: September 2026
Tab Vault collects your browsing history — specifically, the titles and URLs of your open tabs — in order to save it. That collection happens entirely on your own device, and nothing is ever transmitted anywhere. This page explains exactly what that means.
Tab Vault reads the titles, URLs, and pinned state of your open browser tabs on a timer and saves them to chrome.storage.local — storage that belongs to your browser profile, on your own device. This is the entire dataset the extension works with, and it is what Chrome's policies classify as web browsing history.
Nowhere. Tab Vault makes no network requests of any kind. There is no server, no analytics, no third-party SDK, and no account to sign in to. The data above is collected and stored, but never transmitted, sold, or shared with anyone, including the developer. You can verify the "no network requests" part yourself: open Chrome DevTools, go to the Network tab, and use the extension. Nothing will appear there.
Tab Vault cannot read the content of any page you visit. It only ever sees a tab's title, URL, and whether it's pinned — the same information visible in your browser's own tab strip.
Icons shown next to saved tabs are read from Chrome's own local favicon cache via the browser's built-in _favicon API. This does not involve a network request to Tab Vault, to a third party, or to Google.
You can export your full snapshot history to a JSON file at any time, using the Export button. That file is written directly to your Downloads folder by your browser. Tab Vault has no part in transmitting it anywhere, because it doesn't have the ability to.
If this policy ever changes — for instance, if a future paid feature like cloud sync is added — this page will be updated first, and the new version will describe exactly what data that feature sends and where.
Questions about this policy can be sent to the developer contact address listed on the Chrome Web Store listing.