TTomás Reyes
Huddle notes: what we keep, what we throw away
When a huddle ends, Hum posts the decisions. It does not keep the recording unless you ask. The privacy choices behind huddle notes, written by the engineer who made them.
Huddles are quick calls you start from any channel. Since October, when a huddle ends, Hum posts notes in the channel: the decisions first, then follow-ups with owners. People like the notes. They also ask, reasonably, what happens to the audio. Here is exactly what we keep.
The short version
| What | Kept for | Who can see it |
|---|---|---|
| Audio while the huddle runs | Processed live, never stored | Nobody |
| Transcript | Deleted when the notes are posted | Nobody |
| Notes posted in the channel | Like any message, per your retention rules | Channel members |
| Recording (opt-in, Pro and Business) | 30 days on Pro, 1 year on Business | People who were in the huddle |
Why we throw the transcript away
A transcript is the most sensitive thing a call produces. It has every half-formed thought, every joke, every name mentioned in passing. The notes need maybe 2% of it. So the transcript lives in memory on the huddle server while the notes are written, and is deleted the moment they post. It never touches a disk.
How the notes are written
- Speech is transcribed live, per speaker, on our own servers in your data region.
- When the huddle ends, a model reads the transcript and lists decisions and follow-ups. It is told to leave out anything else.
- The notes post as a message from the person who started the huddle, editable by every participant for 24 hours.
- The transcript is deleted. The notes are now a normal message.
Recordings are opt-in, and visible
On Pro and Business, the person who starts a huddle can record it. A red dot shows for everyone for the whole call, and joining a recorded huddle asks you first. Recordings are available only to people who were in the huddle, not to the whole channel and not to admins, unless your workspace has a legal hold.
“Our test for every privacy decision: would the people in the call be surprised by what we kept? If yes, we don't keep it.”
Questions about this, or about anything else we store? Our security page has the full list, and Elise reads every message sent to security@hum.example.
Worth your 6 minutes?
Tomás Reyes · Co-founder, CTO, Mexico City
Wrote the first message Hum ever delivered. Writes about how Hum Labs works for the blog.
Meet the team