Team guide
What our relay sees, and what isn't proven yet
The relay passes your team's sealed notes between Macs. This page lists everything it holds and sees, and what nobody outside has checked yet.
What our relay sees
Notes pass between Macs through a relay we run on this site's domain, on servers in the EU behind Cloudflare, or, with Enterprise, one in your company's network. It holds ciphertext, a membership skeleton, one share of each Mac's recovery copy, 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. Neither share opens anything alone.
| It sees | It never sees |
|---|---|
| The team's id. Each Mac's public key, its role, and an opaque id for the person it belongs to. What kind of entry was written, its size and time. Random project and group ids, who is in each group and who leads it. Which Macs can read an attendees-only note. Invite expiry times. Which Mac a recovery went from and to. When the team's owner reads at the team's end. | Names, emails, project names, rules, notes, transcripts and remarks. And no key that opens them: every such key is made on a member's Mac and wrapped only to members' Macs, and the relay's share of a recovery copy opens nothing without an admin's, nor its share of the end key without the team's recovery words. |
Every write is signed by a member's Mac with a key kept in its Secure Enclave, and every Mac checks every signature against the team's root, which it pinned when it joined. The relay keeps no access logs. When a team's subscription ends, the relay deletes what it holds for the team 28 days after the last day it was paid for, and a free month's team that wasn't bought 14 days after the free month ends; when the team's owner deletes the team, its notes go at once (When a team ends). The relay's share of the end key goes with the team's notes, at once when the owner turns the rule off, and when a team that comes back after its owner read it spends the key. Our license service, which handles the seats, never learns the team's name, its members or who a seat is for. 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. Security describes the services.
Like our license service, the relay refuses every request from the countries and regions under US embargo or sanctions, by the country Cloudflare gives for the request. It refuses France too: French law asks for a declaration to ANSSI, the French cybersecurity agency, before encryption software is supplied there, and Patum isn't offered in France until a month after its declaration. A member who travels to one of these places can't sync from there until they leave, and their Mac keeps working on its own copy. A refusal leaves only a count per day and place: no address, team or Mac.
For your security review
The questions a security or privacy review usually asks, answered in short, with the page that has each in full. For a few questions of your own, write to patum@nikioth.org; a full questionnaire in your company's format, and our security package, come with Enterprise.
| Question | Answer |
|---|---|
| What stays on each Mac, and what is shared | Every meeting is recorded, transcribed and summarized on the Mac that heard it, and work is stored apart from personal meetings. Only the notes their authors publish reach colleagues, and audio never does: Work and personal, What gets shared. |
| What our relay holds and sees | Sealed notes, a membership skeleton and two kinds of key share, which open nothing alone: What our relay sees, above. |
| Where our services run | On servers in the EU, behind Cloudflare: the relay and the license service. With Enterprise, the relay can run in your company's network: Enterprise. |
| What our license service keeps | The seats, a free month's work email until its team is bought or deleted, and the country checks export rules require: Privacy. |
| Which keys are split | Each Mac's recovery copy, between an admin and the relay; the key for the owner's reading at the team's end, between the team's recovery words and the relay: When a Mac is lost, What the owner reads at the end. |
| How long the relay keeps a team | 14 days after a free month that wasn't bought, 28 days after the last day a paid team was paid for, and its notes at once when the owner deletes the team: When a team ends. |
| How much the relay holds | Up to 2 GB a team, whatever its size, and 512 MB in a free month, for published notes and their images: How much the relay holds. |
| When our relay is down | Each Mac keeps recording, transcribing, writing notes and reading what it already has, and what it publishes waits in the Outbox. After 30 days without the relay, its team projects turn read-only, and nothing is deleted on a timer. We don't promise uptime for Team: What isn't proven yet, below. |
| Who helps, and how fast | By email or Help › Report a Problem…, in English, within 2 business days for a team, and one business day with Enterprise: Getting help. |
| A data processing agreement | With Free and Pro, Patum sends us nothing to process. For Team, our relay holds the notes members publish, encrypted with keys made on the team's Macs. A company that needs a data processing agreement writes to us. |
| Every connection the app makes | With what each one sends: Privacy. |
| Managed Macs, directory sync, logs | A managed profile works in any plan: Macs your company manages. Patum has no SCIM sync from Entra ID or Okta and doesn't send the activity log to a SIEM: Enterprise. |
| An outside audit | None has been done: What isn't proven yet, below. |
What isn't proven yet
We would rather you read this before you start a free month than after.
- No outside audit has been done. Read the claims on this page as our design and our own testing, not a third party's finding.
- A relay can withhold notes or show different people different histories. It can't read or forge anything. Macs compare each other's signed checkpoints and stop publishing when they disagree, or when no admin has checked in for seven days. A relay can also refuse service, which people notice.
- The relay sees metadata: when people publish, how much, in which random project, which Macs belong to one person, every recovery, and when the owner reads at the team's end.
- Patum enforces the rules on each Mac. They don't stop a screenshot, a photo of a screen, or a modified copy of the app. A note someone already copied elsewhere can't be called back.
- A removal reaches a Mac when it connects. A Mac that is offline keeps its encrypted work until its next sync. After 30 days without one, its team projects turn read-only. Nothing is deleted on a timer.
- A recording in progress is written unencrypted in Movies › Patum, so a crash can be recovered, and is sealed once it is complete.
- A recovery copy opens only with an admin's share and the relay's together. If the same people run your admins' Macs and the relay, they can open a Mac's work with its backup; the copy then stops only someone who has the backup alone. Two people together, the admin who added a Mac for someone and the person who confirmed it, could open that person's work with their backup. Every step shows in the activity log and on the person's other Macs.
- While the rule for the team's end is on, the team's recovery words and the relay's share of the end key together open every note shared in the team, at any time, not only after the end. The relay hands its share only to the owner's Macs once the team has ended, but that is our relay's own rule. The split protects the notes only while the words and the relay are in different hands: on our relay, the company's safe and Patum; on a company's own relay, they may be the same people. The words, which can already name admins, are worth more for it, and malware on the owner's Mac when they are typed would see them. A team that doesn't want this can turn the rule off (What the owner reads at the end).
- Still to come: a person's other Mac approving a recovery instead of an admin, publishing a team project's regular summaries from the Outbox, and managed-profile locks beyond Require Touch ID to open Patum, Let people know, cloud providers, voice recognition and how long audio is kept.