Privacy policy
Privacy policy
If you only read one paragraph
Nmonic is a local-first macOS application. It has no backend, no user accounts, no telemetry, and no analytics. Your audio and transcripts stay on your Mac. The only outbound network traffic Nmonic makes is to third-party services you configure with your own API keys (Deepgram for transcription, Anthropic or OpenAI for summarization). Their privacy policies, not Nmonic's, govern that traffic.
This policy describes what Nmonic does and does not do with information that flows through it. It is written by mick-jae-johnson ("we" / "us" / "I"). It is in plain English; there are no dark patterns and no hidden meanings.
1. What Nmonic collects
Nothing, on our end. Nmonic does not run any server. There is no Nmonic account, no Nmonic database, and no Nmonic analytics endpoint that receives data from the app. We — the people who maintain Nmonic — never receive your audio, transcripts, summaries, or usage information.
Nmonic does process data locally on your Mac, including:
- Audio. Captured from your microphone (CoreAudio) and your Mac's system loopback when you press record. Held in memory only long enough to stream to your configured transcription service. Not written to disk by Nmonic.
- Transcripts and summaries. Returned by the services you configured. Written to JSON files in
~/Documents/Nmonic/for your own use. - Your API keys. Read from environment variables you set yourself. Held in memory by the app process. Not transmitted to us. Not stored to disk by Nmonic.
2. What Nmonic does not collect
- No name, email, phone, or any user identifier.
- No advertising identifiers (no IDFA, no IDFV).
- No device telemetry, no crash reports, no analytics events.
- No location, contacts, calendar, photos, or filesystem snooping beyond
~/Documents/Nmonic/. - No third-party SDKs that collect data on our behalf.
3. Third-party services you can connect
Nmonic does nothing on its own. To get a transcript, you must provide an API key for at least one of the following services. When you do, the relevant data flows directly from your Mac to that service over a TLS connection. Nmonic is not a proxy. We see none of it.
Deepgram — realtime audio transcription. Receives the raw audio captured by Nmonic. Activated when DEEPGRAM_API_KEY is set. Governed by Deepgram's privacy policy.
Anthropic — Claude model, used for summarization and extraction of decisions/commitments. Receives transcript text (not audio). Activated when ANTHROPIC_API_KEY is set. Anthropic does not train its models on data submitted via the API. Governed by Anthropic's privacy policy and commercial terms.
OpenAI — GPT models, used as a fallback if no Anthropic key is configured. Same data scope as Anthropic. Activated when OPENAI_API_KEY is set. OpenAI does not train its models on data submitted via the API. Governed by OpenAI's privacy policy.
If no keys are configured, Nmonic runs with dummy providers, no network calls are made for transcription or summarization, and no audio leaves your Mac.
4. Where data is stored
All Nmonic-produced data lives at ~/Documents/Nmonic/ on your Mac, as one JSON file per meeting (meeting-{unix_timestamp}.json). The schema is documented in the GitHub repository. The files are plain text; you can read, edit, back up, and delete them with any tool you choose.
5. Your rights
Because Nmonic has no servers or accounts, the usual rights-against-the-controller (access, rectification, erasure, portability) are trivially satisfied: you have full direct control over the files in ~/Documents/Nmonic/. Read them, edit them, copy them, delete them. There is nothing held by us to request.
For data held by Deepgram, Anthropic, or OpenAI, exercise your rights with those services directly using your own account.
6. Children
Nmonic is not directed at children under 13 and has no mechanism for collecting any personal information from anyone, including children.
7. Security
All third-party API calls use TLS. API keys are held in process memory only. JSON files on disk inherit the security of your Mac's filesystem and your user account. We recommend enabling FileVault if you store sensitive meeting transcripts on a portable device.
8. Changes to this policy
If this policy changes materially, the effective date at the top of this page is updated and a note is added to the project repository's CHANGELOG. Because there are no accounts, we have no way to email you. Watch the GitHub repository if you want to be notified.
9. Contact
Questions, audit requests, or vulnerability reports: hello@nmonic.app. Usually a reply within 48 hours.