Privacy

The one thing Bloom sends

About once a day, Bloom posts six values to runbloom.app. That is the whole list, and nothing else in the app talks to us:

• An install token. A random string Bloom made up the first time it ran and keeps on your Mac. It is not derived from your hardware, your account or anything else about you, and it means nothing to anyone who does not have your Mac. It is there so two pings from one Mac count as one install rather than two.
• The version of Bloom you are running.
• The version of macOS you are running.
• Which coding agent you have Bloom set to, such as Claude Code or Codex.
• Which theme you have Bloom set to.
• A country code. Two letters, worked out from the connection while the request is being handled.

What we do not keep

We do not store your IP address. It is used to work out the country code and to stop the endpoint being flooded, and then it is gone: nothing writes it to a database or a log of ours. We do not know your name or your email, because there is no account. We never see your repositories, your branches, your prompts, your code, your file paths or anything you typed into an agent. None of that is in the ping, and there is nothing else for it to be in.

How long we keep it

The individual pings are deleted after 90 days. That is long enough to watch a release reach people and short enough that we are not sitting on a pile of history. A single row per install holds the latest of the values above, and it is deleted once an install has not been heard from for a year.

Why we do it

Bloom is free and has no signups, so this is the only way to know whether anyone is using it, whether a release landed, and which macOS versions we still have to support. We do it under legitimate interest, and we keep the least we can get away with.

What Bloom stores, and where

Bloom keeps its own data in a SQLite database in your Library's Application Support folder, on your Mac. That is where your workspaces and their settings live.

The work itself lives where you would expect: a git worktree is an ordinary directory on your disk, on an ordinary branch. None of it passes through us.

Other programs Bloom runs

Bloom is a window around tools you already have. It starts them as child processes on your own machine, with your own credentials, and it does not sit between them and the services they talk to.

• Coding agents. Claude Code and Codex, whichever of them you have installed. They send your code and your prompts to their own providers under their own privacy terms, exactly as they do when you run them in a terminal. Read the terms of the agent you use.
• git. For worktrees, branches and everything else Bloom does to a repository.
• gh. The GitHub CLI, for pull requests and check runs, signed in with the GitHub account you already set it up with.
• Ghostty's configuration. If you have one, Bloom reads it to match your terminal theme, font and colours. It reads that file and nothing else from it leaves your machine.

Updates

Bloom checks for new versions with Sparkle, which fetches an update feed from us. That request carries the usual things any HTTP request carries, and we do not keep a record of it.

Deleting your data

There is no account to close. Delete Bloom's folder in Application Support and its data, including the install token, is gone from your Mac. If you also want the row on our side removed before it expires, send us the token and we will delete it. Your repositories and worktrees are yours and stay where they are until you delete them too.

Changes to this policy

If Bloom ever starts doing something this page does not describe, this page changes first, and the date at the top changes with it.

Contact

Questions about any of this go to [email protected]. Bloom is made by Spatie, a web development company in Antwerp, Belgium.