Trust Center
Security & availability
Encryption in transit and at rest, identity and access management, network and API security, multi-zone availability and continuity plans: what Univerx is designed for so your customer service keeps running.
At a glance
- Designed for
The platform is built toward the requirement. Evidence such as an attestation does not exist yet – we name it as soon as it does.
- On request
The documents exist. You receive them for your review through the contact form.
- Available
Met and evidenced. We assign this level only once the evidence exists.
- Technical and organisational measuresOn request
#Security as part of the architecture
A contact centre connects telephony, messaging, AI and your business systems. Every one of those connections is a potential point of attack. So Univerx treats security not as an add-on but as a property of the cloud architecture.
The platform is multi-tenant, with your data kept separate from other customers' data. Updates roll out continuously, without upgrade projects. Security fixes therefore reach every tenant without you having to start a project.
#Four layers of protection
| Layer | What it protects | How |
|---|---|---|
| Data | Conversations, recordings, cases | Encryption in transit and at rest |
| Identity | Access for employees and administrators | Role rights, logging, central administration |
| Network and interfaces | Connections to telephony, CRM and AI | Network security, secured APIs and integrations |
| Operations | The running service | Multi-zone availability, continuity plans, monitoring |

#Identity and access
You decide who sees what in central administration: per role, per data type, per feature. A typical set-up: team leads see their team's analytics, administrators see the configuration but no conversation content.
During co-browse the platform masks sensitive fields such as account numbers or health details. The agent guides the customer through the form without seeing what is typed.
Interfaces to your business systems run through the developer platform. Roles and logs apply there too, designed so that every integration gets only the rights it needs.
#Availability and continuity
Customer service matters most when something else has failed. Univerx is designed for multi-zone operation: services run independently in several zones of a region, so the loss of one zone does not interrupt the service.
For larger events there are continuity plans. A public status page is planned so you can see the state of the services at any time. More under Resilience.
#What you set yourself
Security is a shared responsibility. Univerx runs the platform; you define roles, rights, retention periods and integrations. The main settings on your side:
Your settings
#Evidence
The technical and organisational measures are available on request. Univerx is designed for the BSI C5 criteria catalogue; we will name an attestation only once it exists.
For regulated companies, the NIS2 and DORA pages describe which documents Univerx contributes. The product page Security gives an overview of the features.
Products
Where the topic applies.
The product families this topic matters most for.
Univerx Cloud
One cloud for every customer contact.
- EU
- BSI C5
- NIS2
Univerx Trust Center
Security and regulation as a design principle, not an appendix.
- DSGVO
- EU
- AI Act
- BSI C5
- eIDAS
- NIS2
- DORA
- BFSG
Univerx Marketplace & Developer
Open to your system landscape, never an island.
- DSGVO
- NIS2
Trust & Europe
Every topic in the trust center.
Every topic carries a status. It tells you what is a design goal, which documents you can request and what is evidenced today.
| Topic | Status |
|---|---|
| GDPR | On request |
| Data residency & hosting in Germany | Designed for · German hosting planned |
| EU AI Act | Designed for |
| BSI C5 | Designed for · goal, no attestation |
| eIDAS & online ID | Designed for |
| NIS2 | Designed for |
| DORA | Designed for |
| European Accessibility Act | Designed for · WCAG 2.1 AA as a goal |
| Responsible AI | Designed for · principles & controls |
| Security & availability | Designed for |
| United States: HIPAA, PCI DSS, SOC 2, TCPA, CCPA | Designed for |
Frequently asked questions
What availability do you commit to?
Availability is committed in the contract. The figure is in your contract's service description rather than on this page, because that is the only place it binds.
Is there a status page?
A public status page is planned. It shows the state of the services and any ongoing incidents. We share the address with the contract.
Who at Univerx can access our data?
Only people who need it to run the service, with a role and a log. Support access follows the data processing agreement; the details are in the technical and organisational measures.
What happens if a zone fails?
The platform is designed for multi-zone operation: if one zone fails, the others take over. For larger events there are continuity plans.
See Univerx on your own example.
In a demo we show the platform along your channels and requests, from AI agents to video, workforce scheduling and analytics.
Online, in German or English, with no preparation on your side.














