Trust
No servers, no logs.
Nmonic listens to extremely sensitive conversations — your team's, your customers', sometimes your own first take on an idea you haven't sorted yet. That sets a high bar. This page is how we meet it.
EFFECTIVE 2026-05-27 · NEXT REVIEW 2026-08-27
Nmonic has no backend. There is no Nmonic account, no Nmonic database, no Nmonic server that ever sees your audio. The app runs on your Mac. The transcripts live in your Documents folder. If you delete it tomorrow, there is nothing for us to delete.
i. The two-column promise
The honest version, on one screen.
- Captures audio from your microphone and your Mac's system loopback (CoreAudio). Only when you press record.
- Streams to a transcription service using your API key, if you provide one. The audio bytes flow directly from your machine to that service — Nmonic isn't in the middle.
- Asks an LLM to extract decisions and commitments using your API key. Same direct connection.
- Stores the result as a JSON file in your Documents folder. That's it. That's the database.
- No Nmonic accounts. There is no signup, no login, no email collected.
- No telemetry. The app does not phone home. There is no crash analytics SDK. There is no usage analytics.
- No cloud sync. Your meetings never leave your Mac unless you choose to share the JSON file yourself.
- No data sales. We don't have your data to sell. Period.
ii. Where your audio actually goes
Nmonic is glue. When you press record, audio flows from your microphone and your Mac's loopback through Nmonic to whichever services you've configured with API keys. The keys are yours. The contracts with those services are yours. Nmonic is not a party to them.
If none of those keys are set, Nmonic runs with dummy providers and produces no transcripts. It will not silently send your audio anywhere.
iii. Where the files live
One folder. Plain JSON. One file per meeting. Searchable with anything. Diffable with git. Re-importable into anything you'll ever build.
Each file contains: the full transcript (speaker-attributed), a summary (title, narrative, key decisions, open questions), the commitments extracted (with owner + due date + source quote), and tags. Schema is stable and documented in the repo.
iv. Deleting everything
Local app, local data. Two commands. Done.
Any data sitting in your Deepgram / Anthropic / OpenAI accounts is governed by those services' retention policies — sign in there to purge or change settings.
v. If Nmonic ever vanishes
Because Nmonic is local-first, "sunset" doesn't mean what it usually means. Here's the commitment:
The Nmonic source code stays public on GitHub indefinitely. If we stop developing it, the last working version remains buildable. Your JSON files keep working forever — they're not a proprietary format, they're plain text. There is no server we can turn off that would make your past meetings unreadable.
— mick.jae.johnson · maintainer
vi. Talk to a human
Security questions, audit requests, vendor concerns, weird edge cases — same address. Usually a reply within 48 hours.
vii. The legal version
This page is the plain-English summary. The full, legally-binding privacy policy lives at /privacy and is the authoritative document if any phrasing here conflicts with it.