Model catalogue · OpenAI
OpenAI Sprachausgabe
OpenAI's speech output models turn text into spoken audio - the reverse of dictation: pleadings to listen to on the way to a hearing, summaries read aloud, announcement texts. Listening does not replace reading the text. They are procured via Azure, and on that route the contractual chain is closed: the confidentiality undertaking under section 203 of the German Criminal Code is signed for the models sold by the platform, and processing takes place in the chosen region - in Europe only Sweden is evidenced so far.
Everything section 203 requires is settled, including the provider's confidentiality undertaking. You do not have to clarify anything further.
What it is good for
- Intelligible German speech output for file extracts and summaries
- Processing in the deployment region and therefore in an EU member state, not only in the data zone
- Same contractual line as the other models sold by Azure
Where it stops
- Evidenced in Europe only in the Sweden region (as of 2026-08-17) - we found no German deployment
- Produces audio from text and does not replace checking that text - for dictation and transcripts the opposite direction applies
- Abuse monitoring is active by default; switching it off depends on a vendor approval that cannot be booked directly
Routes examined
The same model, procured differently, is a different legal position. What is examined per route is the contract chain, not the model.
| Route | Section 203 status | Version on this route |
|---|---|---|
| Microsoft Azure | covered | - |
The conditions behind a conditional status - which piece is open on which route and who closes it - are set out in the full matrix in the German catalogue, and we go through them in the conversation. The German page for OpenAI Sprachausgabe carries the sources with their retrieval dates.
Is OpenAI Sprachausgabe the right fit?
We go through your tasks and the route that carries them - and say plainly where it does not.
Arrange a conversation