Privacy by design
Your tabs stay
in your browser.
TabShow uses Chrome's extension APIs to list and manage tabs. It does not read page contents, send browsing data to a server, or require an account.
The plain-language summary
TabShow runs locally as a Chrome extension. The current codebase has no TabShow account system, analytics service, advertising system, or backend that receives tab data.
- No account or sign-in.
- No host permissions.
- No access to the contents of webpages.
- No sale, sharing, or transmission of browsing data.
- No advertising or behavioral tracking.
Chrome tab metadata is still sensitive. TabShow reads only what its visible features need and keeps that work inside the browser.
Why TabShow requests each permission
| Permission | What it enables | What it does not enable |
|---|---|---|
sidePanel | Displays TabShow beside the page you are viewing. | It does not grant access to page contents. |
tabs | Reads open-tab titles, URLs, favicons, window membership, and status so TabShow can list, search, sort, preview, switch, and close tabs. | It does not grant access to the DOM, text, forms, or network traffic inside a webpage. |
tabGroups | Reads group names, colors, membership, and collapsed state so Chrome groups can be represented in the side panel. | It does not create a TabShow cloud workspace or send group data elsewhere. |
favicon | Uses Chrome's local favicon cache when a tab does not provide a usable icon. | It does not contact websites on TabShow's behalf. |
TabShow 2.0 removed the previously declared activeTab permission because the implementation did not use it.
What is stored
TabShow stores user settings such as color pairing, hover-preview delay, and current-window versus all-window scope in Chrome's local browser storage. These settings do not contain copies of webpage content.
What is processed temporarily
Open-tab metadata and group information are processed to render the list, search results, sorting, indicators, preview state, and actions you request. The extension reacts to Chrome tab events so the panel stays current.
What is transmitted
The extension code has no TabShow backend endpoint for tab information. Clicking an external link—such as the Chrome Web Store, support site, or public Featurebase board—opens that destination under its own privacy terms.
Changes to this policy
If a future TabShow release adds data collection, an account, remote processing, or a new permission, this page and the Chrome Web Store privacy disclosure must be updated before that release. The policy should always describe the shipped extension, not a marketing aspiration.
Effective date: July 22, 2026. Applies to: TabShow 2.0.