Speech-to-Text API & Playground — Privacy Note

Version: 1.6

Published: 30 October 2026

Provider: Omi Health B.V., Eindhoven, Netherlands

Contact: privacy@omi.health


This plain-language note explains what we collect when you use the Omi Speech-to-Text API or the public STT Playground on this website. It sits alongside our Website Privacy Policy, and the API is governed by the Data Processing Agreement where applicable. If anything here conflicts with a signed agreement you have with us, that agreement wins.


The short version


What we collect

Playground (this website)

Speech-to-Text API accounts and keys (for developers)


What we do not do


Model training

Audio you submit and the transcripts we return are never used to train, develop, or improve our models. This restates the commitment in our Data Processing Agreement in plain terms.

Where it runs and who processes it

Choose the region through your endpoint:

Async audio and stored results remain in the region that processed the request. Account records and billing remain in Frankfurt. Retention and our no-training commitment do not change. We rely on these sub-processors:

Our full production sub-processor list is at Sub-processors.


How long we keep things


Your rights

You can ask us to access, correct, or delete personal data we hold about your API account (for example, your console email or stored vocabulary). Because Playground audio and transcripts are not stored, there is usually nothing to retrieve or erase for a given Playground transcription. Contact privacy@omi.health.

You have the right to lodge a complaint with your data protection authority. In the Netherlands this is the Autoriteit Persoonsgegevens.


Changes and contact

We may update this note as the Service evolves. Material changes will be reflected here with a new version and effective date, and we will provide any notice required by law or our Terms of Use.

Privacy questions: privacy@omi.health · Security reports: security@omi.health