Data Residency

Data residency is only available for the Falcon 2 TTS model.

Regional vs Global: which should you use?

Regional endpoints (strict control—recommended for residency)

• By default, all customer account data (including user profiles, usage, and billing information) is hosted in the United States. However, with data residency enabled, text input, audio synthesis, and processing will be confined to the selected regional environment.
• Ideal for regulated workloads and contractual residency requirements.
  
  Murf offers data residency for Falcon 2 TTS in 11 regional environments:
  
  
  

Global router (latency-first - not for strict residency)

• https://global.api.murf.ai/v1/speech/stream automatically routes requests to an available, geographically close Falcon region for performance and availability.
• Because routing can select any available region, do not use the global URL if you require strict residency.
  

Data Processing

With Murf’s isolated Falcon 2 TTS environments:

• Text and audio data remain confined to the selected region for processing.
• Customer account and billing data are centralized in the United States.
• Network routing ensures requests to regional URLs stay within that jurisdiction.
• Encryption in transit is maintained globally via HTTPS.

Compliance & Security

Data residency environments extend Murf’s core security and compliance framework, including:

• GDPR Readiness: Murf’s processing framework aligns with GDPR’s regional data processing requirements.

• SOC 2 Compliance: Murf follows strict standards for data confidentiality, availability, and integrity.

• Encryption at Rest & In Transit: All content is encrypted using industry-standard AES-256 and TLS 1.2+.

• Region-Specific Isolation: Enterprise accounts can restrict Falcon 2 TTS processing to a specific jurisdiction.