The receipt
What a meeting's receipt in Conclave for Mac shows, and what it does not prove.
What it shows
Conclave's server runs in a confidential VM on Phala, and sends audio and transcripts to NEAR AI for transcription and notes. Transcription runs on NEAR AI's private inference inside a TEE. Our trust page shows the server's live hardware attestation, and NEAR AI's attestation for the transcription and notes models as our server checked it. Each meeting's receipt shows whether its transcript is signed by the server's enclave key, and whether you confirmed the recording notice.
From Conclave 0.1.2 the receipt also names the models that worked on the meeting:
Transcribed by <model> on NEAR AI.
Notes written by <model>.
Each line goes on with what our server recorded about NEAR AI's attestation when it ran: what it checked and when, or that it couldn't check, or that nothing was recorded. A meeting from before the server recorded models says "This meeting's transcription model was not recorded."
What this does not prove:
- that the running code is the code we publish;
- that NEAR AI served your request inside the enclave it attested;
- anything about your Mac before the audio leaves it;
- that
api.conclavehq.orgalways points at the enclave: Conclave controls its DNS, and a change shows in public certificate logs; - that NEAR AI's individual answers were signed.
NEAR AI says it signs each transcription inside its enclave but does not yet expose that signature, so no per-request proof is shown.
The recording notice
Before you record, Conclave for Mac reminds you to tell the others, and your confirmation is kept with the meeting. It is signed into the meeting's receipt.
Where to find it
Every finished meeting gets a receipt, with its transcript signed by the server's enclave key. A failed meeting has no transcript and no receipt.
Conclave shows the receipt as a badge in the meeting's toolbar: in the meeting you just finished and, from Conclave 0.1.4, in any meeting you open from the list. Click it for the details. Verify at /trust opens the trust page.
The meeting's page on app.conclavehq.org shows the same badge and rows for a Mac recording, to its owner only. The browser checks less than the app: "Seal key checked against the published key. Signature and quote chain not checked by the browser — verify at /trust"
The badge
From Conclave 0.1.3 the app checks the sealed version's signature on this Mac, against the key the server publishes, and the badge says what it checked. The line under the badge says more.
| Badge | The line under it |
|---|---|
| "Sealed" | "Signature and enclave key checked on this Mac. Quote chain not checked by the app — verify at /trust" |
| "Retired key" | "Signed by retired key <id>; signature checked on this Mac. Today's enclave quote does not cover that key — verify at /trust." |
| "Could not verify" | The first reason it found, for example "Seal: v<n>'s signature does not match its contents." or "Seal: the server's published seal key differs from the key its enclave quote carries." |
| "Pending" | "Checking…" while the receipt loads, otherwise "Shown once the meeting is ready." |
The app checks the signature on this Mac. It doesn't check the enclave's quote chain or its measurements: the trust page does.
Audio kept on the server
From Conclave 0.1.3 the receipt has a row "Audio kept on the server": "Yes", "Yes, until <time> UTC" or "No". It says "Yes" when "Keep my meeting audio" was on for the meeting. When the server doesn't say, the row isn't shown.