Almost nothing to tell you,which is the point

HuddleOwl is a desktop application that runs on your computer. It has no account system, so there is nothing for you to sign up for and nothing for us to hold. Your audio, transcripts, coaching cues, briefs and draft emails are written to a folder on your own disk. We never receive them, and there is no server of ours for them to be received by.

With the on-device models selected on macOS, the app makes no network calls at all during a meeting. Not fewer. None.

Every privacy page says something like the above. Here are three ways to test this one in under five minutes:

• Turn the wifi off and run a meeting. Live transcription, live cues, the brief and the follow-up email all still work.
• Open Little Snitch, LuLu or any network monitor and watch what the app does during a call.
• Open the data folder from inside the app and read the files. They are yours, in plain formats.

HuddleOwl can use a cloud model instead, which is the default on Windows today. In that mode your transcript is sent to the provider you selected, using the API key you entered, directly from your machine. It does not pass through us, and we do not see it. What that provider then does with it is governed by their terms, not ours.

The two engines are separate, so you can run transcription on your machine and analysis in the cloud, or the reverse, per meeting.

Open the data folder from inside the app and delete it. That is the whole procedure. There is no second copy to request the removal of, no account to close and nobody to email.

The site is a set of static files hosted by Netlify, who record standard server request logs. There are no advertising trackers, no session recording and no third-party analytics scripts. Nothing on this site follows you anywhere else.

If you fill in the teams form, the email address and the note you write are delivered to us through Netlify Forms so we can reply. We use them to reply and for nothing else: no mailing list, no sequence, no sharing with anyone.

Installers are served from GitHub Releases, which means GitHub sees the request as they would for any public file. We publish a SHA-256 for every build so you can confirm the file you received is the file that was built. The releases are here.

If this page ever needs to say something materially different, it will say it plainly rather than in an addendum. Questions, including awkward ones, go to the form on the home page and are answered by the person who wrote the app.