Privacy Policy

01

What Tabnook is

Tabnook is a Chrome extension that saves and manages your tab groups locally. It tracks your open Chrome tab groups, saves them when they close, and lets you reopen them with one click. It also provides per-tab and per-group notes and a snooze function that brings groups back on a schedule you set. All of this runs entirely within your Chrome browser on your machine.

Tabnook is developed by Loupely LLC. This policy describes how the extension handles data. It covers the extension itself, not any website or service hosted separately.

02

What data Tabnook collects, and how

Tabnook reads tab and tab group metadata through Chrome’s standard tabs and tabGroups APIs. It does not inject content scripts, does not read page content, and does not access any data inside the pages you visit.

What is captured automatically. By default, for every tab, Tabnook stores only the site origin: the scheme and host, for example https://example.com. It does not store the page title, URL path, or query string for sites you have not explicitly trusted.

Full capture, which stores the complete URL and page title, happens only for domains you have manually added to your trusted list in the Tabnook side panel. The trusted list is empty by default. If you never configure it, every site is captured minimally.

What you type yourself. Group names and notes are entered by you and stored as you type them. Tabnook does not reduce or filter user-typed content, because you control what you write. If you type sensitive information into a note, that information is stored in your browser’s local database.

Preferences. Settings such as your display theme, density, and trusted domain list are stored in chrome.storage.sync. Chrome syncs this across your signed-in browsers automatically through Google’s own infrastructure. Tabnook does not control this sync and does not receive a copy of it.

03

Where data is stored

Storage area	What lives there	Persists?	Syncs?
IndexedDB	Groups, tab snapshots, notes, snooze schedules, write intents. System of record.	Yes, on your machine	No
chrome.storage.session	Live mirror of currently open groups and a change token. Cleared when the browser closes.	No	No
chrome.storage.local	Hot flags, pre-migration backup slot.	Yes, on your machine	No
chrome.storage.sync	Preferences only: theme, density, and your trusted domain list.	Yes	Yes, via Chrome/Google

All group and tab data lives exclusively in IndexedDB, local to your Chrome profile on your machine. It is not synced and is not accessible to Tabnook’s developer or any third party.

04

What Tabnook does not collect

No page content. Tabnook does not read or store the text, images, or other content of the pages you visit.
No full URLs by default. For untrusted sites, only the site origin (scheme and host) is stored. Path, query string, and fragments are discarded.
No page titles by default. Page titles are stored only for domains you have explicitly added to your trusted list.
No browsing history. Tabnook does not access your browser history. It only reads metadata for tabs and groups that are currently open.
No analytics or telemetry. Tabnook collects no usage data, error reports, or performance metrics. No data of any kind is sent anywhere.
No personally identifiable information. Tabnook does not request your name, email address, payment information, or any identifier. There is no sign-in.
No cookies. Tabnook does not set or read any browser cookies.
No third-party code. Tabnook ships no third-party libraries, SDKs, or remote scripts. No external code runs inside the extension.

05

Transmission off your device

Tabnook makes no network requests of its own. It does not contact any server, including Loupely LLC’s own infrastructure. There is no Tabnook backend, no analytics endpoint, and no remote logging.

The only data that leaves your machine is your preferences, which Chrome syncs through its own account infrastructure when you are signed into Chrome. This sync is controlled by your Google account settings, not by Tabnook. Tabnook has no access to that data in transit or at rest on Google’s servers.

When you use the export feature, Tabnook produces a JSON file on your machine, on demand, by your action. That file goes wherever you save it. Tabnook does not transmit it anywhere.

06

Permissions Tabnook requests

Permission	Why it is requested
`tabs`	Reads tab metadata (URL and title, governed by the capture policy) to track and save tab groups.
`tabGroups`	Reads and manages Chrome tab group names and colors.
`storage`	Reads and writes `chrome.storage.local`, `chrome.storage.session`, and `chrome.storage.sync` for preferences.
`unlimitedStorage`	Lifts the default storage cap so Chrome does not evict IndexedDB data under disk pressure.
`alarms`	Fires snooze timers to reopen groups at the time you set.
`sidePanel`	Runs the Tabnook interface in Chrome’s native side panel.
`notifications`	Notifies you when a snoozed group wakes and reopens.
`contextMenus`	Adds Tabnook actions to the right-click context menu.

Tabnook does not request history, cookies, webRequest, identity, or any host permission. It does not read the content of web pages.

07

Data sharing

Tabnook does not share your data with anyone. There are no third-party services integrated into the extension, no advertising partners, no data brokers, and no analytics providers. Loupely LLC does not sell, rent, or transfer your data in any form.

The only indirect exposure is through Chrome’s own sync mechanism for your preferences, which is governed by Google’s privacy policy and your Google account settings.

08

Data retention and deletion

Tabnook stores data until you delete it or uninstall the extension.

Soft deletes. When you delete a group, note, or snooze record, Tabnook marks the record as deleted rather than removing it immediately. These tombstones are permanently removed after 30 days. This gives you a window to undo a deletion and keeps exported data clean.

Full reset. You can clear all Tabnook data from the extension’s settings panel. This removes all groups, notes, snooze records, and preferences stored by the extension.

Uninstalling. Removing Tabnook from Chrome removes all data stored by the extension in chrome.storage. Data in IndexedDB associated with the extension’s origin is also removed when the extension is uninstalled. Preferences that were synced through chrome.storage.sync may persist in your Google account; you can remove them through Chrome’s sync settings.

09

Encryption

Data stored locally by Tabnook in IndexedDB and chrome.storage is not encrypted at rest by Tabnook. This is a deliberate design choice: Tabnook’s minimal-by-default capture policy avoids storing page-level content for most sites, which reduces what an unencrypted store contains. Without a user passphrase, locally stored encryption offers limited practical protection, and a passphrase requirement would add friction that contradicts Tabnook’s design as a lightweight, zero-friction tool.

A person with physical access to your machine and access to your Chrome profile directory can read the data Tabnook has stored. This is the same access posture as your bookmarks and browser history.

Tabnook transmits no data, so there is nothing to encrypt in transit.

10

Export

Tabnook can export all your data as a JSON file. This export is produced locally, by your action, and saved wherever you choose. The file contains your groups, notes, snooze schedules, and preferences in plain text. It is not transmitted anywhere. Handle it as you would any file containing your browsing context.

11

Children

Tabnook is not directed at children under 13, and we do not knowingly collect any information from children. The extension collects no personal information from anyone.

12

Changes to this policy

If this policy changes in a material way, we will update the “Last updated” date at the top of this page and, where appropriate, note the change in the extension’s release notes. Continued use of the extension after a change constitutes acceptance of the updated policy.

We do not anticipate significant changes to this policy while Tabnook remains a local-only, zero-account tool. Any future version that introduced a server, an account, or external data transmission would require a substantially revised policy before shipping.