TabLoom accesses the following information solely to provide its core features. None of this data ever leaves your device.
All data TabLoom saves — sessions, suspension settings, autosave snapshots — is stored in Chrome's local extension storage (chrome.storage.local) on your own device. This data:
TabLoom does not transmit, collect, or send any of your data anywhere. There are no analytics, no telemetry, no crash reporting, no remote configuration calls, and no external API calls. The only times a page on our website may open are: (1) on first install, when a single welcome page (tabloom.net) opens once in a new tab; and (2) when you click the in-app help (“?”) button, which opens our usage guide on tabloom.net. Both are normal page loads that you initiate or can close, and neither sends any of your data. Apart from these user-facing pages, the extension operates entirely on your device.
The table below explains every permission TabLoom requests and exactly why it is needed.
| Permission | Why it's needed |
|---|---|
| tabs | Required to read your open tab list (URLs and titles) for display, duplicate detection, copying, exporting, and session saving. Also used to close duplicate tabs and navigate suspended tabs back to their original URLs. |
| storage | Required to save and restore your tab sessions, suspension settings, and autosave snapshots — all stored locally on your device only. |
| clipboardWrite | Required only so the Copy buttons can place your selected tab URLs onto the clipboard when you click them. TabLoom never reads your clipboard. |
| alarms | Required to run the auto-suspend timer and autosave task in the background without the popup needing to stay open. Chrome's MV3 service workers are terminated when idle; alarms are the correct API to schedule periodic work. |
| contextMenus | Required to add the right-click menu option that lets you add or remove the current page from a saved session without opening the popup. |
| offscreen | Required to enable clipboard writes from the background service worker. Manifest V3 service workers cannot access the clipboard directly — an offscreen document is the Chrome-approved way to do this. Used solely to power the Copy Tabs feature; no other purpose. |
TabLoom contains no third-party JavaScript libraries, frameworks, or trackers. All functionality is written from scratch using standard browser and Chrome Extension APIs. The only third-party asset is the Manrope font, which is bundled locally inside the extension and used under the SIL Open Font License 1.1. The font is never loaded from any remote server.
Saved sessions and settings persist in local storage until you delete them within the extension or uninstall TabLoom. No data is retained on any external server — there are none.
Because TabLoom collects, stores, and transmits no personal data of any kind, there is no personal information for us to access, export, correct, or delete on your behalf. You remain in full control: all data lives locally and can be cleared at any time by removing the extension or clearing its storage. This design means TabLoom has nothing to disclose or process under privacy regulations such as the GDPR (EU) and the CCPA/CPRA (California).
TabLoom does not collect any personal information from any user, including children. The extension is compliant with COPPA — it does not knowingly collect data from children under 13.
Any future changes to this privacy policy will be reflected on this page with an updated effective date and version number. Significant changes will be noted in the extension's update changelog.
Questions about this privacy policy? Reach the developer directly: