Omi Health — Sub‑processors
Version: 1.8
Last updated: 25 August 2026
Provider: Omi Health B.V., Eindhoven, Netherlands
Contact: [email protected]
This page lists the sub‑processors used by Omi Health B.V. to provide the Speech-to-Text Developer API. It also retains, for the record, the sub‑processor list of the discontinued Omi Scribe Cloud product.
We will update this page when sub‑processors are added or changed. Customers with a DPA may subscribe to change notifications by emailing [email protected].
Note: For customer‑managed / self‑hosted deployments, the Customer selects and controls its own infrastructure and providers; the sub‑processor lists below do not apply.
1. STT Developer API (api.omi.health / api.eu.omi.health)
The developer API — including the developer console, playground, and Omi‑operated Keycloak sign‑in — is hosted and processed in AWS eu‑central‑1 (Frankfurt), European Union.
| Sub‑processor (legal entity) | Service | Purpose | Data processed | Location |
|---|---|---|---|---|
| Amazon Web Services EMEA SARL | AWS | Hosting and processing of Customer Content, and hosting of the Omi‑operated Keycloak identity service (account and identity data) | Customer Content and Service Data | eu‑central‑1 (Frankfurt) |
| Amazon Web Services EMEA SARL | Amazon SES | Transactional email delivery (account and billing email) | Service Data (recipient email address, message metadata; no audio or transcript content) | eu‑central‑1 (Frankfurt) |
| Cloudflare, Inc. | Cloudflare | DNS, CDN, and edge network for the website and console | Service Data (request metadata) | Global edge |
| Stripe Payments Europe, Ltd. | Stripe | Billing and payments | Billing contact and transaction data (no audio or transcript access) | EU / global |
2. Omi Scribe Cloud (Managed) — discontinued
Omi Scribe Cloud was discontinued in August 2026 and its deployment
(Microsoft Azure, Sweden Central, EU) has been decommissioned. Microsoft is no
longer a sub‑processor of Omi Health. Records of the processing that occurred
while the product was in service are retained internally and are available to
affected customers on request via [email protected].
3. Customer‑controlled integrations (not sub‑processors)
The following are typically not sub‑processors because they are selected and controlled by the Customer, and they do not process Customer Content on Omi Health’s behalf:
- Identity providers (SSO) configured by the Customer (e.g., Microsoft Entra ID / Azure AD, Google Workspace / Google Identity)
- The Customer’s EHR/EMR, storage, or internal systems connected via integration/export
- Customer-provided model endpoints (if the Customer configures the Service to call them)
These providers may receive limited user authentication data or exported content under the Customer’s own terms and policies.
4. Changes and objections
When we add or replace a sub‑processor that will process Customer Content or Service Data on our behalf — for either the Scribe cloud Service or the STT Developer API — we will:
1. Update this page at least 30 days before the new sub‑processor begins processing data (unless legally required to do so sooner). (Note: the Dutch Healthcare Addendum extends this to 3 months for customers who have signed that addendum.)
2. Notify Customers who have subscribed to sub‑processor change notifications. API customers are notified through the console and, where subscribed, by email.
3. Where a DPA applies, allow Customers to object within the timeframe set out in the DPA.
5. Contact
Questions about sub‑processors: [email protected]