Last updated: September 22, 2026
Cairn is a Chrome browser extension that helps you organize open tabs into named workspaces, search across your browsing, and clean up tab clutter. This policy explains what data the extension touches, where it lives, and what — if anything — ever leaves your device.
Cairn stores everything locally in your browser. There is no account, no server, no backend, and no telemetry of any kind. The only thing Cairn ever sends off your device is an AI request you explicitly and manually trigger, using your own API key, to an AI provider you choose — and it shows you exactly what would be sent before it sends anything.
| Data | Why Cairn accesses it | Where it goes |
|---|---|---|
| Open tabs and tab groups | To save your current browser as a workspace, and to restore, close, pin, or group tabs on your command | Stored locally only (chrome.storage.local) |
| Browsing history | Searched locally to power universal search and to detect "old" (stale) tabs | Never leaves your device; not stored by Cairn, only queried live |
| Bookmarks | Searched locally to power universal search | Never leaves your device; not stored by Cairn, only queried live |
| Recently closed tabs/sessions | Powers the "Recently closed" recovery list | Never leaves your device |
| A rolling snapshot of your open tabs | So that if the browser restarts and your tabs don’t come back — after a crash, or because Chrome isn’t set to reopen them — Cairn can offer those tabs back, including ones you never saved as a workspace. Keeps the last few snapshots, discards them after a week, and never records incognito tabs. Can be turned off in Settings. | Stored locally only (chrome.storage.local) |
| Workspace names, tabs, notes, tags you create | The core feature — saved workspaces | Stored locally only, on your device |
| Automatic backup files (optional, off by default) | If you turn on automatic backups, Cairn saves a copy of your workspaces and notes as a file on a schedule. Chrome asks your permission to save files the first time you turn it on. Cairn keeps the last 10 files it wrote and only ever removes its own. | A “Cairn Backups” folder in your own Downloads folder. Never uploaded; AI keys are never included |
| Reminders you set | When you ask to be reminded about a workspace, Cairn stores the time and, if you allowed notifications when setting your first reminder, shows a desktop notification when it comes round. | Stored locally only; the notification is shown by your own computer |
| Shared workspace files | “Share” saves one workspace as a file, only when you press it. What you do with that file is up to you. | Your Downloads folder. Cairn sends it nowhere |
| Extension settings | Your preferences (theme, font, search sources, thresholds, etc.) | Stored locally only, on your device |
Cairn does not run any content script on any webpage, does not track
your activity, does not use analytics or crash-reporting SDKs, and
does not communicate with any Cairn-operated server — because there is
no Cairn-operated server. Everything above lives in
chrome.storage.local, which is private to your browser
profile and is deleted if you uninstall the extension or clear its
site data.
Cairn can optionally use an AI provider (Anthropic, OpenAI, or a self-hosted/custom OpenAI-compatible endpoint) to summarize or answer questions about a workspace. This feature is:
Chrome will separately ask your permission (a native browser prompt) the first time you configure a specific AI provider, scoped only to that provider's domain — requested at that moment, never at install.
The Chrome Web Store's Limited Use requirements ask every extension to state four things plainly. Here they are.
Chrome's policies are explicit that disclosure must not live only in a document like this one. Cairn asks in the product, at the moment it matters:
Nothing on this page is a first disclosure. It is the complete version of things the extension already tells you as you go.
All Cairn data lives in chrome.storage.local under your Chrome profile. You can delete it at any time via:
If Cairn's data practices change, this document will be updated and the "Last updated" date above will reflect the change.