TabZen icon Privacy

TabZen Privacy

Your sessions, tab metadata, and recovery snapshots stay on your device unless you explicitly export them.

Last updated: December 2025 Zero tracking Open source
Back to TabZen View Source
Short version

Your tabs stay local

TabZen does not transmit session data to external servers. Saved sessions, recovery points, and settings remain in browser storage unless you deliberately export a JSON backup yourself.

All Extensions Privacy Ask on GitHub

Privacy details

Overview

TabZen helps you manage tabs with auto-save, named sessions, and search.

To deliver that, it needs access to your open tabs and local browser storage, but not to any external service.

Permissions Explained

  • storage stores sessions, settings, and recovery data locally on your device.
  • tabs reads your open tabs so the extension can save sessions and power search.
  • alarms runs the local auto-save schedule every 5 minutes.

Local Storage Only

All TabZen data is stored in chrome.storage.local.

  • No automatic sync across devices by default.
  • No cloud backend or server-side session copies.
  • No access for us to inspect your saved tabs.

Network Activity

TabZen makes zero network requests. There is no sync service, analytics endpoint, or remote account layer.

That is intentional: the safest tab data is the data that never leaves your browser.

What we do not do

✓ We do not collect browsing analytics or usage metrics.
✓ We do not send your tabs or sessions to external servers.
✓ We do not require an account for core functionality.
✓ We do not inject ads or sponsored suggestions.
✓ We do not sell data because there is no backend data store.

Changes

If this policy changes, this page will be updated. Given the product direction, significant privacy changes are unlikely.

Questions

If something is unclear, open an issue on GitHub or go back to the TabZen page.