Data processing locations
All streaming audio and transcription data is processed in AWS regions located in the United States and the European Union: US
EU
Which of these locations processes your data depends on the endpoint you connect to, as described below.
Edge Routing
The default endpoint automatically routes requests to the nearest available region, minimizing latency for real-time transcription. Your data may be processed in any of the US or EU locations listed above. With infrastructure distributed across the US and EU, this endpoint delivers best-in-class streaming performance regardless of where your users are located.Data Zone Routing
Data Zone endpoints guarantee your data never leaves the specified region. This is designed for organizations with strict data residency and governance requirements. Your audio and transcription data is processed exclusively in that zone’s locations listed above and remains entirely within the US or EU, respectively.Which endpoint should I use?
- Optimizing for latency? Use Edge Routing (default). No configuration change is needed, as it automatically routes to the nearest region for the fastest response.
- Need data residency? Use a Data Zone endpoint. Choose US or EU to ensure your audio and transcription data stays within that region.
How to use it
Edge Routing is the default. If you’re using the SDKs without overriding the base URL, you’re already using this endpoint and no configuration change is required. To use a Data Zone endpoint, set the endpoint URL when you connect. The examples below use the US Data Zone endpoint. For the EU Data Zone, replaceus with eu.
- Python SDK
- Python
- Javascript
- JavaScript SDK