tabonomy.Privacy Policy
Last updated: 2026-07-26
Tabonomy organizes browser tabs, keeps an Archive of closed tabs, and exports video transcripts when asked. Grouping and search run on your device.
The short version
- Your tabs and Archive stay in your browser.
- Tabonomy has no account system, analytics, advertising, or tracking.
- Tabonomy does not request browser-history or cookie access.
- Network use is limited to model downloads, Chrome preference sync, and transcript or export actions you start.
Data stored by the browser
| Data | Storage | Purpose |
|---|---|---|
| Tab titles, URLs, and derived metadata | chrome.storage.local | Organizing open tabs |
| Archive records and cleanup receipts | chrome.storage.local | Finding and restoring closed tabs |
| Text embeddings and grouping results | chrome.storage.local | Local grouping and search |
| Downloaded model files | Browser OPFS cache | Avoiding repeated downloads |
| Theme, grouping mode, thresholds, and protective settings | chrome.storage.sync | Remembering settings; Chrome may sync these between your signed-in profiles |
| Optional video progress: video ID, URL, title, position, duration, update time, and completion state | chrome.storage.local | Showing where you left off after you enable the feature |
| Local failure counters | chrome.storage.local | Diagnosing optional enrichment; they contain no tab titles, URLs, or event stream |
Video progress is off by default and requires consent on each device. It excludes Shorts and incognito windows, retains no raw pause or seek history, expires after 90 days, and is capped at 1,000 records.
Network requests
- Chrome preference sync. Chrome may sync non-sensitive settings stored in
chrome.storage.sync. Tab titles, URLs, Archive records, embeddings, video progress, and diagnostic counters are not stored there. - Model download. On first setup, Tabonomy downloads about 200 MB of model files from
huggingface.coorhf.coand caches them in OPFS. No tab data is included. After a failed load, a smallHEADrequest may check whether that model host is reachable. - Transcript request. When you request a transcript, Tabonomy fetches captions and basic video metadata from YouTube or Bilibili. The request identifies that video. Transcripts are not fetched automatically.
- Obsidian export. Markdown is saved through Chrome downloads or a folder you choose. If you configure Obsidian Local REST API, Tabonomy sends the note to the host and port you provide; the default is
127.0.0.1on your machine.
That is the complete list for this release. Fonts are bundled with the extension. Favicons come from Chrome's cache, not an icon service.
Bilibili login
Tabonomy never reads or stores cookies. During an explicit Bilibili transcript export, the subtitle request runs in the open video page, where the browser may attach your existing Bilibili session. Tabonomy receives the subtitle list, not your credential. Public subtitles still work without a login.
What Tabonomy does not do
- Sell, rent, advertise with, or build server-side profiles from your data.
- Transfer data outside the Chrome-managed and user-requested uses disclosed above.
- Use or transfer data to assess creditworthiness or for lending.
- Send analytics, browsing history, progress, or diagnostics to Tabonomy.
- Read Chrome history or cookies.
- Create an account or sync your Archive to a Tabonomy server.
Retention and deletion
- Restorable tabs recorded in Archive can be reopened while retained. Re-closing the same page updates its record instead of creating endless duplicates.
- Video progress expires after 90 days or 1,000 records. Disabling the feature clears it.
- Clear browsing data deletes Archive records, closed-tab history, embeddings, transcripts, analyses, video progress, and manual category choices. It preserves settings, custom groups, and downloaded model files. Tabonomy verifies the deletion before reporting success.
- Uninstalling Tabonomy removes its
chrome.storage.localdata and OPFS cache.
Changes
Material changes appear here with a new date. A future hosted feature would require new disclosure and consent; it would not upload existing local history by default.
Contact
Questions: hi@tabonomy.app