Recordist security brief

Desktop app for Mac, Windows and Linux (Windows and Linux are a preview). It records calls from the computer's own microphone and sound output, transcribes them and writes notes on that computer. Meeting audio, transcripts and notes never reach our systems, so we hold no meetings of yours to lose.

Version 1 · 18 October 2026 · Recordist 1.0.0
recordist.app/trust/brief

The full questionnaire

Where meeting data lives

Audio, transcripts, notes and the search index stay in one data folder on each computer. Nothing joins the call.
Recordist never uploads audio. With the built-in engine, no request takes meeting content off the computer.
Files are protected by the operating-system account and by full-disk encryption where it is on; the app does not encrypt them itself.

What leaves the computer

Update checks and downloads from media.recordist.app; the public list of withdrawn licence keys from license.recordist.app. No telemetry, analytics or crash reporting.
Meeting content goes elsewhere only where the person sends it: a cloud AI provider with their own key, their own Ollama, an assistant they connect, or an export.
The Privacy Ledger in Settings lists the app's requests with host, purpose and bytes; each one that can carry meeting content is written before it is sent.

AI

Speech recognition (whisper.cpp) and notes (a built-in engine) run on the computer.
Decisions, action items and quotes are checked against the transcript line they cite; unsupported items are removed. Notes can still be wrong.
No model is trained on customer meetings: we never receive them.

Consent and access

By default it asks before it records. A call is recorded only once the person confirms or starts it, unless they turn on one of two settings, both off by default.
No accounts. The local API listens on 127.0.0.1 only, needs a token per connected program, and each program can be revoked.
Cloud AI keys live in the operating system's keychain, never in files or logs.

Retention and deletion

At setup the person chooses how long audio is kept, until they delete it or 30 days (7, 90 days or right after transcription in Settings). Whole meetings can be deleted by age.
Legal hold for one meeting, or for every meeting on a managed Mac.
Delete all my data removes every meeting in one step; Remove everything and quit also removes models, settings, the licence and keys.

Central management

On a Mac, a configuration profile from your MDM enforces fifteen keys, including ForceLocalModel, DisableCloudAIKeys, MaxRetentionDays, LegalHold, DisableUpdateCheck, and from 1.0 DisablePromiseLedger, DisableInstantReplay and DisableConsentPassport.
No admin console and no reporting back: compliance is checked on each Mac. Windows and Linux have no managed settings yet.

Build and update integrity

Mac builds are signed with our Apple Developer ID (Team ID JNC57WQK69), notarised by Apple, and check their own signature at launch. The Windows installer is not code-signed yet.
Updates install only when the person chooses, and only if their signature matches the key built into the app. Speech models and the notes engine are checked against a pinned SHA-256.
Dependencies are pinned, and audited weekly and on every pull request that changes a lockfile. A CycloneDX SBOM is available on request.

What we hold

Only what a person gives the website or a purchase (an email and order details for a licence key, site form entries, support tickets), a few counts and standard request logs. Payments are taken by Stripe; we never see card numbers.
Processors: Stripe, Cloudflare, Resend, Slack (masked addresses only) and Anthropic for the website's support assistant.

Assurance, said plainly

No SOC 2 report, no ISO 27001 certificate and no independent penetration test yet. No cyber or professional liability insurance yet.
A published disclosure policy with safe harbour: acknowledgement within 3 business days, the aim of a fix for confirmed high-severity issues within 14 days.
No HIPAA business associate agreements.