“HIPAA-compliant” names a contract, not an architecture.

Every healthcare AI scribe leads with “HIPAA-compliant,” and if you are shopping for a HIPAA-compliant AI notetaker the label sounds like the finish line. Read it precisely and it names a contract: the vendor will sign a business associate agreement covering the session data it receives from you. The agreement makes the disclosure lawful. It does not make the disclosure unnecessary, and unnecessary is the stronger standard available in 2026. None of this is legal advice; the primary sources are linked throughout.

There is no such thing as HIPAA-certified software

Start with the part vendors rarely volunteer: HHS recognises no HIPAA certification for products, services or organisations. Compliance under the Privacy and Security Rules is a property of a covered entity's practices, assessed by the Office for Civil Rights after something goes wrong, not a stamp a tool can earn in advance. When a notetaker's pricing page says “HIPAA-compliant,” the load-bearing claims underneath are two: the vendor believes its safeguards meet the Security Rule, and it is willing to sign a business associate agreement. Both can be true and your client's session still ends up on infrastructure you do not control.

Who the rules actually bind

HIPAA's definitions do real work here. The rules bind covered entities: health plans, clearinghouses, and providers who transmit health information electronically for covered transactions. A therapist billing insurance is almost certainly one. The rules then reach vendors through the business associate definition in 45 CFR § 160.103: anyone who creates, receives, maintains or transmits protected health information on a covered entity's behalf. A cloud notetaker on a session call is squarely that, which is why § 164.502(e) requires the BAA before the audio flows.

Coaches sit outside this machinery entirely. A coach is generally not a covered entity, so there is no BAA to sign and “HIPAA-compliant” is marketing rather than a legal category that applies to them. Their confidentiality duties are real but come from client agreements and ethics codes such as the ICF's, and a cloud recording collides with those duties just the same. The vertical version of this argument, including where tools like Upheal and Mentalyc land, is in the therapists and coaches post.

What a BAA does, stated exactly

A business associate agreement is the legal instrument that permits your client's session to leave your practice. It obliges the vendor to safeguard what it holds, restricts what it may do with the data, and requires it to notify you of breaches under the Breach Notification Rule. Those are real obligations with real penalties behind them.

Now list what the BAA does not do. It does not make the vendor unbreachable. It does not put stored sessions beyond the reach of legal process; subpoenas find records wherever they sit. It does not survive every acquisition on your terms. And it does not change the underlying fact that a verbatim record of the most sensitive conversation in professional life now exists outside your practice, for however long the vendor's retention schedule says. It papers the disclosure. It does not prevent it.

The conduit myth

One escape hatch gets cited in vendor FAQs more than it should: the conduit exception. It is real and it is narrow. HHS's cloud computing guidance limits it to pure transmission services in the mold of a courier: the data passes through and only transiently. A service that stores session audio or transcripts is a business associate even if it cannot read the data, even if the data is encrypted and the vendor holds no key. “We are just a pipe” stops being true the moment anything about your session persists on the vendor's side, and for a notetaker, persistence is the product.

The architecture where the question does not arise

Every obligation above is triggered by one event: protected health information reaching a third party. Remove the event and the chain never starts. That is an architectural choice, not a paperwork one, and it is now practical because on-device transcription caught up with the cloud.

Fazit captures the call without a bot, transcribes it on your Mac, and writes the note with a local model, so neither audio nor transcript reaches us or any third party. The audio itself is never written to disk: it lives in a fixed-size RAM ring buffer, defined in AudioRingBuffer.swift, and is destroyed on every exit path, which is why each note carries audio_retained: false in its frontmatter. The security page documents each invariant with the code path that enforces it. Under § 160.103 there is no business associate for session content, because no one creates, receives, maintains or transmits PHI on your behalf. The question the BAA answers does not get answered. It does not arise.

What on-device does not do for you

Honesty about the boundary: no tool makes a practice HIPAA compliant, this one included. If you are a covered entity, the Security Rule still governs your own devices and records. The finished session note in your vault is part of the designated record set: FileVault, screen locks, access to the machine, backup hygiene and retention are your responsibility, exactly as they are for the paper notes the profession kept for a century. What on-device processing removes is the third party: the vendor risk assessment, the subprocessor list, the breach exposure and the BAA for session content. What remains is a records practice you already run, under rules that were written assuming the records live with you.

Five questions that sort the market

FIVE QUESTIONS FOR ANY VENDOR CLAIMING "HIPAA-COMPLIANT"

1. Will you sign a BAA, and does it cover every subprocessor
   that touches session content?
2. Does session audio or its transcript ever reach your
   infrastructure at all?
3. How long is a session retained, and what is exempt from
   deletion (backups, logs, model training)?
4. Has your service ever been named in a breach notification
   under 45 CFR 164.400?
5. If my client asks who holds a record of their session,
   how many organisations are in the honest answer?

Fazit's answers: no BAA needed for session content because
none reaches us; never; nothing is retained anywhere; no;
and the honest answer is one, you.

The same architectural logic comes out simple for EU practitioners under a different rulebook: see the GDPR analysis. And whatever tool you choose, recording-consent law sits on top of all of it; the US map is in Is It Legal to Record Client Calls?

Frequently asked questions

Is there an official HIPAA certification for software?

No. HHS recognises no HIPAA certification for products or vendors. “HIPAA-compliant” on a marketing page means the vendor believes its safeguards meet the Security Rule and that it will sign a business associate agreement. Compliance is a property of a covered entity's practices, assessed after the fact, not a badge a tool can carry.

Does a HIPAA-compliant AI notetaker need a BAA?

If the vendor creates, receives, maintains or transmits protected health information on your behalf, yes: 45 CFR § 164.502(e) requires a business associate agreement before the data flows. A tool that processes everything on your own machine and sends nothing to any vendor never creates that relationship for session content, because no third party receives PHI.

Are coaches covered by HIPAA?

Generally no. Coaches are usually not covered entities, so there is no BAA to sign and “HIPAA-compliant” is marketing rather than a legal category that applies to them. Their confidentiality duties come from client agreements and ethics codes such as the ICF's, and those duties still collide with a cloud recording.

Does using an on-device notetaker make my practice HIPAA compliant?

No tool makes a practice compliant. On-device processing removes one large obligation, the business associate chain for session content, because the audio never leaves your machine. Your own Security Rule duties remain: the finished note is still part of your records, and disk encryption, access control and retention stay your responsibility.