What "On-Device" Has to Mean in a Privilege Fight

In privilege disputes involving digital records, courts look past marketing language and examine how the data is handled. The question in cases such as United States v. Heppner (S.D.N.Y. 2026) is whether confidential material leaves the user's controlled hardware and, if so, under what contractual terms. In Heppner, the court held that a software privacy policy allowing third-party data sharing defeated any reasonable expectation of confidentiality.

For privileged legal work, labels such as "local" or "secure" carry no legal weight. The key question is whether audio files, transcripts, or summaries are sent to third-party servers. If data leaves the computer, the analysis turns to third-party disclosure rules, vendor privacy policies, and subprocessor access rights. This article is for informational purposes and is not legal advice.

Practitioners must examine the exact boundary between local processing and cloud transmission.

RecapMuse's technical architecture and current limits are straightforward. The Mac application records meetings and calls locally without sending a bot into the call. Apple's on-device speech engine generates the live transcript entirely on the user's Mac, and that transcript never leaves the device. The Diary step, however, sends that recording's audio to OpenAI by default, using the lawyer's own API key, to draft the titled summary. Users can choose a fully local summarization engine in the app settings today. Making local summarization the default is the planned next development step and has not shipped. RecapMuse is not described as 100 percent on-device from end to end.

RecapMuse also lets users search all past recorded conversations locally. RecapMuse Counsel, an edition designed for legal practice, is in development and is not yet available.

Attorneys evaluating these tools should ask:

First, does the live audio stream or transcript leave the machine during recording? If speech recognition occurs on cloud servers, every spoken word is sent over the internet to an external provider.

Second, if the software makes external API calls, whose credentials does it use? Data handling terms may differ significantly when a practitioner uses an individual API key under an enterprise agreement instead of a shared consumer endpoint.

Third, can the user bypass cloud processing entirely? If the software offers a local processing model, practitioners can keep sensitive case files on isolated hardware.

Privilege protection depends on whether a product's claims match how it works. A transcript produced on the machine is never transmitted at all, which is a different fact pattern from one produced on a vendor's servers. A summarisation step that calls an external API is a transmission, on whatever key it runs, and has to be managed as one or switched to the local engine. Courts examine technical facts, not marketing descriptions.