Privacy policy

What it reads

When you open a Flow in Flow Builder, the extension reads your Salesforce session cookie for that org, locally, and uses it to ask your org’s Tooling API for the flow’s last saved metadata. The cookie is sent only to your own org’s *.my.salesforce.com host. It is never stored, logged, or sent anywhere else.

What it sends, and to whom

When you ask a question or use one of the actions, the flow’s saved metadata, your conversation, and any instructions you wrote in Settings go from your browser directly to the AI provider you chose, Anthropic, OpenAI, or Google, under your own API key. The metadata is the flow’s definition: element names, formulas, labels, and any text whoever built the flow typed into it. No Salesforce records are read or sent.

With an Anthropic or Google key, the flow’s saved metadata is also sent to that provider when a flow opens in the panel or you change the model, before you ask anything, to check that the flow fits the model you picked. With an OpenAI key, that check happens on your computer.

Your API key goes on its own to the provider that issued it: when you add it, and at most once a day after that, when the panel opens, to get the list of models it can use.

The provider’s privacy policy applies to that data: Anthropic, OpenAI, Google. On Google’s free tier, prompts may be used to improve Google’s models; use a paid project if that matters for your org.

Open in Excalidraw, under a drawn diagram, puts the diagram on your clipboard and opens excalidraw.com in a new tab. Nothing goes to excalidraw.com until you paste it there yourself, and the extension never talks to that site.

What it stores, on your computer only

Your API key (in Chrome’s extension storage; when “Remember this key on this computer” is off, it is forgotten when Chrome closes), your settings, and your chat history per flow. Nothing is synced or backed up by us. “Forget everything on this computer” in Settings removes all of it, including any answer still arriving.

What it never does

No telemetry, analytics, crash reports, advertising identifiers, or accounts. There is no sign-up, so we never learn your name or your email unless you write to us. The extension makes no network request except the ones in points 1 and 2. Nothing is sold, and nothing is shared with anyone other than the AI providers whose keys you add.

Permissions

cookies and the Salesforce host permissions exist to read your session and call your org’s Tooling API. sidePanel shows the panel. storage keeps the items in point 3. The three provider host permissions allow the requests in point 2, under your key. The extension does not request the tabs permission and cannot see the addresses of pages outside Salesforce.

How to check any of this yourself

You do not have to take our word for it. Chrome shows the extension’s full permission list at chrome://extensions, and you can open DevTools on the panel to watch every request it makes. The extension also ships a content security policy that Chrome enforces whatever this page says: it allows connections only to the hosts named above, and allows the panel to load nothing else from anywhere, no remote images, fonts, or frames. The source code is public on GitHub under the GPL-3.0 licence, so the code itself can be read, not only the installed copy inspected.

A policy is a promise. The manifest is a rule the browser applies.

This website, which is not the extension

Everything above is about the extension. This website is a separate thing, and it does one thing the extension does not: it counts visits, so we know whether anyone is reading. That is Vercel Web Analytics, which sets no cookies and identifies a visit by a hash of the request that is discarded and reset each day, so a visitor cannot be followed between days or across sites. It records the page, the referrer, and the country, browser and operating system. It runs on this site only. The extension has no analytics of any kind.

Changes

Material changes update the date at the top of this page and the Web Store listing.