Privacy Policy
Last updated July 28, 2026
The short version: TabKeeper doesn't collect, transmit, or sell any data. Everything it stores stays on your device, in your browser's local storage. There's no account, no analytics, no tracking, and no server TabKeeper talks to.
What TabKeeper stores
TabKeeper saves the following locally, using Chrome's chrome.storage.local API:
- Your settings (auto-cleanup toggle, inactivity threshold, notification preferences, theme)
- Your domain whitelist
- A history of tabs it has closed (title, favicon, URL, and time closed), so you can restore them
- Pause state and basic usage statistics (tabs closed, estimated memory/time saved)
- A per-tab timestamp of the last time you focused it, used to determine inactivity
None of this ever leaves your device. It is not synced to a server, not sent to us, and not accessible to anyone but you.
What TabKeeper does not do
- It does not read your browsing history
- It does not read the content of your tabs or pages
- It does not use analytics, telemetry, or crash reporting
- It does not request host permissions for any website
- It does not require an account or sign-in
Permissions it requests, and why
- tabs — to read tab metadata (URL, pinned/audible/active state) and to close, create, or query tabs
- alarms — to schedule the once-a-minute cleanup check without keeping a background page running
- storage — to save settings, whitelist, and history locally, as described above
- notifications — to show the cancellable warning before tabs are closed
- favicon — to display real favicons in Recently Closed, without requesting access to any site's content
Open source
TabKeeper's full source code is public, so you don't have to take any of this on faith: github.com/evans-kwofie/tabkeeper.
Changes to this policy
If this policy ever changes, the update will be reflected on this page with a new "last updated" date. Given TabKeeper's design — no server, no accounts, no data collection — that's not expected to change.
Contact
Questions or concerns: open an issue at github.com/evans-kwofie/tabkeeper/issues.