AI & data · updated 27 September 2026
How we handle AI and your data.
We build AI that works inside your business, so you should know how it treats your data. In short: it runs in your accounts, a person approves before anything goes live, and we put it in a signed agreement.
In short
- 01People know it's AIAgents say they are AI, and generated media is marked, as the EU AI Act requires.
- 02Your data, your accountsWe build in your cloud, database and ad accounts. You keep the code.
- 03A person approvesNothing goes live until the tests pass and a person signs off.
- 04Every service namedEach outside service that processes data is listed, here and in your agreement.
- 05DPA on requestA data processing agreement, signed before we process personal data for you.
How we use AI
We use AI in two places. In what we build for you: agents, data products and generative marketing. And in our own work, where agentic coding helps us build faster. In both, AI drafts and a person stays responsible for the result.
When you contact us, a person reads and answers. There is no chatbot on this site.
The EU AI Act, Article 50
The AI Act's transparency rules apply from 2 August 2026. In what we build for you, that means:
- Agents and assistants that talk to people say they are AI, unless that is obvious.
- Systems that generate text, images, audio or video mark their output as AI-generated in a machine-readable way, where the Act requires it.
- Realistic images, video or audio of people, places or events are labelled as AI-generated when you publish them. We raise this in every generative marketing project.
The full text: Regulation (EU) 2024/1689. This page explains how we work; it is not legal advice.
Your data stays in your accounts
Wherever we can, we build in your own cloud, database, AI model and ad accounts. They are yours, and you can take back the access you give us at any time.
- You keep the code and the data. Nothing is locked in with us.
- If something has to run on our side, we tell you what, where and why before we use it, and it goes in your agreement.
- We keep personal data to what the workflow needs.
A person approves before anything goes live
- 01Agent evals passed
- 02UI and API tests passed
- 03A person approves
- 04Live in production
Every release passes the same gate: agent evals, UI and API tests, then a person approves it. Only then does it go live.
In production, agents propose and a person approves anything that matters. You decide what that includes, and we build the approval step into the workflow. We review it with you every week.
Who processes data
On this website
| Service | What it does | When |
|---|---|---|
| Vercel | Hosting, cookieless site statistics and speed measurement | Every visit. Server functions run in Frankfurt. |
| Google Workspace | Our email: booking confirmations and replies | When you book a demo or send us a message |
| Our database | Stores demo bookings and messages | When you book a demo or send us a message |
| Google Tag Manager, Analytics and Ads | Site analytics and ad measurement | Only after you accept cookies |
| Chat with us | Only if you choose to chat there |
Transfers outside the EU rely on the EU-US Data Privacy Framework or standard contractual clauses. More in our privacy statement.
In your project
Each project uses its own services, such as your cloud, your database and the AI model providers the workflow needs. We list each one in your agreement with what it processes and where. You approve them before we start, and we tell you before anything changes.
Data processing agreement (verwerkersovereenkomst)
When we process personal data for you, the GDPR (AVG) requires an agreement that sets out what we process, why, how it is secured and which services help us. Ask for ours at any time; we sign it with you before we process any personal data.
Certifications
We work in line with the GDPR (AVG). We are not SOC 2 certified yet: we are putting the controls in place and will update this page when that changes.