Tab Hammer privacy policy

Last updated November 6, 2026

Tab Hammer is a Chrome extension that shows your windows, tab groups, and tabs as an outline. It is published by Bolt Creative. This policy describes every piece of data Tab Hammer handles, where it goes, and how to delete it.

The short version: Tab Hammer has no server and no analytics. Nothing is ever sent to Bolt Creative. Your data stays in your browser, except what you choose to put in your own Google Drive (optional sync) or hand to Claude Code on your own computer (optional Claude bridge).

What Tab Hammer stores on your computer

All of this lives in your Chrome profile, in Tab Hammer's own extension storage (IndexedDB and chrome.storage), and is readable only by Tab Hammer:

Incognito: Tab Hammer never takes or stores screenshots of incognito pages. Chrome doesn't let extensions see incognito windows at all unless you turn on "Allow in Incognito" for Tab Hammer in chrome://extensions; if you do, incognito windows appear in your outline (and in sync, if it's on) like any other window, but are still never screenshotted.

Optional: sync through your Google Drive

If you sign in to sync, Tab Hammer uses your Chrome profile's Google account (through Chrome's own sign-in, chrome.identity) with one permission: drive.appdata. That gives Tab Hammer a hidden app-data folder in your own Google Drive, and nothing else: it cannot see, read, or change any of your other Drive files.

Into that folder Tab Hammer writes:

Previews (screenshots) are never uploaded. Tab Hammer talks directly to Google's Drive API (www.googleapis.com) from your browser; there is no Tab Hammer server in between. Google's handling of your Drive is covered by Google's own privacy policy.

Tab Hammer's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Optional: your other Chrome Sync devices

The devices panel can show the tabs open on your phone and other computers, as Chrome Sync reports them (chrome.sessions). Tab Hammer only reads them after you click "Show your phones and other Chrome Sync devices" and grant Chrome's permission. They are shown read-only and are not stored or uploaded by Tab Hammer; Chrome Sync itself is Google's service.

Optional: the Claude bridge

If you install Tab Hammer's MCP server for Claude Code (a separate install step; nothing happens without it), Claude Code on your computer can list, open, move, group, and close your tabs. The extension talks to a small helper program on your computer through Chrome's native messaging, and that helper talks to Claude Code over a local socket in your home folder. Nothing in this path goes through the network or to Bolt Creative.

What Claude Code does with the tab titles and addresses it reads is up to Claude Code and the model provider you use with it, under their own terms. It only reads them when it uses Tab Hammer's tools in a conversation. Hibernated and recently closed rows are never shared with it.

What Tab Hammer does not do

Deleting your data

Changes

If this policy changes, the new version will be published at this address with a new date.

Contact

Questions about this policy: support@boltcreative.com.