Subprocessors

DictaFlow Medical Subprocessor List

Last updated: October 22, 2026. This page summarizes production subprocessor categories for Medical customers. Specific BAA copies, settings screenshots, and contract evidence are available through customer/vendor review rather than posted publicly.

Medical BAA and HIPAA safeguards: DictaFlow has signed the required agreements with all providers listed below, including applicable BAAs or downstream business-associate terms for providers handling PHI. For PHI-bearing Medical workflows, DictaFlow restricts clinical data processing to approved providers covered by those terms. Retention and model-training settings are reviewed before a provider route is enabled, and BAA-provider enforcement uses a fail-closed production allowlist. Medical customers must have the applicable customer BAA and reviewed settings in place before using DictaFlow Medical with PHI. These contractual and operational safeguards are not a government certification.
Vendor / category Service Data role Medical controls
Microsoft Azure (backend hosting) and Google Firebase / Firestore Backend hosting, database, authentication support, and operational infrastructure. May store account, configuration, usage, audit, disclosure, and operational metadata. Medical backend mode, restricted admin access, audit/disclosure records, and BAA-covered deployment review.
Deepgram Speech transcription when enabled by Medical backend configuration. Receives audio and approved keyterm hints only for requested transcription work. Provider allowlist enforcement, BAA coverage, and Medical disclosure metadata.
OpenAI Transcription or formatting routes when enabled by Medical backend configuration. Receives audio or text only when the selected model route is allowlisted. Provider allowlist enforcement, BAA coverage, and no direct client-side Medical bypass.
Groq Transcription fallback and formatting routes when enabled by Medical backend configuration. Receives audio or text only when a Groq-backed route is allowlisted. Provider allowlist enforcement, BAA coverage, and Medical disclosure metadata.
Resend / Postmark Transactional, lifecycle, support, and reviewed customer communications. May process account identifiers and support messages. Users should not send PHI through ordinary email unless an approved support workflow is in place. Medical support guidance, PHI warning copy, and BAA-covered workflow review where PHI or PHI-linked metadata may be present.
Stripe Payments, checkout, billing portal, and subscription status. Payment data only. Patient information should not be included in checkout metadata, invoices, receipts, or billing support notes. Payment-only use; Medical policies prohibit PHI in Stripe metadata and billing messages.

Clinical-processing and administrative scope

Deepgram, OpenAI, and Groq are clinical-processing providers only when an approved Medical route is enabled. Microsoft Azure hosts the Medical backend, while Google Firebase / Firestore supports the database, authentication, and operational roles described above. Stripe is limited to billing and subscription operations and is not an approved patient-content route. Resend / Postmark are used for administrative communications; ordinary email is not an approved PHI channel. A separately approved, BAA-covered support workflow is required if PHI or PHI-linked metadata must be handled for support.

Provider allowlist

The Medical backend's BAA-provider enforcement is configured to fail closed. PHI-bearing audio or text is routed only through providers present in the production allowlist after the applicable executed BAA or downstream business-associate terms and retention/training settings are reviewed.

Change notice

Material subprocessor changes are reviewed before production use and can be communicated to customers according to the applicable customer agreement or BAA.