HIPAA dictation software that keeps patient information on your machine

Whisperstream is a $29 one-time dictation app for Windows. In Lockdown Mode, Whisperstream's transcription, AI cleanup, and transcript storage run on your own PC, and its cloud providers are turned off. Lanreal does not receive audio or transcript content through that pipeline. The application that receives the text is a separate part of your workflow and must be assessed separately.

The short answer

No software is HIPAA certified. HHS does not endorse or recognize private certifications regarding the Security Rule; compliance describes how the covered entity (under HIPAA, that is you or your practice) uses a tool inside its own program.

The local-only angle

In Lockdown Mode, Lanreal does not receive audio or transcript content through Whisperstream's dictation and cleanup pipeline. The destination application still receives the text you direct Whisperstream to deliver.

Why no BAA

A business associate is a person or entity that creates, receives, maintains, or transmits PHI on your behalf (45 CFR 160.103). Lanreal does none of those things for content in the Lockdown dictation pipeline, so Lanreal is not a business associate for that pipeline. Assess the destination separately.

Who this is for

Therapists, solo and small-practice clinicians, and anyone dictating patient information on a Windows PC without an IT department to run a BAA process. If your sensitivity driver is attorney-client confidentiality instead, see legal dictation software.

If you searched for "HIPAA compliant dictation software", here is the part most vendors skip: that label does not exist as a certification. HHS does not endorse or recognize private certifications regarding the Security Rule, and FTC business guidance is blunter still, noting that HHS does not certify companies or products as HIPAA compliant. There is no seal to earn, no registry to check, and no product that can hand you compliance in a download.

The FTC has gone after companies that leaned on that label anyway: its 2023 complaint against BetterHelp alleged a deceptive HIPAA seal and false "HIPAA certified" representations, and in 2020 it alleged that SkyMed displayed a "HIPAA Compliance" seal for roughly five years with no third-party review behind it. Both cases settled, and both are framed here as allegations, but the pattern matters more than the case law: a compliance badge on a product page is a marketing artifact, not a legal status.

So the useful question is not "which dictation software is HIPAA compliant" but "where does my session note go when I dictate it, who can access it, and what safeguards does the tool support". Compliance lives in how you run your practice, not in any software box. The rest of this page answers the useful question for Whisperstream's Lockdown Mode, and it applies the same honest framing to the cloud alternatives.

You already know the drill from every other tool in your practice: if a company handles PHI for you, you need a BAA first. HIPAA's definition is what decides it. A business associate is a person or company that creates, receives, maintains, or transmits protected health information on your behalf (45 CFR 160.103). Those four verbs are the whole test. If a vendor's servers do any of the four with your patients' information, that vendor is your business associate, and HIPAA requires a business associate agreement before PHI can flow to them.

Cloud dictation trips the test. The moment you dictate a session note or a patient email into a cloud tool, that audio travels to the vendor's servers to be transcribed, and receiving and transmitting a patient encounter is exactly what the definition covers. HHS's cloud computing guidance says a cloud service provider that creates, receives, maintains, or transmits ePHI on behalf of a covered entity is a business associate, and that this is true even if the provider stores only encrypted ePHI and lacks the encryption key. That is why the legitimate cloud path comes with a BAA.

Local-only dictation never enters the test. In Lockdown Mode, your microphone audio is transcribed on your device, AI cleanup uses an on-device model, and Whisperstream's cloud providers are turned off. Lanreal does not receive your audio or transcript content through that pipeline. The destination application receives the text and remains a separate system to assess. Lanreal is not a business associate for the Lockdown pipeline because it does not handle the PHI in that pipeline.

Free local dictation tools are a reasonable instinct. If a vendor never receives the audio, that vendor is not a business associate for the audio-processing path. The same applies to Lanreal's role in the Lockdown pipeline. That instinct gets the network half right. The half your risk analysis also has to cover is what happens on the machine itself: per their published source code, the popular free local dictation tools we audited in July 2026 store plaintext transcripts and unencrypted audio of every dictation, saved unconditionally, with no history-off switch and no lock.

For patient notes, that means months of dictated PHI sitting readable on disk for anyone who can reach the PC, its backups, or a sync folder, which is the same access-control and encryption-at-rest vocabulary you already apply under 45 CFR 164.312. Locality is necessary for the no-BAA path, but it is not sufficient on its own. We published the full tool-by-tool findings in our dictation app privacy audit.

Here is what Lockdown Mode does for your notes and transcripts, mapped to the HIPAA Security Rule's technical safeguards (45 CFR 164.312) in the regulation's own vocabulary, so you can drop it straight into your risk analysis. Lockdown Mode's features are designed to align with these safeguards; the map is a description of what the software does, not a compliance determination, which only you can make for your own practice. Two rows below are marked Addressable, the regulation's term for safeguards you must assess and document rather than implement in one fixed way. Addressable is not optional.

Access control45 CFR 164.312(a)(1)

Your transcript history is locked behind a password. A key derived from that password wraps the encryption key. Without your password or your one-time recovery code, the history stays encrypted.

Automatic logoff45 CFR 164.312(a)(2)(iii) · Addressable

Transcripts lock again automatically after a period of inactivity that you set.

Encryption at rest45 CFR 164.312(a)(2)(iv) · Addressable

Transcript history is encrypted at rest with AES-256-GCM.

Audit controls45 CFR 164.312(b)

A private, content-free access log records when your history is opened, locked, and unlocked, and when an unlock fails. It never records what your transcripts say, and it stays on your device.

Integrity45 CFR 164.312(c)

The authenticated encryption used for transcript history is designed to detect tampering, which helps confirm your transcripts have not been altered.

Person authentication45 CFR 164.312(d)

Opening transcript history requires your password, and repeated failed attempts trigger escalating delays.

Transmission security45 CFR 164.312(e)

In Lockdown Mode Whisperstream blocks its optional cloud AI cleanup and keeps its transcript history local. Text you deliver to a destination application, and any separate Agent Speak interaction with Claude Code or its provider, follows that system's transmission and security controls.

Administrative safeguards

Your risk analysis, your policies, and your workforce training stay yours (45 CFR 164.308). No software performs these for you.

Physical safeguards

So do facility access and device controls, including who can physically reach the PC that holds your transcript history (45 CFR 164.310).

User identity

Whisperstream relies on your Windows account to know who is using it. The Lockdown password is a second gate on the transcript history, not a separate identity for each person who shares the device. If several people share one Windows login, they share one identity.

Recovery

If you lose both your password and your one-time recovery code, your transcript history cannot be recovered. That is by design: the encryption key is wrapped by a key derived from your password, so there is no reset path through Lanreal.