Security

Patum's main protection is that your meetings never reach us. The services we run for the app, the license service and the relay for teams, hold as little as they can.

On your Mac

  • Recordings, transcripts and notes live in Patum's sandboxed container, in Movies › Patum and in your vault folder. Patum can ask for Touch ID when it opens, when the Mac wakes and when its main window closes; macOS does the check.
  • API keys for AI providers are kept in your Keychain. Text goes to a provider only for the jobs you choose, after a consent screen, straight from your Mac to the provider, and every request is listed in Settings › Providers under Sent recently.
  • Before text from your notes, transcripts or code reaches a model, Patum removes the markers a model uses to tell its instructions apart from the text it is given, so a line in a note can't open an instruction of its own. The model is also told that this text is data and never instructions. This makes it harder for a note to pass itself off as an instruction, though no model is fully safe from that.
  • Voice profiles are computed and kept on the Mac, and never sent anywhere. Recognize voices across meetings, in Settings › Recording, can be turned off: Patum then tells the voices apart within each meeting and keeps only your own profile, to find you in a room.
  • Models on your Mac have no way to send anything anywhere. They are downloaded at fixed versions, and every file's size and hash is checked before Patum uses it.
  • The MCP server (Pro) is off until you turn it on. AI apps reach it through a helper inside Patum, which talks to the app over a local socket that only that helper may use. Nothing listens on the network.
  • In a team, the team's work is kept apart from your own meetings, encrypted with a key that never leaves the Mac except as a split recovery copy, and closes when the Mac sleeps or locks. When the team ends, its owner can read every note shared in it, with the team's recovery words and the relay's share together, unless they turned that rule off. Patum for teams has the details.
  • Screen moments (Pro) are off until you turn them on. Patum then captures only the call's window: the one you choose in macOS's sharing picker, or the one it finds if you allowed Screen Recording. Never the whole screen or its own windows. The pictures and their text stay on the Mac.
  • Files you import are read on your Mac: by macOS, or for WebM and MKV by Patum's own reader. Nothing is uploaded.
  • The download from this site checks the signature of every update before it installs it.
Providers
Patum needs no provider: everything runs on this Mac. Add your own key only if you want a cloud model for some jobs. Keys stay in your Keychain; Patum has no server in between.
Your keys
AnthropicClaude modelsAdd key…
OpenAIGPT modelsAdd key…
Google GeminiGemini modelsAdd key…
xAIGrok modelsAdd key…
OpenRouterMany models through one keyAdd key…
OllamaA model server on this MacSet up…
Use them for
Notes and summaries ProThe meeting’s transcript is sent.On this Mac
Briefings ProIf a provider is chosen: the meeting’s event, earlier notes with these people, your notes about them and your vault’s recent notes.On this Mac
Live context ProIf a provider is chosen: the question, the passages it cites, the call’s last minutes, and the meeting’s calendar event and briefing.On this Mac
Ask ProIf a provider is chosen: the question, the cited passages and the chat so far.On this Mac
Sent recently
Nothing sent yetNotes, transcripts and audio stayed on this Mac.Show full log…

The license service

License keys are digital signatures. Without our private keys nobody can make one, and knowing the format doesn't help. A key also has to be activated on each Mac, which needs the internet once. The license service signs the activation for that key and for a key the Mac keeps in its Secure Enclave, and Patum checks that signature with our public key, which is built into the app. So an activation copied from another Mac, or one from a server pretending to be ours, does nothing. Apart from the reports you send from Help › Report a Problem…, which it keeps for 180 days, and the work email a free month of Team starts from, which it keeps for that month's emails, 44 days at most, the service stores hashes of device keys and license key ids, and no names, emails or IP addresses. Every request from the app is signed with a key kept in the Mac's Secure Enclave.

Patum for teams uses a second service, the team's relay, which holds encrypted notes, a membership list, one share of each Mac's recovery copy, which opens nothing without an admin's, and, while the team's rule for its end is on, one share of the key its owner reads every shared note with at the end, which opens nothing without the team's recovery words. The relay hands that share only to the owner's Mac, and only once the team has ended. It deletes what it holds for a team 28 days after the last day the team's subscription was paid for, and a free month's team that wasn't bought 14 days after the free month ends. The license service never learns a team's name or its members; for a team it sells or starts as a free month, it keeps the random reference that ties the team key to its team on the relay. Patum for teams lists what the relay sees and what is not proven yet.

How the services run

Our license service and the relay for teams run on servers in the EU, behind Cloudflare. The license service is one small program with two dependencies, in a minimal container with no shell, running as an unprivileged user on a read-only file system, behind TLS. Neither service keeps access logs. The license service's database is backed up continuously to storage that is encrypted at rest.

Reporting a vulnerability

Write to patum@nikioth.org with what you found and how to reproduce it. We answer within three business days, keep you posted while we fix it, and credit you if you'd like. Please don't access other people's data or disrupt the service while testing. Our security.txt has the same details.