How do you comply with GDPR and the EU AI Act - and what role do we vs. you take on?+
Typically you are the deployer of the AI system, and we act as data processor and provider of the underlying components. The role split under the EU AI Act and GDPR is fixed contractually: data processing agreement under Art. 28 GDPR, technical documentation aligned with Annex XII of the AI Act, transparent list of all sub-processors. Our RAG architecture follows the German DSK guidance on RAG from October 2025.
Where is our data processed and which models do you use?+
Hosting in your own Azure, AWS, or GCP tenancy in an EU region, or fully on-premise. We are model-agnostic and choose per use case between OpenAI, Anthropic, Mistral, Llama, or custom fine-tunes - swapping models after go-live is a configuration change, not a re-implementation project. Your data does not flow back into model providers' training sets, secured both contractually and technically.
How do you prevent hallucinations - and how do we know the system actually works?+
Every answer is traced back to concrete sources; without sufficient evidence the system refuses to answer rather than guess. Before every release, an automated evaluation suite runs against a golden dataset of your real questions - measuring faithfulness, citation accuracy, answer relevance, and more. In production we continuously monitor the same metrics, plus drift in the data base and user behavior.
How does the system integrate with M365, SharePoint, Confluence, SAP - and are permissions respected?+
Standard connectors for Microsoft Graph, SharePoint, Confluence, SAP, and common databases; anything else we wire up via REST or SQL. Permissions are checked against the source system at query time - users only see content they would have access to in the original system. Changes to the data base flow into the index via delta sync or webhook.
Who owns the code, index, and models - and who runs the system after go-live?+
Source code, configuration, index, and fine-tunes belong to you. For operations there are three models: we keep running the system (managed), we hand it over to your internal IT, or to a third-party operator of your choice. Handover includes runbook, architecture documentation, and the eval suite - whoever runs the system in future can also prove its quality.