Privacy
Privacy Policy
Last updated 14 September 2026 · Applies to SwitchCue for Chrome v0.1.0 and to switchcue.app
This policy is in three parts, because there are three different situations and they have different answers: the extension you install, this website, and writing to support.
Part 1 — The SwitchCue extension
What it does
SwitchCue saves the set of tabs you are using for one project, together with one short note about what to do next, and switches between those saved sets in a single Chrome window. Everything it records is in service of reopening them later.
What it stores, and when
Only for tabs you put in a Workspace — by ticking them when you create one, by adding the tab you are on, or through the setting that adds tabs automatically while a Workspace is open. Tabs you never put in a Workspace are not recorded.
| What | When | Why it is needed |
|---|---|---|
| The address (URL) and title of each tab you put in a Workspace | When you create a Workspace, add a tab to one, or save one on the way out | This is the saved Workspace. Without the address there is nothing to reopen |
| Whether a tab was pinned, and the title, colour and collapsed state of its tab group | At the same moment | So the window comes back arranged the way you left it |
| The name and colour you give a Workspace, and the Next Action you write | When you type them | The two things the product exists to hand back |
| Which of that Workspace's tabs you were last looking at | At the same moment | Shows "Left off at …" and puts you back on that tab |
| Next Actions you have replaced, up to 100 per Workspace | When you change a Next Action, unless you have switched this off | So you can look back at one, or put it back |
| Your settings, including the light or dark preference | When you change them | The theme is also copied into the browser's local storage for this extension, so the panel can paint in the right colours before it has finished loading |
| A note that you closed a tab by hand — keys only, no address or title | While a Workspace is open, and only until you switch or restart | So the panel can offer to put that tab back |
What it does not do
- It does not continuously track your browsing history. It does not keep a running log of the pages you visit, and tabs you never put in a Workspace are not written down. What it does store is the URL and title of each tab you choose to include in a Workspace, recorded at the moments listed above — when you put that tab in, and when a Workspace you are leaving is saved.
- It cannot read the content of a page. The extension requests no host permissions and has no content scripts, which is what would be required to see inside a page. It cannot read what a page says, what you type into it, your passwords, your form entries or your cookies.
- It has no account and no sign-in, so there is no profile of you to build.
- It does not sell or share data with anyone, because there is no one to share it with and nothing is transmitted.
Requests to the network
The extension code we write contains no networking at all: no server calls, no analytics endpoint, no remotely loaded code. Searching the source we author finds nofetch, XMLHttpRequest, WebSocket,EventSource or sendBeacon anywhere in it. There is no SwitchCue server for your Workspace data to be sent to.
Two things are worth stating precisely rather than glossing over, because anyone can unpack a Chrome extension and read it.
The first is site icons. Where the panel lists tabs that are open right now — when you are choosing tabs for a new Workspace, managing a Workspace's tabs, or reviewing tabs before you switch — it shows each site's small icon by pointing at the icon address the browser already has for that tab. Your browser usually answers that from its own cache; where it does not, the request goes to that site, which your browser had already contacted to show you the page. Nothing about it reaches us, nothing is stored, and lists of saved tabs never load icons at all.
The second is one line in the finished package that SwitchCue did not write. The package also holds the libraries SwitchCue is built with, and the tool that assembles it adds a little code of its own. One line of that is a fetch call — a standard warm-up step for loading files that are already inside the extension slightly earlier than the browser otherwise would. It cannot run here: its first instruction checks whether the browser already does this job itself, and every version of Chrome that can install SwitchCue does, so it stops there. Even if it did not, it only looks for a kind of link tag the panel does not contain, and the only addresses it could use are files inside the extension. It is not remotely loaded code, it has no access to your Workspaces, and nothing about you can travel with it. We leave it in place because what is published to the Chrome Web Store is the exact package that was tested; rebuilding it to change what a text search finds, rather than what the software does, would make it less verified, not more.
The local usage journal
To judge whether the beta works, SwitchCue keeps a journal of what it did — counts and size bands for actions such as "a Workspace was created", "a switch completed", "a restore failed", with how long the action took and whether it succeeded.
- It never records a Workspace name, a page title, an address, or the text of a Next Action. Only a fixed list of event names and a fixed list of numeric or true/false properties is allowed; anything else is discarded rather than written.
- It is bounded: at most 500 entries, and nothing older than 30 days. Older entries are deleted automatically.
- It is stored on this computer like everything else, and it is not transmitted. It reaches us only inside the diagnostics file described below, if you choose to send one.
- You can switch it off in Settings, under Diagnostics. Switching it off stops new entries from being recorded. It does not erase entries already stored — declining to be recorded from now on is not the same as asking for existing records to be destroyed, and a checkbox should not make an irreversible choice on your behalf.
- The extension also generates a random identifier for this installation, so that if you do send a diagnostics file we can tell one installation's numbers from another's. It is not linked to you and is used for nothing else.
Where it is stored, and who can see it
In your browser's own local database (IndexedDB) for this extension, on the computer you are using. It is not synced between your devices and it does not leave for anywhere else. We cannot see it — we have no server to see it from.
Files you create yourself
Settings has two export buttons. Both write a file to your own computer and nothing else:
- Export contains your Workspaces, their saved tabs and addresses, your Next Actions including replaced ones, and two of your settings. It is the only copy that survives uninstalling the extension. What happens to that file afterwards is up to you.
- Export beta diagnostics contains the usage journal only — event names, counts and bands — checked a second time on the way out so that no name, title or address can be in it. Sending it to us is your decision; nothing is sent unless you send it.
Keeping and deleting
- Delete a Workspace in Settings to remove it and the tabs it had saved.
- Clear a Workspace's replaced Next Actions from its own history screen.
- Switch off the usage journal in Settings → Diagnostics to stop new entries.
- Uninstalling SwitchCue deletes everything it stored, permanently and immediately. Export first if you want to keep it.
What we tell the Chrome Web Store
The listing, the Chrome Web Store privacy declarations and this page are written to say the same thing. The single purpose we declare is, word for word:
SwitchCue saves the set of tabs a user is using for one client or project, together with one short note about what to do next, and switches between those saved sets in a single Chrome window.
The extension requests three permissions and no host permissions:
| Permission | Why it is required | What it does not grant |
|---|---|---|
sidePanel | The whole interface is a Chrome side panel. This permission declares it, and lets the toolbar icon and the keyboard shortcut open it. | No access to tabs or page content. |
tabs | Chrome returns a tab's address and title as empty values without it, and a saved Workspace needs both. It also covers the actions you ask for: opening a Workspace's tabs, closing the ones you are leaving, and focusing the tab you left off on. | Metadata only. With no host permissions and no content scripts, the content of a page is out of reach. |
tabGroups | Reads a group's title, colour and collapsed state so the group can be rebuilt when the Workspace reopens. | Group metadata only. It grants no additional access to tabs, and none to page content. |
We also declare, and it is true of the shipped build: SwitchCue uses no remote code— all of its JavaScript is inside the package; we do not sell or transfer your data to third parties; we do not use or transfer it for anything unrelated to the purpose above; and we do not use or transfer it to judge creditworthiness or for lending.
Part 2 — This website
switchcue.app is a set of static pages. It has no accounts, no sign-in, no cookies, no analytics, no tracking pixels and no third-party scripts or fonts — every file a page asks for comes from this site's own address.
Serving a page still requires a server, and a server necessarily sees the request. This site is hosted on Cloudflare Pages, which processes what any web host processes in order to deliver a page and to defend itself against abuse: the address you requested, your IP address, the identification your browser sends, and the time. That processing is the host's, under the host's own privacy terms. We do not add anything to it, we do not use it to build a profile, and we do not combine it with anything from the extension — which has no way to reach this site in any case.
Part 3 — If you write to support
If you email support@switchcue.app, we receive your email address, whatever you write, and anything you attach — which may include a screenshot or a beta diagnostics file, if you chose to send one.
We use it to answer you and to fix what you reported, and for nothing else. It is kept as ordinary email for as long as it is useful for that, and you can ask us to delete your correspondence at any time by replying and saying so.
Who we are, and how to reach us
SwitchCue is made and published by an independent developer based in Vietnam, working under the name SwitchCue — the developer name shown on the SwitchCue listing in the Chrome Web Store. For anything about this policy, about your data, or about the extension, email support@switchcue.app.
Children
SwitchCue is a tool for work and is not directed at children. We do not knowingly collect anything from them, and in practice there is nothing to collect: the extension keeps its data on the user's own computer and sends none of it to us.
Changes to this policy
If this policy changes, the new version is published on this page with a new date at the top. If a change to how the extension handles your data is ever made, it will be described in the extension itself before it takes effect, rather than only here.