What Toolbox stores about you, where it lives, and when anything leaves your machine. Last updated August 13, 2026.
The short version
Toolbox has no ads, no analytics scripts, and no trackers. We don’t sell or share your data with anyone for marketing.
Everything you save — projects, imported assets, preferences — is stored so you can load it again. Projects are private by default.
Your images and graphs only leave our infrastructure when you use an AI node that calls an outside provider, and the sections below spell out exactly which node sends what, where.
Your account
You sign in with Google. From your Google profile we receive and store your email address, display name, and avatar. The email is used only to identify your account — we don’t send marketing email. The display name is stored in a public profiles table so that public projects can show “by <display name>”next to the title; it’s the only piece of account data other users ever see.
You can use Toolbox without an account, but anything that saves to the cloud (projects, preferences, AI recipes) requires signing in.
Projects, assets, and ratings
Projects are private by default and stay that way until you flip them public yourself. Private projects are visible only to you; public projects are visible to everyone, including signed-out visitors. See Public vs. private for the ownership rules.
Imported assets(images, audio, and other media you bring into a graph) are uploaded to file storage so your project can reload them later. Assets follow their project’s visibility.
Thumbnails of your projects are stored so the load screen can show previews.
Ratings you leave on public projects are stored with your account — one rating per project, and you can change it any time. Other users only ever see the aggregate average and count, never who rated what.
Bring-your-own API keys
Some AI features run on your own provider accounts. If you add an OpenAI key, Anthropic key, or Hugging Face token in User Preferences, it is stored in your preferences row in the database, protected by row-level security so only your own authenticated session can read it back.
Keys are used solely to call the matching provider on your behalf when you use the feature that needs them.
For AI recipes, your Anthropic key is read on the server at request time — it never travels in a request body to or from your browser.
You can clear any stored key from User Preferences at any time.
AI features
Each AI feature is opt-in — nothing is sent anywhere until you use the node or button in question.
Image Generate node— your prompt and any reference images you wire in are sent to OpenAI using your own OpenAI key. Generated images and their prompts are saved to a private storage bucket in your account so the node’s history survives reloads.
AI recipes(generate / edit a graph from a prompt) — your prompt and the relevant graph context are sent to Anthropic’s Claude API, using your key if you’ve added one. Requires sign-in.
Background removal, depth, and segmentation run entirely on your device, in the browser. The model weights are downloaded from Hugging Face the first time you use them, but your images never leave your machine for these features.
Services Toolbox relies on
Service
What it does
What it receives
Supabase
Sign-in, database, file storage
Account info, projects, assets, preferences (including any API keys you add), ratings
Vercel
Hosts the web app
Standard server request logs, including IP addresses
OpenAI
Image Generate node
Prompts and reference images, only when you use the node, under your own key
Anthropic
AI recipe generation and editing
Your prompt and graph context, only when you use the feature
Hugging Face
Serves on-device AI model weights
Standard download requests; your optional access token if you’ve added one
GitHub
Desktop app update checks and downloads
Standard request metadata (IP, app version)
Each of these providers processes that data under its own privacy policy. We don’t send them anything beyond what the table lists.
Cookies
Toolbox sets only the session cookies needed to keep you signed in. There are no advertising, analytics, or third-party tracking cookies.
The desktop app
The desktop app is the same application in a native shell, talking to the same services, so everything above applies equally. The one addition: on launch it checks GitHub Releases for updates and downloads them from there.
Deleting your data
Delete any project you own from the load screen — its assets and thumbnail go with it.
Clear stored API keys from User Preferences at any time.
To delete your account and everything attached to it, email us (address below) and we’ll remove it.
Copies are the one caveat: if someone saved a copy of one of your publicprojects while it was public, that copy belongs to them and isn’t affected by you deleting the original.
Changes & contact
If this policy changes, we’ll update this page and the date at the top. Questions, or an account deletion request: henry@isthishenry.com.