TabSidecar runs locally in your browser and is built to help you manage tabs and windows with local-first defaults. This page reflects the current audited build as of June 2, 2026.
TabSidecar is a tab and window management extension. Its main purpose is to help you organize open tabs, restore windows, auto-park inactive tabs, save browser state, and export your own backup files.
Based on the current code audit, most extension data is stored locally in the browser using the extension's own IndexedDB database. The current code also includes two outbound data flows: optional AI-generated window titles sent to TabSidecar's API, and an optional email submission during onboarding sent to a Supabase backend.
tabs: used to read, organize, move, create, focus, pin, and close tabs.windows: used to inspect, name, restore, focus, create, and remove browser windows.alarms: used for scheduled extension tasks such as auto-park checks and delayed processing.history: used to search browser history for closed-URL backfill and to support history deletion features triggered by the user.favicon: used to display site icons for tabs and saved items.downloads: used to export backup files that you choose to generate.The current host permissions are https://api.tabsidecar.com/* and https://ymvkvyfsrcdkkpkcicfd.supabase.co/*.
TabSidecar does not currently request permissions for cookies, identity, bookmarks, microphone, camera, geolocation, or broad host access to arbitrary websites. It also does not read page contents, keystrokes, form fields, or passwords from websites.
Based on the current codebase, TabSidecar primarily stores data locally in the extension's own IndexedDB database. That local data may include open tabs, windows, saved windows, auto-parked tabs, closed URLs, settings, labels, nicknames, saved-for-later items, and similar organization metadata.
When you export backup files, the extension generates those files locally and saves them through Chrome's download system. The current code excludes the install-scoped AI userId from exported settings backups.
api.tabsidecar.com containing an install-scoped random identifier, simplified tab information for the current window, and existing window titles so the service can return a generated title.ymvkvyfsrcdkkpkcicfd.supabase.co.TabSidecar does not currently include third-party advertising SDKs, behavior analytics SDKs, cross-site tracking pixels, or general-purpose telemetry platforms. We also found documentation describing possible future cloud backup architecture, but that documentation does not appear to be an active user-facing backup upload feature in the current build.
TabSidecar uses information to display, search, sort, and organize your tabs and windows, auto-park inactive tabs, restore windows and layouts, save your labels and preferences, generate local backup exports, generate optional AI-based window titles if enabled, and collect an optional onboarding email address if you choose to submit one.
Based on the current code audit, TabSidecar does not sell your personal information. The current code sends data to external service providers only in the limited cases described above: the TabSidecar API for optional AI window titles and Supabase for optional onboarding email capture.
You can choose whether to use the AI window-title feature, choose whether to provide an email address during onboarding, export your own backup files locally, remove extension data by uninstalling the extension or clearing extension storage through Chrome's extension controls, and manage browser history separately through Chrome.
Local data remains in the extension's local storage until you delete it, overwrite it, clear the extension's data, or uninstall the extension. Exported backup files remain wherever you save them. If you submit an onboarding email or use the AI title service, data sent to those services may be retained by the relevant backend according to operational needs and applicable law.
TabSidecar stores most working data locally inside the browser extension environment. No software can guarantee absolute security, but the current architecture limits always-on remote transmission by keeping most tab-management data on device unless you use a feature that specifically sends data to a backend service.
TabSidecar is not directed to children under 13, and we do not knowingly design it to collect personal information from children.
This Privacy Policy may be updated as the product changes. If future versions add cloud backup, accounts, or additional remote services, this policy should be updated to reflect those changes before or when those features ship.
For privacy questions about TabSidecar, contact support@tabsidecar.com.