Privacy by Design,
Not by Policy.
TabLogger is built on a simple philosophy: your browsing habits are your business. We don't want your data, so we architected an app that physically cannot see it.
Core Privacy Pillars
How we ensure your data stays yours.
100% Local Storage
Your data lives and dies on your machine. All logs are stored within your browser's IndexedDB. When you click "Remove Extension", every byte of data we've ever collected is instantly and irreversibly destroyed by the browser itself. We have no cloud backups.
No External Servers
We literally cannot "phone home" because there is no home to phone. TabLogger has:
- close No Backend Database
- close No Analytics SDKs
- close No Tracking Pixels
Strict Permissions
We request strictly what is necessary to detect tab events. We do not ask for "management" permissions that would allow us to close or modify your tabs.
Open & Transparent
Don't trust our words, trust our code. Our repository is public, and our production code is unminified for easy verification.
Permission Breakdown
manifest.json
"tabs"
Why do we need this? expand_more
This is the core permission required to function. It allows the extension to listen for onCreated, onUpdated, and onRemoved events. Without this, we cannot know when you open or close a tab. We specifically use this to read the Title and URL for your dashboard visualization.
"storage"
Why do we need this? expand_more
This permission allows us to save your settings (like dark mode preference or chart configurations) and access IndexedDB to store your local history logs. This data never leaves the storage.local area of your browser.
"alarms"
Why do we need this? expand_more
We use alarms to periodically clean up old data based on your retention settings (e.g., "Delete history older than 30 days"). This ensures your browser doesn't get bogged down with infinite logs.
TabLogger operates entirely within the strict sandboxed environment of the Google Chrome Extension architecture v3.