Skip to content
Privacy & Security11 min read · Published 2026-09-05

Where Does Your Voice Data Go? A Privacy Deep-Dive into Popular Dictation Apps

A technical, packet-by-packet comparative analysis of data retention, sub-processors, and network transit across Otter.ai, Dragon NaturallySpeaking, OpenAI Whisper API, and Murmur local dictation.

S
Murmur Security & Compliance GroupInformation Security & Architecture
Key Strategic Takeaways
  • 01.Cloud dictation platforms stream raw audio across public network interfaces to third-party cloud infrastructure (AWS/GCP/Azure) with multiple analytics sub-processors.
  • 02.OpenAI API terms specify 30-day data retention by default, leaving customer transcripts subject to discovery and subpoena risks under the third-party doctrine.
  • 03.Dragon NaturallySpeaking cloud editions centralize audio for acoustic retraining unless enterprise customers negotiate bespoke opt-out riders.
  • 04.Murmur processes voice in volatile RAM via whisper.cpp, discards raw PCM audio upon text insertion, and makes zero network requests.

The Illusion of "Free" and Convenient Voice Dictation

Voice dictation has become an indispensable productivity tool. Articulating complex software logic, drafting sensitive litigation arguments, or writing psychotherapy notes at 160 words per minute feels revolutionary compared to keyboard fatigue.

However, behind the polished user interfaces of modern speech-to-text applications lies a fundamental architectural divide:

1.
Cloud-First Architecture: Audio is captured by your microphone driver, encoded into compressed lossy formats, and streamed over public Internet connections to multi-tenant cloud servers.
2.
Local-First Architecture: Audio is captured directly into volatile system RAM, processed by a local neural network running on your device's GPU or CPU, and injected into the target window without opening a single network socket.

To understand the tangible risks of this divide, we conducted packet-capture inspections, reviewed vendor terms of service, and audited sub-processor registers across four leading dictation technologies:

  • Otter.ai
  • Nuance Dragon (Dragon Professional Anywhere)
  • Whisper via OpenAI API (used by many SaaS wrappers including Wispr Flow)
  • Murmur (on-device whisper.cpp)

  • Comparative Architecture & Data Flow Breakdown

    ┌────────────────────────────────────────────────────────────────────────────────────────┐
    │                        HOW VOICE DATA TRAVELS: 4 ARCHITECTURES                         │
    ├───────────────────┬─────────────────────────┬──────────────────────┬───────────────────┤
    │ Application       │ Network Path            │ Remote Sub-processors│ Cloud Retention   │
    ├───────────────────┼─────────────────────────┼──────────────────────┼───────────────────┤
    │ Otter.ai          │ WebSockets → AWS S3     │ AWS, Segment, Stripe │ Indefinite default│
    │ Nuance Dragon     │ HTTPS TLS → MS Azure    │ Microsoft Azure      │ Up to 90 days     │
    │ OpenAI Whisper API│ HTTPS POST → OpenAI API │ OpenAI, Cloudflare   │ 30-day default log│
    │ Murmur (Local)    │ NONE (Air-gapped RAM)   │ ZERO (100% On-device)│ ZERO (0 Bytes)    │
    └───────────────────┴─────────────────────────┴──────────────────────┴───────────────────┘

    Deep Dive 1: Otter.ai (Cloud Recording & Meeting Bots)

    Otter.ai is widely used for meeting notes and real-time transcription. However, its architecture is engineered around continuous cloud streaming:

  • Network Egress: Every second of audio is uploaded in real time over WebSockets to Otter's ingestion endpoints hosted on Amazon Web Services (AWS).
  • Sub-processors & Third-Party Trackers: A network audit reveals active telemetry to third-party marketing, customer engagement, and analytics vendors (including Segment, Amplitude, and Mixpanel) embedded in client applications.
  • Data Retention & Model Training: Historically, Otter's privacy terms permitted using user audio and transcripts to train proprietary machine learning models unless users explicitly opted out. While business tiers offer stricter controls, transcripts remain stored in cloud databases accessible to authorized support personnel.
  • The Third-Party Doctrine Risk: Because transcripts reside on external servers, US law enforcement can issue subpoenas or National Security Letters directly to the hosting provider under 18 U.S.C. § 2703 (Stored Communications Act) without notifying the end user or client.

  • Deep Dive 2: Nuance Dragon (Dragon Professional Anywhere)

    For decades, Dragon NaturallySpeaking was the gold standard of local desktop dictation. However, Nuance's modern enterprise products (now owned by Microsoft) have shifted heavily to cloud-hosted acoustic engines:

  • Network Egress: Voice dictation streams audio to Microsoft Azure infrastructure in regional data centers.
  • Acoustic Profiling: Audio samples are uploaded to build centralized speaker profiles. While this improves accuracy for individual accents, it requires associating your biometric vocal profile with a cloud user identity.
  • Enterprise Isolation: Dragon offers robust BAA and SOC 2 Type II compliance for enterprise healthcare and legal customers, but it requires costly enterprise agreements ($1,200+/seat/year) that are inaccessible to solo practitioners, freelancers, and independent developers.

  • Deep Dive 3: Whisper via OpenAI API (The SaaS Wrapper Model)

    Many modern voice dictation apps (such as Wispr Flow, Superwhisper cloud modes, and custom menu bar utilities) rely on OpenAI's hosted Whisper endpoint (api.openai.com/v1/audio/transcriptions):

  • Network Egress: Audio is captured into a local WAV/MP3 file and sent via an HTTPS POST request (multipart/form-data) across the public Internet.
  • OpenAI Data Retention Policy: Under OpenAI's standard business API data usage policies:
  • > "OpenAI retains API data for 30 days for abuse and misuse monitoring purposes, after which it is deleted (unless legally required otherwise)."

  • The 30-Day Vulnerability Window: Even if the wrapper application promises "we delete your audio immediately," the underlying OpenAI endpoint retains the unencrypted audio file and generated transcript for 30 calendar days in remote US data centers. If a breach occurs or a valid subpoena is served during that 30-day window, your client communications or trade secrets are exposed.
  • Commercial Rate Limits & Lock-In: Reliance on the OpenAI API enforces strict payload limits (25MB per request) and recurring per-minute charges that force SaaS providers to charge recurring monthly subscriptions or cap free usage (e.g. Wispr Flow's 2,000 words/week limit).

  • Deep Dive 4: Murmur (100% Local-First & Air-Gapped)

    Murmur was engineered from the ground up to eliminate policy promises and replace them with physical hardware isolation:

  • Audio Capture to RAM: Audio is captured from the default input device into a fixed-size ring buffer in volatile system RAM using native platform audio bindings (cpal in Rust).
  • Zero Temporary Files on Disk: Audio is decoded directly from RAM. No WAV, MP3, or cache files are written to the file system during dictation.
  • Local Whisper Model Inference: Speech frames are passed across an in-process C++ boundary to whisper.cpp, compiled with native hardware acceleration:
  • - macOS: Apple Silicon Metal GPU shaders and Accelerate framework.

    - Windows: DirectML (DirectX 12 GPU compute) and NVIDIA CUDA / Tensor Cores.

  • RAM Erasure on Paste: The instant transcription completes, formatted text is injected into the OS active window, and the audio buffer in RAM is zeroed and freed.
  • Zero Network Sockets: The Murmur binary contains zero analytics SDKs, zero telemetry endpoints, and zero cloud API keys. You can disconnect your Wi-Fi, enable Airplane Mode, or run Murmur in an air-gapped SCIF—it operates identically.

  • Detailed Privacy & Regulatory Comparison Table

    Privacy DimensionOtter.aiNuance Dragon CloudOpenAI Whisper APIMurmur (Local)
    Audio Processing LocationAWS Cloud ClustersMS Azure CloudOpenAI Cloud (US)Local GPU / RAM
    Outbound Bytes per Hour~15–25 MB~20–30 MB~18–35 MB0.00 Bytes
    Default Cloud RetentionIndefinite (User account)30–90 days30 days (Abuse log)0 seconds (RAM only)
    Account / Login RequiredMandatory (Email/SSO)Mandatory (License ID)Mandatory (API key)None (100% Anonymous)
    Third-Party Sub-processorsAWS, Segment, MixpanelMicrosoft AzureCloudflare, OpenAI0 Sub-processors
    Subpoena VulnerabilityHigh (US Cloud servers)High (Microsoft Azure)Moderate (30-day window)Zero (Physical machine only)
    Air-Gap / Offline CapableNoNoNoYes (100% Offline)
    HIPAA Compliance PathEnterprise BAA ($$$)Enterprise BAA ($$$)Zero Data Retention BAAHardware Isolation (Local)
    Cost$10–$30 / month$1,200+ / yearUsage-based / SaaS feeFree & Open Source (MIT)

    Legal & Regulatory Implications for Professionals

    1. Attorney-Client Privilege (ABA Model Rule 1.6)

    Under American Bar Association Model Rule 1.6(c), lawyers are legally obligated to "make reasonable efforts to prevent the inadvertent or unauthorized disclosure of, or unauthorized access to, information relating to the representation of a client."

    Streaming privileged strategy notes, witness interviews, or settlement negotiations to cloud speech vendors without explicit client disclosure exposes attorneys to malpractice allegations and potential waiver of privilege.

    2. HIPAA & Healthcare Privacy (45 CFR § 164.502)

    Covered healthcare entities cannot disclose Protected Health Information (PHI) to third-party vendors without an executed Business Associate Agreement (BAA). Using consumer cloud dictation tools for patient clinical summaries violates HIPAA guidelines. Because Murmur never transmits data outside the hospital laptop, it does not act as a cloud intermediary.

    3. Enterprise NDAs & Proprietary Source Code

    Software engineers dictating proprietary algorithms, API keys, or unreleased system designs into cloud voice utilities risk violating non-disclosure agreements with employers and clients.


    How to Audit Your Dictation Tools Yourself

    Don't trust marketing claims—verify network traffic on your own machine:

    macOS: Packet Monitor with tcpdump

    # Monitor all outbound packets from your machine while dictating:
    sudo tcpdump -i any -n "not port 53 and not port 443"

    (Notice: With Murmur active, zero packets are emitted. With cloud tools, continuous packet streams to AWS/Cloudflare appear instantly.)

    Windows: Packet Monitor with pktmon

    # Create a filter and monitor active adapters:
    pktmon filter add -t TCP -p 443
    pktmon start --etw
    # Dictate your text, then stop and inspect:
    pktmon stop
    pktmon format PktMon.etl -o log.txt

    Little Snitch / LuLu (macOS) & Portmaster (Windows)

    Configure application-level firewalls to block all outbound connections for Murmur. You will notice that Murmur functions flawlessly with all network adapters disabled.


    Conclusion: Data Sovereignty as a Default

    Privacy should not be an expensive enterprise add-on or a checkbox in a 40-page terms of service agreement. By leveraging modern local hardware acceleration and open-weights Whisper models, Murmur proves that you no longer need to sacrifice privacy to achieve world-class voice dictation.

    Short-Form Content Angle
    "When you press dictation, where does your voice actually travel? We ran network packet captures on 4 major tools."
    "The legal difference between 'We don't sell your data' and 'Your audio never touches a network interface'."

    Experience 100% On-Device Voice Typing

    Murmur runs locally on your Mac or Windows PC. No cloud transcription, no audio uploads, zero subscriptions.

    Download Murmur (Free Forever)