We built the tool we wanted to exist.
Flowers started with a practicing clinician doing paperwork at 9pm, again, and looking at the AI note-takers that promised to fix it. Every one of them wanted to upload the session first.
That trade never sat right. The most sensitive thing a person will ever say out loud, handed to a company because the alternative was another hour of typing. It felt like the wrong bargain to have to make, so we made a different one: put the AI on the clinician's own machine, where the recording never has to go anywhere at all.
That is a harder way to build software. It means shipping a real language model instead of calling an API, and it's why Flowers needs a reasonably modern Mac. We think it's worth it, because it turns a promise about data handling into something structural. We can't leak, sell, subpoena, or get breached out of session data we never receive.
No telemetry. Not now, not later.
Flowers has no analytics, no crash reporting, and no usage tracking of any kind. We genuinely do not know how you use the app.
Your PHI never reaches us
Not as a policy we could quietly revise, but as an architecture. There is no account and no server holding your clients' records. Read the security overview →
Your data outlives us
Records live in files on your Mac, and you can export everything unencrypted at any time. If this company disappeared tomorrow, nothing of yours would switch off.
No ads, no data sales, no insurers
Flowers is funded by the people who use it. There is no second business model reading over your shoulder, because there is nothing for one to read.