Privacy Policy

Tab Debt makes no network requests. Not to us, not to anyone. There is no server to send your data to, because there is no server.

Tab Debt · Chrome extension · Last updated 2026-08-03

What Tab Debt can see

To do its job, Tab Debt reads metadata about your open tabs:

It does not read the content of any page. It has no content scripts and no host permissions, so it has no ability to see what is on a page — only that the tab is open.

What Tab Debt stores, and where

Everything is stored in chrome.storage.local, which lives on your computer inside your Chrome profile:

None of it is synced. chrome.storage.sync is not used, so nothing crosses between your devices or touches Google's sync servers.

What Tab Debt sends

Nothing.

This is enforced, not merely promised. A check runs on every build and fails the build if fetch, XMLHttpRequest, WebSocket, EventSource, navigator.sendBeacon, importScripts or any remote URL appears anywhere in the shipped code. A lint rule bans the same globals in source. The extension's content security policy (script-src 'self') blocks remote code even if something slipped through.

Third parties

There are none. No service providers, no processors, no advertisers, no partners. Your data is never sold, shared, rented or disclosed, because it never leaves your machine.

Your control

Children

Tab Debt is a browser utility with no accounts, no content and no communication features. It collects nothing from anyone, of any age.

Changes

If this policy ever changes, the change ships with a new version of the extension and this page is updated in the public repository alongside it. Since the extension has no network access, a policy change cannot retroactively affect data that was never transmitted.

Contact

Questions or concerns: open an issue on the project's GitHub repository.