Website and extension data flows

The website and installed extension are separate execution environments. Visiting documentation does not give the website access to open tabs, and using the extension does not make the website part of its session-file flow.

Website data

Loading the Tab Organizer website sends a normal web request to its hosting infrastructure. Hosting can process request metadata such as IP address, time, requested path, user agent, and delivery logs according to the current Website privacy information. The site also sets first-party functional cookies for theme, language, and an optional get-started completion marker, and it can receive optional uninstall feedback. That is not a claim that the website processes no personal data.

Documentation search is designed to use the active locale's generated search index in the site rather than require a user account. This technical separation does not erase ordinary hosting requests made to load the page and its assets.

Extension data

This version processes current browser data through Chrome extension APIs, including:

• open-tab URLs, titles, favicons, pinned state, and activation;
• tab access counts and last-access times;
• group names, colors, memberships, and domain assignments;
• window structure, position, size, and focus;
• language, theme, filter, and view settings; and
• complete Recent Sessions, up to five, in local extension storage.

Session export writes selected captured data into a .tabsession file under your chosen file-storage flow. The file is not encrypted and can contain browsing and display-layout details. The website does not receive the file as part of export or restore.

A static inspection of the released package found no bundled analytics SDK. Default operation does not send votes. The package still declares https://votes.taborganizer.app/* for an optional backend path that ships disabled. This is a package-specific observation, not a guarantee about Chrome, synced browser services, file storage, or future releases.

Optional sync data

Two features use the word sync but have different boundaries:

Feature	What moves	Where
Chrome storage sync	Custom group names, colors or gradients, group taxonomy, grouping rules, context profiles, and split settings	Through chrome.storage.sync in the Chrome profile
Native Tab Groups Sync (BETA)	Current group assignments and group state	Between Tab Organizer and native Chrome Tab Groups through browser APIs

Grouping rules and the extra domains in a taxonomy entry can contain the names of sites you visit, so Chrome carries them as part of that sync. Open tabs, tab access counts, and Recent Sessions stay on the device. Custom-group storage can encounter Chrome Sync quota errors. Native group sync can override an existing browser group structure when activated. Neither flow is the same as uploading a session file to the website.

External media data

The current website does not embed external video and does not load third-party media frames.

The extension contains an external donation link. Following it is a user-initiated navigation to another site with that site's own data practices.

Use Website privacy for hosting details and Extension privacy for the reviewed extension-specific statement. This reference explains technical boundaries but does not replace those policies.