HumlaPrivate means it never leaves your Mac
For most apps, “private” means encrypted on the way to their servers. Humla's version is simpler: it doesn't send your meeting anywhere.
Free · Open source · macOS 13+ (Apple Silicon)
“Private” usually means your audio is encrypted in transit — then decrypted, transcribed, and stored on someone else's cloud. Humla is private a different way: the whole pipeline can run on your Mac, notes live in a local database, and there's no account to create.
Local, not just encrypted
On-device Whisper and diarization mean your audio is never uploaded in the first place — nothing to intercept, nothing to leak.
No account, no sign-up
Download and record. There's no login, no profile, and no cloud project tied to your name.
Local storage
Notes sit in a local SQLite database on your disk. No vendor retention.
What Humla sends back
A few anonymous counters about setup, at most once per install — no identifier, and nothing about what you record. It's disclosed in the setup wizard, with the switch right there.
Bring-your-own-key mode
Prefer a cloud engine for speed? Only your audio goes to the provider you chose, on your own account — never through Humla.
Open source
MIT-licensed and auditable, so “private” is something you can verify, not just trust.
See a meeting become a note.
New note, record, summary — that's the whole workflow. The cleanup afterwards is none, on a five-minute meeting or an hour-long one.
FAQ
What does “private” actually mean here?+
That your meeting can stay entirely on your Mac. In on-device mode, audio, transcript, and summary never leave the machine.
Do I need an account?+
No. The app has no sign-up. The optional team-sync layer needs an account, but the app itself doesn't.
What if I use a cloud transcription engine?+
Then only that audio goes to the provider you picked, on your own key. Humla has no server in the middle.
So what does Humla itself send?+
Only a few anonymous counters about setup: that the app was run for the first time, and whether the setup wizard was finished or skipped. Each goes once per install and carries nothing but the event name — no identifier, no account, no version, nothing about what you configured or recorded. They're stored as daily totals, so there's no record to tie back to anyone. The setup wizard says so and lets you switch it off there, or later under Settings → About. Installs from before the feature was added are never enrolled.