HC Healthcare evaluation

On-device dictation for clinical teams.The transcription vendor leaves the data flow.

Recognition and cleanup run on the Mac, so no transcription provider receives clinical speech. Compliance is decided by your deployment. Here is what the software does, and how to evaluate it with synthetic data.

Audio never saved or sentNo transcription vendorAES-256-GCM at restCopy only mode

Fig. 01 — Floating bar · three real states: audio is held in memory while listening, transcribed on the Mac, saved to History, then pasted once at the cursor.

01 Processing location

One less party in the path.

When dictation is transcribed in a vendor cloud, that vendor's infrastructure, retention, subprocessors and contracts enter your risk analysis. On the Mac, they don't.

Fig. 02. With cloud dictation, audio travels from the microphone over the internet to a vendor cloud, which enters your risk analysis, and text comes back to the cursor. With LockedIn Flow, the microphone feeds speech recognition, cleanup and an encrypted save on the Mac, and the text is pasted at the cursor. After the paste, the text follows the receiving app's own policies.
Where compliance is decidedIn your deployment. Every organization owes its own risk analysis covering its devices, people, contracts and the systems text lands in. LockedIn Flow removes one exposure from that analysis, a transcription provider receiving clinical speech, and leaves the rest of your program with you.

02 The product

In clinical terms.

What happens to a dictation on a managed Mac, from the microphone to the field it lands in.

Fig. 03 — Dictation History · Retention
LockedIn Flow behavior relevant to a healthcare deployment
PropertyBehavior
RequirementsApple silicon Macs, macOS 15 or later, about 484 MB for the speech model.
RecognitionParakeet TDT v3 through Core ML, on the Mac.
Transcription vendorNone. The app does not send audio or transcripts to LockedIn Labs or anyone else; after the paste, text follows the receiving app's policies.
NetworkNever downloads models, checks for updates, sends telemetry or calls a hosted service. Its speech library's downloader is switched off before any model loads.
AudioHeld in memory, never written to disk.
HistoryIn memory until you quit, by default. Seven retention options, from “Do not retain” to “Keep indefinitely”; AES-256-GCM on disk.
DeliverySaved to History first, then one paste at the cursor; the previous clipboard is put back.
Password fieldsFields macOS identifies as password fields are skipped: nothing typed, nothing copied.
Copy onlyNothing is typed into other apps until you choose Copy. Works without Accessibility.
CleanupLocal rules, written for English. The optional Apple Intelligence pass (macOS 26 with Apple Intelligence) is off by default and falls back to the rules when it fails a meaning check.
VocabularyYour terms as reviewable, removable rules, stored encrypted. Learning from edits is off by default.
AccountsNone. No sign-in, no analytics, no telemetry. MIT-licensed, no activation.

03 Evaluation

Run the pilot on synthetic data.

Start on managed Macs with a team build and synthetic dictation. Plan the pilot around six points, owned by your clinical, security and IT leads.

  1. 01

    Synthetic first.

    Dictate made-up content into the apps your teams use. No patient information until your organization approves production use.

  2. 02

    Approved terminology.

    Build vocabulary from an approved term list. Keep it as one CSV you can review, import, and hold under your own change control.

  3. 03

    Clinician review.

    Keep review of high-risk content in the workflow: numbers, negation, laterality, medications and doses, before the text is relied on.

  4. 04

    Verified delivery.

    Test delivery into your record-system and browser fields: focus changes, password fields, and re-inserting from History.

  5. 05

    Defined retention.

    Choose a History retention that fits policy, decide whether meeting notes are used at all, govern clipboard tools, and require FileVault and screen lock.

  6. 06

    Acceptance thresholds.

    Agree accuracy and safety thresholds in advance, measure them on representative workflows, and review them before production use.

04 Beyond healthcare

Same properties, other regulated work.

Legal, finance and public-sector teams that keep dictation off the cloud evaluate it the same way: no transcription vendor, no internet once the speech model is installed, explicit vocabulary, and encrypted local retention with an off switch.

LegalFinancePublic sector

05 Questions

What clinical teams ask first.

How does LockedIn Flow relate to HIPAA?

HIPAA compliance is a property of a deployment: your organization's risk analysis, policies, device controls, workforce practices, contracts, incident response and the systems text lands in. LockedIn Flow's part is architectural. Dictation audio and transcripts are processed on the Mac, so no transcription vendor receives them.

Does clinical dictation go to a vendor cloud?

No. Dictation audio and transcripts are processed on the Mac and are not sent to a transcription provider. The app never downloads models, checks for updates, sends telemetry or calls a hosted service; its speech library's downloader is switched off before any model loads.

After the paste, text follows the policies of the app that received it. The security architecture covers the full data flow.

How should a clinical team start an evaluation?

Request a build for managed Macs, dictate synthetic text into the applications the team uses, and record the results against a pilot plan. Keep clinician review of dictated text in the workflow.

HC Healthcare evaluation

Plan the evaluation with us.

Clinical and security teams can share a non-sensitive outline. Never send patient information, recordings, private terminology, credentials or production configuration through the website.

Architecture statements reviewed against the source · October 2026