It comes down to the whole chain, from the language model to the server: where each link runs, and what stays behind after the conversation. That may sound like a matter for the lawyers. Yet it's often the very first thing a data protection officer asks about, the moment an AI tool lands on the table.
Picture an information security officer at a local authority who has to approve an AI notetaker for the executive board's meetings. She reads the privacy page, sees "data stored in a European region" and ticks the box.
A week later the data protection officer starts asking questions. The data centre really is in Europe, but the parent company is in the United States. And that puts the entire service under American law, however European the server may be.
To see how that happens, it helps to take an AI service apart for a moment.
What does keeping your data out of the US actually mean?
Keeping your data out of the US means your conversation leaves Europe at no step at all: not at the language model, not at the speech-to-text and not in storage, and that nothing of it stays with the provider afterwards. That's because an AI service isn't one thing but a stack of layers. Only once you look at them separately do you see where things go wrong.
- The language modelThe model that writes the summary. Often from OpenAI, Microsoft or Google; sometimes the provider's own model.
- The speech-to-textThe step that turns the conversation into words. It runs somewhere too, and it belongs to someone.
- The cloudThe servers everything runs on, and where the data sits.
- The companyThe owner of the service, and the country it answers to. That jurisdiction decides who can legally reach your data.
Most AI tools have an American party on at least one of those layers: the model comes from OpenAI, the cloud belongs to Amazon or Microsoft, or the company itself is American. So ask, layer by layer, where it runs and what stays with the provider after the conversation. And ask whether your conversations are used for training.
Sovereign AI, European AI, AI without an American cloud, AI without Big Tech: they're different words for the same question. Where is your conversation processed, and what's left of it afterwards?
At Notuly your conversation is processed in Europe, and our own models on servers in Amsterdam create the report. Once the report has been sent, nothing stays behind at Notuly.
What is the CLOUD Act, and does it reach EU data?
The CLOUD Act (in full: the Clarifying Lawful Overseas Use of Data Act) is a US law that obliges American providers to hand data over to the US government, even when that data sits in Europe. That last part is the whole point.
An American company falls under American law even when its servers are in Frankfurt or Amsterdam. The Dutch National Cyber Security Centre (NCSC) wrote in 2022 that the chance of the US actually invoking the CLOUD Act against European customers is small. But small isn't zero, and the provider can't rule it out (see the sources at the bottom).
That became concrete on 18 June 2025, when an inquiry committee of the French Senate held a hearing. There Anton Carniaux, director of public and legal affairs at Microsoft France, was asked whether he could guarantee under oath that French customers' data would never go to the US government without consent.
"No, I cannot guarantee that, but, again, it has never happened before."
The quote is translated from the French, and it has indeed never happened, as Microsoft itself points out. But the provider can't guarantee it, and that's what it comes down to: the law of the home country comes first.
So what can be demanded under that law depends on the company and its partners, and on what stays with them, not on the server. That's why the last part is what counts at Notuly: once the report has been sent, nothing stays behind, and the report sits in your own inbox.
How to check a tool for this yourself is covered on our security page. Here we're after the why, and the why starts with a misunderstanding about the server.
Is an EU cloud or an EU data centre enough?
No, not automatically. An EU data centre determines where your data physically sits. It doesn't determine which law applies to the company that can reach it.
That difference is often glossed over. An American provider puts a data centre in Europe, sticks an EU flag and a certificate on it, and calls it sovereign. In practice that's known as sovereignty-washing: it looks European, but the parent company, and with it the ultimate say, stays American.
And the odds of running into such a set-up are high: American hyperscalers hold around 70% of the European cloud market (Synergy Research Group, 2025).
"Our data sits in Europe" and "our data falls under European law" are therefore two different promises: the first is about a place, the second about control. So for a confidential conversation you want to know more than the place: where it's processed, whether anything is trained on it, and what stays with the provider after the report.
At Notuly the data centre is therefore just one layer, and on top of it the whole AI step runs on our own models. We work in line with ISO standards. Our data servers run in an ISO 27001-certified data centre in Amsterdam.
Where your conversation really goes.
The easiest way to see this is to lay two routes side by side. Not as a checklist, but as the journey your conversation makes from the moment someone starts the recording.
Route A: the usual route, with storage at the provider
- Your conversation. Someone starts the recording.
- Processing wherever the model runs. The tool sends the audio or the text to a model from OpenAI, Microsoft or Google, and that model doesn't always run in Europe.
- Storage at the provider. The recording, transcript and report stay in an account, often on an American cloud, sometimes in an EU region.
- Under the CLOUD Act. Whatever stays with an American provider falls under American law, wherever it sits.
- With free consumer AI, often: training. Your input helps improve the model.
Route B: the route that stays in the EU
- Your conversation. Someone starts the recording.
- Processed in Europe. Our own, self-hosted models in Amsterdam create the report.
- The report in everyone's inbox. With the summary, the decisions and the action points, and the full transcript as an attachment, unless you switch it off.
- Audio deleted within a minute of processing. The report sits in your own inbox.
- No training. Your conversations are not used as training data, and your data never leaves the EU.
The difference between the two routes isn't "better encryption", because both can be strongly secured. It lies in what happens to your conversation: where it's processed and what stays with the provider afterwards. Which is why an EU flag on a website proves nothing on its own.
Notuly follows route B: the report is in everyone's inbox within ten minutes, and once it has been sent, nothing stays behind at Notuly.
When data going to the US is perfectly fine.
For a great deal of work an American AI tool is a perfectly good choice, and we're honest about that. Those tools are technically strong, well secured and connect to everything you already use. For a brainstorm, a public presentation or an internal note without sensitive content, where the model comes from is rarely a problem.
It bites in two places. Confidential conversations: a customer, someone in your care, a case file, an executive board meeting, or a lawyer bound by confidentiality. And organisations with hard requirements around sovereignty or the GDPR.
If you run conversations through a general chatbot rather than a notetaking tool, first read whether ChatGPT is GDPR compliant.
A European stack of your own has downsides too: fewer integrations, no worldwide ecosystem of plugins, a smaller company behind it. This isn't a story of good against evil. It's a choice that depends on what gets said in the conversation.
With a confidential conversation like that, the choice weighs heavily. That's where you want the report without your data leaving the EU. That's what Notuly delivers.