Univerx Trust Center
Europe & regulation
The Univerx Europe layer: GDPR, EU data residency, the EU AI Act, BSI C5, eIDAS, NIS2, DORA and the Accessibility Act. For each framework the honest status, what “designed for” means and which documents exist.

Building blocks
Europe & regulation in detail.
The building blocks at a glance – all in the same workspace and under the same administration.
One layer, every family
The Europe layer runs beneath every family; each page shows the frameworks that matter there.
Honest status
“Designed for”, “on request” or “available”, never more than the evidence supports.
Sources linked
Each framework links to the original text on EUR-Lex, gesetze-im-internet.de or the BSI.
Documents on request
For procurement, privacy and supervisors we provide documents per framework.
#One layer beneath every family
European rules do not affect one product but all of them. The GDPR applies to every recording, the EU AI Act to every AI agent, the Accessibility Act to every customer interface.
So Univerx treats regulation as a layer running beneath every family, not as an add-on product.
On each family page, small markers show which frameworks matter most there. This page brings them all together, with status and source.

#The status per framework
| Framework | What it covers | Status at Univerx | More |
|---|---|---|---|
| GDPR | Data processing, impact assessment, erasure | Documents on request | GDPR |
| EU data residency | Data and media in EU regions | Designed for; hosting in Germany planned | Data residency |
| EU AI Act | Disclosure, oversight, logging | Designed for | EU AI Act |
| BSI C5 | German criteria catalogue for cloud security | Designed for; no attestation claimed | BSI C5 |
| eIDAS | Online ID, electronic signatures | Designed for, in the Univerx Channel | eIDAS |
| NIS2 | Cybersecurity, supply chain, reporting | Designed for | NIS2 |
| DORA | Digital resilience in finance | Designed for | DORA |
| EAA | Accessible customer interfaces | Designed for WCAG 2.1 AA, EN 301 549 | EAA |
#Three levels, clearly separated
Designed for. The platform is built for the requirement. We can show how, but independent evidence is pending.
On request. Documents exist and are handed to prospects and customers, such as the data processing agreement.
Available. Evidence exists, with type, date and scope. We use this level only when it applies.
#German specifics
Beyond the European frameworks, further rules matter for customer service in Germany: co-determination over analytics under § 87(1) no. 6 BetrVG, consent to marketing calls under § 7 UWG, and the confidentiality of the spoken word for recordings (§ 201 StGB).
How Univerx is configured for them is shown by Univerx Workforce and Univerx Outbound. Our guide Running a contact centre in Europe offers an overview for procurement and privacy.
Univerx Trust Center
Security and regulation as a design principle, not an appendix.
Security, privacy, resilience and responsible AI as a family of its own, plus the Europe layer from GDPR to the Accessibility Act. With settings you make yourself and documents on request.
Security
Encryption in transit and at rest, identity and access control, network and API security and secure operations. What the platform brings, and what you set yourself in administration.
- DSGVO
- BSI C5
- NIS2
Privacy
Your data stays your data: region choice within the EU, a sub-processor list, deletion and export, role-based rights and a data processing agreement under Art. 28 GDPR on request.
- DSGVO
- EU
Resilience
Multi-zone availability, independent services, continuity plans and a planned status page: Univerx is designed to keep your customer service running when part of the infrastructure fails.
- NIS2
- DORA
- EU
Responsible AI
Transparency, human oversight, fairness, privacy and governance for every AI module in Univerx: AI agents, Univerx Assist, conversation analytics, knowledge and Semantic². Principles that work as settings.
- AI Act
- DSGVO
Frequently asked questions
What does “designed for” mean?
The platform is built for the requirement and we can describe how. Independent evidence, however, is not yet in place. Once it is, we change the status and state its type, date and scope.
Why are there no seals on the website?
Because a seal without evidence would be a claim. We show statuses, sources and documents. That is less eye-catching, but it can be checked.
Which frameworks apply to us?
That depends on your industry, size and use. The industry pages show which frameworks typically matter; the binding assessment remains with your legal team.
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.



















