Last updated: September 7, 2026
Tabfolio helps you organize browser tabs. It has no accounts, analytics, telemetry, or Tabfolio-operated data servers. Your Spaces, preferences, and recovery records are stored locally. Thumbnail and favicon features make network requests to the sites and image providers described below.
Tabfolio reads the URLs, titles, favicon URLs, window/tab positions, active and pinned state, and available last-accessed timestamps of open tabs through Chrome’s tabs API. It uses these to display, search, group, inspect duplicates, and manage your tabs. It does not query Chrome’s browsing-history database.
Tabfolio also handles URLs and titles you save or import into Spaces, plus website metadata and images used to display thumbnails and favicons. URLs and titles can contain sensitive information; only save or import data you want Tabfolio to handle. In Chrome Web Store terminology, these features handle Web history and Website content, including when processed locally.
Tabfolio does not read page form fields, passwords, or the browser’s cookie store. It does not inject content scripts into your pages. Its thumbnail worker fetches HTML to locate preview-image metadata, as described below.
Tabfolio uses chrome.storage.local on your computer:
Spaces and preferences remain until you change or delete them. Chrome removes extension storage when you uninstall Tabfolio. Locally stored records are not uploaded to Tabfolio servers. Some URLs, domains, and video IDs are used for outbound display requests below; this is not a claim that no data leaves your computer.
Inspection searches stay in the manager session and are not sent to a search service. If you choose Copy diagnostic details, Tabfolio copies its version, build identifier/time, extension ID, and browser user-agent to your clipboard. Those details exclude tab URLs, titles, Space names, and installation paths. Diagnostics are never sent automatically.
Tabfolio does not add an account or installation identifier to these requests. Receiving servers still see normal network information such as your IP address, request URL, and browser headers. A URL may include query parameters. Providers’ privacy policies govern their handling of those requests.
For public HTTP/HTTPS URLs shown in tab or Space cards, the background worker can fetch HTML and look for an Open Graph, Twitter image, structured-data image, or touch-icon URL. It reads a bounded prefix of the response, stopping at the end of the HTML head when present. It does not retain the HTML.
The worker uses credentials: 'omit', so that metadata fetch does not send
cookies. It follows redirects. Requests go directly to the page’s server and
redirect destinations, not a Tabfolio proxy. The resolver skips common
local/private address patterns before the initial request.
The manager then loads the resulting image from its host, which may be a separate CDN. It can also load the favicon URL provided by Chrome. Image requests use the browser’s normal network and cookie rules; the image elements use a no-referrer policy. Tabfolio does not read the browser’s cookies.
If a tab’s favicon is unavailable, Tabfolio can request a favicon for its host:
www.google.com, using the tab’s host to request its favicon.icons.duckduckgo.com, using the tab’s host.The provider receives the host and normal network information, not your full Space collection or recovery history.
For YouTube and Vimeo URLs, Tabfolio extracts the video ID and loads a thumbnail:
i.ytimg.com, using the video ID.vumbnail.com, using the video ID.These requests reveal the video ID to the image provider, along with normal network information. Tabfolio does not send your whole tab list.
Fonts and executable code are bundled with the extension. No font CDN or remote executable code is used at runtime.
The extension declares:
tabs: read tab metadata and focus, move, and close tabs for the manager’s
user-facing features.storage: persist Spaces, preferences, thumbnail cache, and recovery data
locally.host_permissions: http://*/* and https://*/*: allow the background worker
to fetch thumbnail metadata for HTTP/HTTPS URLs represented by your cards.Tabfolio also uses Chrome’s windows API to create and focus windows. There is
no separate windows permission declared in the package.
Tabfolio’s use of data complies with the Chrome Web Store User Data Policy, including its Limited Use requirements. Data is used only for the disclosed user-facing tab-management and display features. Transfers to page and image providers are limited to those features. Tabfolio does not sell data, use it for advertising or credit decisions, or send browsing records to its developers for human review. No analytics or telemetry service is included.
Use Settings to export or import Space backups, restore pre-import data, or clear the thumbnail cache. Use Recovery history to forget copies or clear that history. Delete a Space to remove its saved entries, or uninstall Tabfolio to remove its extension storage. Exported files you save outside the extension must be deleted separately.
Undo and recovery reopen URLs. They do not restore form contents, passwords, scroll positions, or deleted Space structure.
Tabfolio is a general-purpose productivity tool. It does not ask users for their age or operate an account-registration system.
We update this policy when data practices or disclosures change. Previous versions are retained in the project’s version history.
For privacy questions, support, or feedback, email hello@round6.co.