How does an AI meeting bot join a Microsoft Teams call?

The bot joins the Teams meeting as a participant, the same way a colleague would from a meeting link. It appears in the participant list, captures the meeting audio, and streams it to the transcription pipeline. Because it joins as a visible participant rather than hiding in the background, everyone in the call can see that it is present, which supports consent and transparency.

Can a Teams meeting bot keep data in the EU?

Yes, if the bot's pipeline is built that way. Microsoft Teams itself is a US-headquartered platform, but the meeting assistant that joins your call is a separate system. Numi's bot streams audio to an EU-only pipeline where transcription and analysis run on EU infrastructure, so the assistant does not add a US processor to the path even though the conferencing platform is American.

What does without US processors actually mean here?

It means the meeting assistant's own data path, capturing audio, transcribing it, storing it, and analysing it, runs on EU infrastructure with no third-party US processor in that chain. Numi self-hosts transcription in Frankfurt and does not send audio to a US transcription API. It is a statement about Numi's pipeline, not a claim about Microsoft Teams, which remains a US platform you have chosen separately.

Is an AI Teams bot GDPR-compliant?

GDPR compliance depends on lawful basis, transparency, and where the data is processed, not on the tool alone. An EU-resident meeting bot removes the international-transfer problem for the assistant's own processing and makes consent easier because the bot is a visible participant. You still need a lawful basis, participant notice, and an Article 28 data processing agreement, which an EU provider should supply.

An AI Meeting Bot for Microsoft Teams Without US Processors

If your team runs on Microsoft Teams and you want an AI assistant in those calls, the usual options come with a catch: the assistant sends your meeting audio to the US to be transcribed and analysed. You can have the notes, but the conversation leaves the EU to produce them. For a European sales team, a compliance-minded RevOps function, or anyone under a strict data-residency policy, that trade is the whole problem.

It does not have to be that way. A meeting bot can join a Teams call and keep its own data path entirely inside the EU. Here is how that works, and what "without US processors" honestly means when the conferencing platform itself is American.

How an AI bot joins a Teams meeting

A meeting bot joins your Teams call as a participant, the same way a colleague joins from a calendar invite or a meeting link. It shows up in the participant list with a name you can recognise. Once it is in, it captures the meeting audio and streams it to the assistant's transcription pipeline, where it becomes a transcript and, from there, coaching, scorecards, and call analytics.

The important part is that the bot is a visible participant, not a hidden tap. Everyone in the meeting can see it is there. That visibility is not a cosmetic detail; it is what makes consent and transparency workable, because participants can be told, and can see, that the call is being captured.

Definition

An AI meeting bot is a participant that joins your video call to capture its audio for transcription and analysis. It appears in the participant list like any attendee. Whether it is sovereign depends not on the conferencing platform but on where the bot sends the audio it captures.

The platform is American. The assistant does not have to be.

Here is the distinction that gets muddled. Microsoft Teams is a US-headquartered platform, and your choice to run on Teams is a separate decision with its own data-governance profile. The AI meeting assistant that joins the call is a different system with its own data path. Those two things are not the same, and conflating them is how teams end up assuming that using Teams means every tool touching a Teams call must also run through US infrastructure.

It does not. The assistant controls where the captured audio goes after it leaves the meeting. A well-built EU assistant streams that audio to an EU-only pipeline, transcribes it on EU servers, and stores and analyses it in the EU. The conferencing layer being American does not force the assistant to add a US processor of its own.

What "without US processors" actually claims

Precision matters here, because it is easy to overclaim. "Without US processors" is a statement about the meeting assistant's own data path, capturing the audio, transcribing it, storing it, and analysing it. In Numi's case that chain runs on EU infrastructure with no third-party US processor in it. Transcription is self-hosted in Frankfurt, so the audio is not shipped to a US transcription API, and nothing about your meetings is used to train a model.

What it does not claim is that Microsoft Teams is a European product. It is not. If your requirement extends to the conferencing platform itself, that is a separate procurement question about Microsoft. What an EU meeting assistant removes is the second transfer, the one most notetakers quietly add on top of Teams by sending your audio onward to US systems for processing.

The honest version

Sovereignty is about control, not origin. Numi does not control which conferencing platform you use, and Teams is American. Numi does control its own pipeline, and that pipeline keeps your meeting audio in the EU with no US processor in the transcription, storage, or analysis path.

Why EU teams ask for this

The demand is not abstract. A German sales org with a works council, a financial-services team under sector rules, a public-sector supplier with residency clauses in its contracts, all of them face the same question from procurement and legal: where does the recording go? "To a US notetaker under Standard Contractual Clauses" is an answer that invites a transfer impact assessment and a long conversation. "It stays in the EU" ends the conversation.

This is the same reasoning we walk through for consent under German law in our piece on AI notetaker consent, §201 StGB, and the Betriebsrat, and it is why residency, not just contractual protection, is what compliance-conscious buyers keep coming back to.

How Numi does it on Teams

Numi's meeting bot joins Microsoft Teams calls as a participant, captures the audio, and streams it to an EU-only pipeline. Transcription runs on self-hosted models in Frankfurt, storage stays in the EU, and the coaching and analytics your team actually uses are built on top of that EU-resident transcript. No US transcription API, no training on your data.

You can see how the bot connects to the tools your team already runs on the integrations page, and how the wider product fits together on the meeting assistant page. If Google Meet is also in your stack, we cover the same setup for a GDPR-safe notetaker on Google Meet, and if you are comparing tools on data residency directly, the GDPR-compliant AI meeting assistant comparison scores the options.