Your data stays in Europe
AI-Flow runs in the European Union. We host the application in Heroku's EU region and store your data in MongoDB Atlas clusters in Europe. Traffic reaches us through Cloudflare, which terminates TLS and filters malicious requests before anything touches the app. Running AI-Flow does not require your data to leave the EU.
We built it this way on purpose. A European company that answers to the GDPR should not have to send its documents and its employees' questions to a US platform and hope for the best. So we didn't build it that way.
Your model, your keys
AI-Flow runs on your own LLM API keys. You choose the model provider, and inference runs against that provider with your key, so you decide where your prompts go and under whose contract. Your keys sit in an encrypted vault and are never passed into a model's context window. Because you hold the key and the provider relationship, AI-Flow is not a middleman for your model calls.
How we protect your data
Everything moves over encrypted connections. Cloudflare and the app enforce HTTPS, so data in transit is encrypted end to end. MongoDB Atlas encrypts your data at rest on its EU clusters, and automated encrypted backups run on the same platform.
Each customer organisation's data is separated by organisation-scoped access control. Every record belongs to an organisation, queries are scoped to that organisation, and one customer cannot reach another customer's data through the application. Inside your organisation, role-based access control decides who sees which knowledge bases and which agents. A full audit trail records every agent action, so you can see who did what. Every answer an agent gives cites the source it came from, and the full trace of a run stays available, so you can check exactly how an answer was produced rather than trust a black box.
Sign-in
You sign in to AI-Flow with Microsoft Entra ID, and the platform also supports SSO/SAML. Authentication happens against your identity provider, so your password never reaches us and you keep your own tenant's sign-in policy, including multi-factor authentication if you enforce it.
The infrastructure we build on
We don't run our own data centres, and that's the point. We build on providers audited far more rigorously than any company our size could audit itself, and your data inherits their physical and platform security.
Heroku (our application host) holds ISO 27001, ISO 27017, ISO 27019, SOC 1, SOC 2, SOC 3 and PCI-DSS. MongoDB Atlas (our database) holds SOC 2 Type II and ISO 27001. Cloudflare (our network edge) holds SOC 2 Type II, ISO 27001 and ISO 27701. Each is renewed on the provider's own audit cycle.
AI-Flow itself is not yet independently certified, and we won't pretend otherwise. What we can say is that AI-Flow runs on ISO 27001 and SOC 2 certified infrastructure, and that we're working toward our own attestations.
The GDPR
Fundation GmbH is the data processor for what you put into AI-Flow, and you remain the controller. We sign a Data Processing Agreement (Auftragsverarbeitungsvertrag) with customers, available on request at [email protected], list our subprocessors openly, and only use subprocessors that offer EU data processing and Standard Contractual Clauses where a transfer could occur. Our Impressum, Terms of Service and Privacy Policy are published at ai-flow.eu/impressum, ai-flow.eu/termsofservice and ai-flow.eu/privacypolicy.
When a subscription ends, we delete the organisation's data within 30 days.
Subprocessors
We keep a current list of every company that processes customer data on our behalf, what they do, and where, at ai-flow.eu/subprocessors.
Reporting a security issue
If you find a vulnerability or have a security concern, write to [email protected]. We read every report, we respond, and we don't take legal action against researchers who report in good faith and give us reasonable time to fix the problem. Our disclosure details are also published at /.well-known/security.txt.
Last reviewed: 14 September 2026. Fundation GmbH, Köln.
