Privacy Policy

TabDog ("the extension") is a tab manager Chrome extension that helps you search, organize, and manage your browser tabs. This policy explains what data the extension accesses and how it is used.

Data the Extension Accesses

To provide its functionality, the extension accesses:

Tab metadata: tab URL, title, favicon URL, active state, and window/tab IDs
Recently closed sessions: tabs you've recently closed (via the Sessions API)
Browsing history: your last 7 days of browsing history (via the History API)
Local timestamps: tab creation/open times (stored locally in the browser)

How the Data is Used

The extension uses this data only to:

Display, search, and manage your open tabs in the popup
Group tabs by domain and sort by last accessed time
Show and reopen recently closed tabs
Display browsing history with search and date grouping
Save and restore tab sets as workspaces

Cloud Sync (Optional)

If you choose to sign in with Google, the extension uses chrome.identity for authentication and stores the following in Google Firestore:

Your workspace data (workspace name, color, and saved tab URLs/titles)
Your device identifier (browser name and a generated ID)
Your open tab list (for cross-device sync)

This data is associated with your Google account and is used only to sync your data across your own devices. Background sync runs at regular intervals via the chrome.alarms API.

You can use TabDog without signing in. When not signed in, all data stays 100% local on your device.

Data Sharing & Selling

The extension does NOT sell user data to anyone
The extension does NOT share user data with third parties
The extension does NOT use any analytics or tracking
The extension does NOT transmit data to any server other than Google Firestore (only when signed in)

Permissions

tabs — Read and manage open tabs (title, URL, favicon, activate, close, create)
sessions — Retrieve recently closed tabs for quick reopening
history — Display browsing history from the last 7 days
storage — Save preferences, workspaces, and tab timestamps locally
identity — Google OAuth sign-in for optional cloud sync
alarms — Schedule background sync and session history snapshots

Storage

Local data is stored in chrome.storage.local on your device, including: tab creation timestamps, UI preferences, workspace data (when not signed in), and session history snapshots. This data is automatically cleaned up as needed.

Security

Authentication is handled through Chrome's built-in identity API using Google OAuth. Cloud data is stored in Google Firestore with security rules that restrict access to each user's own data. No custom backend servers are involved.

Changes to This Policy

This policy may be updated over time. Updates will be reflected in this document with a new effective date.

Contact

For questions or concerns about this privacy policy, please open an issue on our GitHub repository.