Privacy Policy

Tab Atlas does not collect, sell, or transmit browsing information to its developer or third parties. It processes open-tab information locally, on your own device, to provide its tab-organization features.

Tab Atlas does not collect, transmit, sell, or share personal data or browsing information with its developer or third parties.

What Tab Atlas stores locally

Time machine recording is enabled by default. Tab Atlas automatically records changes to folders, active saved links and their order locally, including saves from the popup and page context menu while the dashboard is closed. Archived links are excluded from ordinary snapshots and the timeline. You can pause or turn off recording in its options menu; that choice is kept after restarting. Browser tab activity, browsing history, website contents, settings, scroll positions and manual workspace snapshots are excluded. No Chrome browsing-history permission is requested.

Snapshots and the protected return point for Undo are stored in the separate tab-atlas-collections-history IndexedDB database. History has a 20 MiB accounted payload budget and is trimmed towards 16 MiB as it fills, keeping the latest protected return point. There is no fixed maximum age; available depth depends on collection size and changes. Physical database overhead and browser origin quotas apply separately. You can pause or turn off recording, or explicitly clear snapshots and protected Undo from Time machine options → History storage. Clearing history leaves current folders, saved links, archive and browser tabs unchanged. Regular backup files do not include history. Removing the extension removes its local history.

Restoring changes active Atlas collections and protects the exact preceding state separately for durable Undo, including the prior archive state of reactivated links. Restored links return active to their original folder without duplicating the same currently archived identity. Other current archived links stay unchanged. Undo after newer edits requires confirmation and protects those newer edits too. A restore receipt, collection revision and generation are stored locally to recover interrupted operations. Older collection history is migrated to active-only snapshots while preserving recorded moments and protected Undo data. Opening a saved historical link is a separate action in the current normal browser window; restoration does not create browser windows or record browser activity.

Saving a page from the toolbar popup or the page context menu stores its title and URL in your chosen folder on this device. One latest quick-save result and Undo record are retained locally so you can undo the save after reopening the popup. After you confirm a popup save or invoke the page context menu, a temporary notification is inserted into that page using access granted by your action. It removes itself afterward, does not extract website content, and makes no network requests. A local copy of your theme and sound settings keeps feedback consistent with the dashboard. Save and Undo sounds are packaged locally and can be disabled with Sound.

When you use the save, folder, workspace, theme, or shortcut features, Tab Atlas stores the relevant data using Chrome's local storage (chrome.storage.local) and the browser's localStorage. This may include:

• URLs and page titles of tabs you explicitly save for later or archive
• Folder names and the pages you file into them
• Workspace snapshots (window layouts and the tabs they contain)
• Your theme choice, privacy-mode state, and editable shortcuts

All of this remains on your device and is never sent to the developer or any third party.

What Tab Atlas does not do

• No analytics or telemetry
• No advertising
• No accounts or sign-in
• No cookies
• No remote APIs, analytics, or server-side storage of your tabs
• No automatic external resource requests (fonts, icons, and scripts are all packaged locally)

Optional folder sharing

When you explicitly choose to share a folder, Tab Atlas creates a compressed encrypted copy in the link's fragment (the part after #). It does not upload that copy or retain it on a server. It may remove known tracking parameters where safe and excludes sensitive and local-network links by default; signed URLs are left unchanged.

The link contains an encrypted copy of this folder. Anyone who has the complete link can decrypt, view, and import it. Encryption prevents casual reading and detects changes; it does not restrict recipients and does not provide revocation, expiry, or server-side access control.

Site icons (favicons)

Tab Atlas displays site icons using Chrome's built-in local favicon cache (the _favicon API). It does not contact the sites themselves or any third-party icon service to fetch them.

Data use

• Data is not sold to third parties.
• Data is not used for any purpose unrelated to the extension's core functionality.
• Data is not used for creditworthiness or lending purposes.

Retention and your control

Locally saved data stays until you remove it. You can delete saved items and archive entries directly in the extension, clear the extension's local storage, or uninstall the extension to remove everything. Backup files are exported and imported only at your explicit request, and they are ordinary local files on your computer.

Contact

Questions about privacy can be submitted through the project's public issue tracker: github.com/Haperone/tab-atlas/issues.