EU-sovereign AI platform.
Full EU stack from the first call.
US AI platforms promise 'EU region' but hosting runs on US corporations with Cloud Act exposure. You need real EU sovereignty, no US subsidiary with EU wrapper.
Regulatory requirements for AI processing in the EU are growing rapidly. Schrems II ruling 2020 + DPF (Adequacy Decision July 2023, confirmed by General Court September 2025) + Schrems-III action pending — third-country transfer requirements remain politically volatile. EU AI Regulation 2024/1689 will be sharply enforced from 02 August 2026 with Article 50 (transparency obligation). In parallel comes the data sovereignty discourse: 'EU region' at US cloud providers doesn't solve Cloud Act risk, the parent corporations are US subjects, jurisdiction follows US law. Real EU sovereign AI means: EU company as provider, EU hosting infrastructure, EU LLM processing, full GDPR Art. 28 DPA with transparent subprocessor list. Rinqo meets these requirements from day one, not as retrofitted setup but as architecture default.
Rinqo is the EU-sovereign AI workforce platform for European SMBs: full EU stack (Hetzner Falkenstein/Nuremberg + Microsoft Azure OpenAI (Microsoft Ireland, Sweden Central)), AI Act Art. 50 by default, automatic DPA without US clauses, 7 DACH industry templates, workforce OS with 17+ roles roadmap.
Try EU-sovereign platformWarum Rinqo?
EU hosting on Hetzner Germany
Falkenstein and Nuremberg, German company, German DPA without third-country transfer. No Cloud Act exposure.
EU LLM stack without US components
Microsoft Azure OpenAI (Sweden Central) as primary LLM, optional failover to OVHcloud (opt-in Pure-EU failover). Complete processing in the EU.
Schrems II compliant
No personal data leaves the EU. Not for model training, not for logging, not for telemetry.
AI Act Art. 50 by default
AI disclosure default-active in phone, chat and email. Compliance is architecture default, not configuration effort.
DPA automatic at contract signing
Full DPA per GDPR Art. 28, without US clauses, without negotiation effort. With US providers typically only via sales contact.
Transparent stack
All components (hosting, LLM, voice engine, vector DB, queue) are documented with provider, region, DPA status. Full sovereignty auditability.
Vorher. Nachher.
US AI platforms with 'EU region': US corporation as parent, Cloud Act exposure, DPA with third-country clauses, AI Act implementation with the buyer.
Rinqo: full EU stack (Hetzner DE + Microsoft Azure OpenAI (Microsoft Ireland, Sweden Central)), DPA with transparent subprocessor list on /security (US parent companies openly disclosed), AI Act default, full EU data residency for all voice/chat/email streams with full auditability.
What 'EU sovereign' really means
EU sovereign AI is more than 'EU region' at US cloud providers. Real EU sovereignty requires four layers: first EU company as provider (legal entity under EU law, not US subsidiary); second EU hosting infrastructure (servers in EU member state, not US cloud region); third EU LLM processing (inference on EU servers, no US hyperscaler); fourth DPA without third-country clauses (full GDPR Art. 28, no US sub-processors). With US hyperscalers point one is already problematic, parent corporations are US subjects, jurisdiction follows US law (Cloud Act 2018). 'EU region' just shifts the server location, not legal sovereignty.
Schrems II + GDPR Art. 28, the legal reality 2026
The Schrems II ruling of the European Court of Justice 2020 classified US third-country transfers of personal data as fundamentally problematic. EDPB clarifications 2024 tightened: additional safeguards (TIA, encryption, sub-processor audits) are mandatory, US cloud providers with US parent must be individually justified. For practices, law firms, banks and all SMBs with personal data in AI workflows this becomes the regulatory breaking point from 2026. EU-sovereign stack avoids the problem from the start, no third-country transfers, no TIA declaration, no US cloud audit needed.
AI Act Art. 50, transparency obligation from 02 August 2026
Article 50 of the EU AI Regulation 2024/1689 obliges providers from 02 August 2026 to disclose AI interactions with end customers. Concretely: AI calls must be marked as AI in opening sentence, AI chats need visible disclosure banner, AI emails standard note. Violations can incur fines up to €15 million or 3% of global annual turnover. With US providers compliance implementation sits with the buyer, they must build the disclosure note into every workflow. Rinqo does this automatically in all channels.
Rinqo's full EU stack in detail
Hosting: Hetzner Online GmbH, Falkenstein and Nuremberg, German DPA per GDPR Art. 28. App + API + database + vector DB + queue + voice service all on Hetzner hardware. Voice pipeline: Pipecat (Apache 2.0) on Hetzner Coolify, telephony via EU data centres (Dublin and Frankfurt). LLM: Microsoft Azure OpenAI (Microsoft Ireland, Sweden Central) (primary) on Equinix infrastructure Finland, OVHcloud Roubaix as opt-in Pure-EU failover (sub-processor only once API key is set). STT: speech recognition in an EU setup with a DPA; self-hosted Whisper on Hetzner GPU can be connected on request. TTS: a German speech synthesis provider, hosted in the EU, connected via API. No US hyperscalers in the primary processing pipeline.
When EU sovereign is mandatory, and when not
Mandatory: practices with patient data, law firms with client conversations, banks/insurance with financial data, all industries with professional secrecy (tax consulting, notary, healing professions), public administration. Strongly recommended: all DACH SMBs with employee data in AI workflows. Optional: purely product-related applications without personal data (e.g. anonymous FAQ bots on marketing pages). Anyone not clearly serving this filter risks tightened audit requirements from 2026, BfDI complaints and fines under EU AI Act and GDPR.
Frequently Asked Questions
Sources
- EU AI Regulation 2024/1689, Art. 50
- ECJ ruling C-311/18 (Cloud Act exposure)
- EDPB Statement on Schrems II (2024)
- GDPR Art. 28 (Processor)
Last updated: 2026-05-08
Founder & CEO, Rinqo
Sven builds Rinqo from a simple observation: most AI tools are designed in San Francisco and sold in Berlin. The workshop in the Black Forest, the veterinary practice in Salzburg, the family hotel in Tyrol get software that doesn't speak their language. Rinqo flips that. On European servers, set up in ten minutes, in twenty languages. With templates built by the industries themselves.
Last updated:
Try it live
View agent