Your privacy is not a feature.
It's the foundation.
TabBye โ Auto Tab Timeout was built from day one with a simple rule:
your data belongs to you โ and only you.
No exceptions. No asterisks.
We collect no personal information. TabBye does not collect, transmit, or store any personally identifiable information (PII). This includes but is not limited to: names, email addresses, IP addresses, device identifiers, location data, or browsing history.
Tab URLs and titles processed during auto-close checks are evaluated entirely in memory, on your device, in real time. They are saved to your local Graveyard storage only โ never sent anywhere else.
All data generated by TabBye โ including Graveyard entries, user settings, focus mode preferences, whitelist rules, and usage statistics โ is stored exclusively in your browser's chrome.storage.local API. This data is sandboxed to your device and is not accessible by any other extension, website, or external party.
The Graveyard stores up to 500 tab entries locally. Older entries are automatically pruned when the limit is reached. You may clear all data at any time via Settings โ Clear Graveyard.
TabBye does not collect data from anyone, including children under the age of 13. Since no data is collected at all, TabBye is fully compliant with COPPA and similar child privacy regulations by design.
If this privacy policy is ever updated, the new version will be included in the extension update and the "Last updated" date will be revised accordingly. Any material change that could affect your data rights will be clearly communicated in the extension's update notes.
Our core commitment will never change: no data collection, no external servers, no tracking. If that ever became impossible to maintain, we would discontinue the extension rather than compromise it.
TabBye's source code is available for review. We encourage security researchers, developers, and privacy-conscious users to audit the codebase and verify every claim made in this policy. Trust shouldn't require blind faith โ it should be verifiable.