TabPare privacy
Privacy Policy
How TabPare handles information while organizing, identifying, closing, sleeping, protecting, and restoring Chrome tabs.
Scope
This policy applies to the TabPare Chrome extension.
- Effective date
- August 30, 2026
Information processed
TabPare installs without tab access. Before Chrome asks for the optional permission, the popup explains that TabPare checks only currently open tabs, does not access full browsing history, does not measure time spent on websites, and processes tab data on the device. Only after the user selects Enable tab cleanup can TabPare read the following information about tabs currently open in Chrome:
- The title and hostname of an eligible tab, to classify ungrouped normal web tabs in the current window for Smart organize.
- The tab URL, to match duplicate pages and restrict organization and cleanup to normal HTTP or HTTPS pages. If the user enables optional tracking-parameter matching, TabPare removes recognized tracking parameters from the local comparison while preserving all remaining parameters and their order.
- The tab's last-accessed timestamp, to identify inactive tabs and choose which duplicate to keep. TabPare compares this timestamp with the selected threshold; it does not calculate time spent on a website.
- Whether the tab is active, pinned, playing audio, already discarded, or already grouped, so TabPare can report scoped totals, include Chrome-discarded tabs in manual Close, avoid discarding them again in Sleep, protect excluded tabs, and preserve pinned and existing grouped tabs during Smart organize.
- The tab and window identifiers and tab position, so Chrome can group, close, or discard selected tabs, limit actions to their specified window, and restore the latest reversible action.
This information is processed on the user's device. Smart organize processes only eligible open tabs' titles and hostnames, not page content or the user's full browsing history. Its deterministic classifier works without a network service; when Chrome's on-device language model is already available, TabPare may use that browser-provided model to enhance the local plan.
TabPare temporarily keeps only the metadata needed for Undo in Chrome's in-memory extension session storage. It does not save page content, a browsing-history log, back/forward history, form contents, or credentials.
Settings and local records
TabPare stores only the information needed to remember user choices and report the latest cleanup:
- Chrome Sync storage: whether automatic organization or automatic duplicate cleanup is enabled, the shared automation interval, the manual inactivity threshold and unit, whether inactive cleanup closes or sleeps tabs, whether duplicate matching ignores recognized tracking parameters, and whether manual cleanup covers all windows or only the current window. Chrome may sync these settings through the user's signed-in Chrome profile when Chrome Sync is enabled.
- Local extension storage: exact protected hostnames chosen by the user and one aggregate status record for the latest cleanup or Undo operation. The aggregate record contains timestamps, operation details, and counts, but no tab URLs. Protected hostnames are not placed in Chrome Sync storage.
- In-memory session storage: after a cleanup closes tabs, the URLs and window-placement metadata needed to offer Undo; after Smart organize creates groups, the affected tab identifiers and previous positions needed to offer Undo organization. This information is not synced and is never sent to the developer or third parties.
How information is used
Tab information and saved settings are used solely to provide the user-facing functions described in the Chrome Web Store listing: report open-tab and Chrome-discarded counts for the selected scope, organize eligible tabs on demand or on the user's optional schedule, undo the latest organization, count and manually close duplicate or inactive tabs, sleep inactive tabs through Chrome's tab-discard feature, compare duplicate URLs with the user's selected matching rule, limit manual cleanup to a selected window scope, protect active, pinned, audible, or user-selected websites, restore the latest tab-closing cleanup, and run optional scheduled duplicate cleanup after the user enables it.
Optional tracking-parameter matching is off by default. When enabled, it ignores parameter names case-insensitively: utm_*, gclid, dclid, gbraid, wbraid, fbclid, msclkid, mc_cid, mc_eid, _ga, _gl, yclid, ttclid, twclid, li_fat_id, and igshid. It never ignores ref, source, si, tag, token, session, or redirect. The same rule is used for manual and scheduled duplicate cleanup, and every remaining parameter stays in its original order.
No developer collection or sharing
TabPare has no developer-operated data server, advertising SDK, or analytics SDK. The extension does not sell or send tab titles, hostnames, URLs, organization plans, browsing activity, or settings to the developer or to any developer-selected external service. When the user enables Chrome Sync, Chrome may sync only the preference settings described above through that user's Chrome profile. TabPare does not use information for advertising, creditworthiness, lending, or any purpose unrelated to tab organization and cleanup.
Your controls and retention
- Automatic organization and automatic duplicate cleanup are both off by default and can be disabled at any time in TabPare settings.
- TabPare cannot be enabled in Incognito windows.
- Manual Smart organize runs only after the user selects it. Automatic organization is off by default and runs only after the user enables it. Chrome requests optional tab-group permission before either feature can create groups; declining it leaves cleanup features available.
- Close is the default inactive action. The user can instead choose Sleep, which asks Chrome to discard the loaded page while keeping the tab. Chrome reloads the page when the user returns.
- Settings remain in Chrome extension storage until changed, cleared through Chrome, or removed with the extension, subject to Chrome Sync behavior.
- Exact protected hostnames remain in local extension storage until the user removes them, clears extension data, or uninstalls TabPare.
- The local aggregate cleanup record is replaced after a later cleanup and can be removed by clearing the extension's stored data or uninstalling TabPare.
- Sleep does not create an Undo snapshot. The in-memory Undo snapshot is cleared when another cleanup starts, including a Sleep cleanup, when Chrome restarts, or when the extension is reloaded, updated, disabled, or removed.
- The organization snapshot is stored only for the browser session and is cleared when Chrome restarts or when the extension is reloaded, updated, disabled, or removed.
Chrome permissions
tabs(optional)- Requested only after the user selects Enable tab cleanup. Reads the title, hostname or URL, state, grouping, and placement of currently open tabs so TabPare can classify eligible tabs, find cleanup candidates, close or discard selected tabs, and restore reversible actions.
storage- Saves cleanup settings, exact protected hostnames, the most recent aggregate cleanup result, and the temporary in-memory Undo snapshot.
alarms- Schedules local tab organization, duplicate cleanup, or both at the interval explicitly enabled and selected by the user.
tabGroups(optional)- Creates, titles, colors, and undoes tab groups after the user selects Smart organize or enables Automatic organize. Chrome asks for this optional permission before use, and the user may deny it without losing cleanup features.
TabPare does not request access to all website content, bookmarks, Chrome browsing history, downloads, or the user's identity.
Limited Use
TabPare's use of information received from Chrome APIs complies with the Chrome Web Store User Data Policy, including its Limited Use requirements.
Changes and contact
If TabPare's data practices change, this policy and the Chrome Web Store disclosures will be updated before the change is released. Questions can be submitted through the Support hub on TabPare's Chrome Web Store listing.