At LiveHub, we take significant measures to stay up to date with the latest security and privacy protocols. Here are a few helpful links to explore our privacy policies and procedures.
Live Hub Terms of condition
Live Hub privacy policy
Live Hub GDPR compliance
Live Hub Servers locations:
EMEA - Germany
USA - East
Asia - Singapore
In addition note that you can define your own Cookie consent by CookieHub preferences on LH platform as shown below on the main LH screen:
Additional supporting documents:
The information related to AI services is sourced from the respective service providers' privacy documentation. For full information, please refer to:
Additional privacy-relevant data:
How Are the SBCs Secured?
Session Border Controllers (SBCs) in the Live Hub environment are secured using a layered security approach that includes:
VoIP Protocol Security: SBCs are configured to use secure VoIP protocols such as SIP over TLS and Secure RTP (SRTP) for Media.
Management Security: Secure protocols are enforced for management interfaces, and access is restricted to authorized personnel only. Access to the provisioning of the SBCs is roll based controlled.
Encryption:
In Transit: TLS 1.2/1.3 is used for signalling and HTTPS for external service connections (e.g., STT, TTS, LLMs).
At Rest: AES-256 encryption is applied to all stored data.
Firewall and WAF: The infrastructure includes firewall protections and Web Application Firewalls (e.g., Imperva) to mitigate external threats
Where Are the SBCs Hosted, Who Is Responsible, and What Data Is Collected?
Live Hub SBCs are hosted on Audiocodes' Azure infrastructure and deployed across multiple Azure regions -
Key configuration, recording, billing, and call history data are maintained in Germany West Central.
SIP call handling, voice traffic, bots, speech-to-text (STT), and text-to-speech (TTS) services can be deployed in Germany West Central, Southeast Asia, or East US 2, based on customer preferences.
Collected Data
Types of data collected is described in the following document : GDPR Notice for AudioCodes Live Hub
Processing and retention of customers data is described by Live Hub’s Privacy Policy
Data protection by Live Hub AI services (translations, TTS, STT, etc.)
The following provides information about the privacy practices of the AI services we use, ensuring that your data remains protected.
Live Hub is using the following AI services:
Azure Translation - Microsoft guarantees that "There will be no record of the submitted text or voice, or any portion thereof, in any Microsoft data center. The audio and text will not be used for training purposes either."
Open.AI, provided by Azure - According to the Azure OpenAI Service data privacy documentation, the data you submit "...are NOT used to train, retrain, or improve Azure OpenAI Service foundation models."
Claude, provided by AWS - As per the Amazon Bedrock documentation, "Amazon Bedrock doesn't store or log your prompts and completions. Amazon Bedrock doesn't use your prompts and completions to train any AWS models and doesn't distribute them to third parties."
What Security Controls and Measures Are in Place?
Compliance and Certifications:
AudioCodes hold ISO 27001:2022 , ISO 27032:2023 , and SOC 2 Type II
Infrastructure Security:
Logical data isolation using schema-based multitenancy database
Role-based access control (RBAC), domain login, and admin credentials stored in Azure Key Vault
Encryption:
In Transit: TLS 1.2/1.3 is used for signalling and HTTPS for external service connections (e.g., STT, TTS, LLMs).
At Rest: AES-256 encryption is applied to all stored data.
Firewall and WAF: The infrastructure includes firewall protections and Web Application Firewalls (e.g., Imperva)
Operational Safeguards:
Cluster-based resource pooling redirects new calls to available resources in case of a component failure.
Live Hub uses multiple Azure Availability Zones (AZs) for redundancy in data storage and service resilience.
Let us know if you have any questions!
Thank you,
The LiveHub Team. 🙏