Reference
Extension permissions
Map each Chrome permission in Tab Organizer App to its task, processed data, and storage or data-flow boundary.
Chrome permissions describe which browser APIs an extension may call. They do not by themselves say that every accessible value is stored or sent elsewhere, so this reference pairs the manifest with behavior observed in this version.
Permission overview
| Permission | Product task | Data involved | Destination or persistence |
|---|---|---|---|
tabs | List, search, activate, move, group, and close tabs; focus, merge, and restore windows | Open-tab URLs, titles, state, and position; window membership, position, and size | Processed in the extension; selected fields also appear in local history and sessions |
tabGroups | Read, create, update, and collapse native groups | Group title, color, membership, and collapsed state | Applied to Chrome Tab Groups; captured in sessions |
storage | Keep settings, usage history, assignments, and recent sessions | Preferences, counters, group data, and complete recent sessions | Chrome local or sync storage, depending on the field |
system.display | Map saved windows to display work areas | Display bounds, work areas, and metadata | Captured in session objects and files |
alarms | Schedule badge sync and assignment cleanup | Schedule identifiers and timing | Browser alarm scheduling; no direct page-content access |
sidePanel | Open Tab Organizer App in Chrome's Side Panel when that host is selected | Same interface data as the popup | Presentation in the Side Panel; no extra network access |
favicon | Show the site icons of open tabs | Address of the tab the icon belongs to | Read from Chrome's local icon cache; no request to the tab's website |
The manifest has no content scripts and no host permission. Window features need no separate permission in Chrome. Tab access still exposes sensitive current-browser data through the tabs API, which is why the scope should be evaluated directly rather than inferred from host permissions alone.
Tab access
The tabs and tabGroups permissions work together:
- grouping reads a tab's domain and page title, then assigns unpinned tabs;
- search matches displayed open tabs and activates the selected tab;
- multi-window tools move tabs and focus or merge windows;
- cleanup closes only tabs included in a confirmed action; and
- session capture records tab, group, and window structure.
system.display supplements session capture and restore with monitor geometry. It does not grant access to screen pixels.
Storage access
Observed examples in chrome.storage.local include:
- tab access counts and last-access timestamps;
- domain-to-group assignments;
- language, theme, filter, view, sync, and Auto-Collapse settings;
- up to five complete Recent Sessions and recovery snapshots; and
- your grouping rules, your context profiles with the active profile, and renamed groups including any extra domains you assign. These are stored here only. Rules and extra domains can contain the names of sites you visit.
Local extension storage persists beyond the current popup session and can be removed when extension data is cleared or the extension is uninstalled. Do not use it as your only backup.
Sync access
This version uses chrome.storage.sync for custom group names, group colors, and the oversized-group split settings. Chrome, rather than the Tab Organizer App website, operates that sync mechanism under the active Chrome profile.
Grouping rules, context profiles, the active profile, and renamed groups with their extra domains are not written to sync storage. If an older version left a copy there, the extension takes it over into local storage once and does not read it again; the copy is not deleted. To move rules and profiles to another device, use Export backup (JSON) there and Import backup (JSON) here.
Open tabs, tab access counts, domain-to-group assignments, and Recent Sessions are not written to sync storage either.
The extension handles quota and storage errors. If Sync Storage Full appears, the attempted custom-group update might not be saved; remove unused groups or shorten names and retry.
Native Tab Groups Sync (BETA) is different from Chrome storage sync:
- Tab Groups Sync (BETA) applies extension assignments to the current browser's native groups.
- Chrome storage sync stores supported custom-group settings through Chrome.
Privacy details
For storage locations and website separation, read Data flows and Extension privacy.
A static review of the delivered package found no bundled analytics SDK. That observation is version-bound; it is not a claim that Chrome, Chrome Sync, the Web Store, or user-opened external links perform no processing.