Meeting transcription apps that do not add a call participant

The participant list is a poor proxy for the recording path. A native app can capture microphone and system audio directly. A browser extension may depend on browser audio or the meeting platform’s captions.

For readers asking which meeting transcription apps do not use a bot, verified options as of September 17, 2026 include Noats, Granola, Jamie, Krisp, Otter Desktop, Notta Desktop, Circleback Desktop, Supernormal, Read AI Desktop, Bluedot, Shadow, TwinMind, Tactiq, tl;dv Desktop, Fellow Desktop and Fathom 3.0 for supported accounts. This availability was checked September 2026.

Some also offer participant-based capture. Select the named desktop application or extension route. Then check its audio source and processing location instead of treating an empty participant list as evidence that meeting data stays on the device.

These apps capture without adding a participant

The verified list is Noats, Granola, Jamie, Krisp, Otter Desktop, Notta Desktop, Circleback Desktop, Supernormal, Read AI Desktop, Bluedot, Shadow, TwinMind, Tactiq, tl;dv Desktop, Fellow Desktop and Fathom 3.0 for supported accounts. Availability was checked September 2026.

Native desktop products generally take the microphone channel and computer output. Noats, Granola, Krisp, Otter Desktop, Notta Desktop, Circleback Desktop, tl;dv Desktop and others in the list document this kind of route on their supported operating systems. Supernormal moved capture to its Mac and Windows desktop application in April 2026. Fathom offers transcript-only and audio-only participant-free modes to supported accounts, with its rollout still changing when checked September 2026.

Browser tools have a narrower input. Bluedot handles supported Google Meet, Zoom and Teams sessions opened in Chrome. Tactiq supports those services in Chrome or Edge, and its Zoom workflow requires Zoom automated captions. Within their own platforms, Teams transcription and Google Meet notes also work without an external participant and notify attendees.

An empty roster does not locate the meeting files

Participant-free capture describes how audio enters a product. It does not establish where transcription runs, where notes are generated or how long the provider retains a recording. Two applications can look identical in a meeting roster while sending their inputs through materially different processing routes.

For Noats, local is the whole file path: audio capture, transcription, speaker separation, note generation and storage all stay on the Mac by default. Whatever your Mac's microphone hears is attributed to you; the voices on the other end of a call are split into speakers. Recording begins when you start the note. We control the capture and processing routes in our application, and we keep the default pipeline on the Mac.

Transcription and speaker separation run on your Mac's Apple silicon once the models are downloaded. Your audio, transcripts, speaker labels, notes, folders and chat history are written to a database and plain files in your own Application Support folder. Any note exports as markdown with a keystroke. The field-level account of Noats network requests describes the optional provider connections separately.

Other products make different choices. Krisp states that processing may happen on the device or on its servers depending on language and settings, with stored meeting data retained until deletion is requested. Bluedot stores recordings, transcripts and summaries in its cloud library. Zoom, Meet, Teams and other call providers still carry the underlying conversation under their own terms.

Choose the job, then test the route

Use the same test for any candidate:

1. Start a supported meeting with the desktop application or browser extension you intend to use.
2. Begin capture from that named application or extension rather than selecting its participant-based route.
3. Inspect the meeting roster and confirm that no new participant appears during this test.
4. Identify whether the input is computer output, microphone input or captions supplied by the meeting platform.
5. Check where transcription, note generation and storage occur and what deletion controls the provider documents.

Mobile support needs its own check. TwinMind offers iOS, Android, Mac, Windows and browser applications, checked September 2026, but its mobile guide says it cannot capture phone calls or Zoom, Meet and Teams sessions running on the same phone. Apple’s native call recorder follows another route: it gives both participants an audible notice and can produce a transcript.

Removing a visible participant does not remove consent duties. Federal law generally provides a one-party-consent baseline in the United States, subject to statutory exceptions.

State requirements vary. The Reporters Committee guide advises applying the stricter jurisdiction’s rule to interstate calls. Employer rules and meeting-platform policies can add requirements.

Otter Desktop handles live capture. TurboScribe begins with an existing audio or video upload, making it the better fit when the recording already exists.

Otter’s privacy policy identifies the company as registered in Delaware with a California address. It is a US company, not a Chinese company. Otter is also the defendant in unresolved privacy litigation. An August 13, 2026 order dismissed some claims and allowed others to proceed, so the allegations are not adjudicated facts.

Choose the job first. Live calls point to tools such as Noats or Otter Desktop. Existing files point to an upload service such as TurboScribe. Then filter by operating environment, input source, processing location and consent requirements.