EU AI Act Emotion Recognition Ban and Meeting Tools

The short answer: The EU AI Act bans inferring employees’ emotions from biometric data such as voice, and consent does not cure it. Analysing the sentiment of a written transcript is outside the ban on the Commission’s reading, so the question for any meeting tool is whether it reads your audio or your text. Tools that process audio on the user’s device, such as Hedy, keep that question inside the customer’s own control.

On 2 August 2026 a large part of the EU AI Act began to apply, and a lot of coverage claimed that sentiment analysis in meeting tools was now illegal. That is not quite right, and the real rule is narrower and older. The part that is prohibited is genuinely prohibited, and consent will not save you.

What the rule actually says

The relevant provision is Article 5(1)(f). It prohibits placing on the market, putting into service for this specific purpose, or using AI systems to infer emotions of a natural person in the areas of workplace and education institutions, except for medical or safety reasons. Read with the Article 3(39) definition of an emotion recognition system and the Commission’s guidelines, the inference in question is one drawn from biometric data: voice, face, keystroke dynamics, posture.

Three things about that sentence do the work.

It is a prohibition, not a restriction. Article 5 is the Act’s list of banned practices. This is a different category from the high-risk regime, which imposes conformity assessments and documentation. The ceiling for administrative fines under Article 99(3) is the higher of EUR 35 million or 7% of worldwide annual turnover (the lower amount for small and medium-sized enterprises).

Consent does not cure it. Under GDPR, consent is one available lawful basis for processing. Article 5 does not work that way. A prohibited practice remains prohibited even if every employee in the building signs a form agreeing to it.

It hinges on biometric data. This is the limiting condition, and it is where the “your tool is now illegal” claims fall apart. The Commission’s guidelines on prohibited practices say the prohibition is limited to inferences based on a person’s biometric data.

The distinction that decides your case

The Commission’s guidelines draw a line that matters enormously for meeting software: inferring emotions from written text does not fall within the scope of the prohibition.

Most meeting assistants that advertise “sentiment analysis” are not analysing your voice. They transcribe the call to text, then run a language model over the transcript to judge whether the customer sounded positive or negative about pricing. That is text analysis, and on the Commission’s reading it sits outside Article 5(1)(f).

Some conversation-intelligence systems instead analyse the audio signal itself (tone, pitch, pace) to infer emotional state. Voice is a physiological and behavioural characteristic. That is far closer to the line, and in a workplace context it is the implementation most likely to be caught.

So the question is not “does this tool do sentiment analysis.” The question is “does it infer emotion from the audio, or from the transcript?”

A few more boundaries worth knowing. The Commission’s guidelines say the prohibition does not cover physical states such as pain or fatigue, and the Act’s recitals say the same. The medical and safety exceptions are read narrowly: therapeutic uses with CE-marked medical devices, or protecting life and health. General workplace wellness monitoring, such as burnout or stress scoring, is not covered by the exception.

The prohibition applies to placing on the market, putting into service and use, so it reaches employers who deploy a system, not only providers. An employer cannot rely on a vendor’s terms as a defence for having deployed it that way.

There is also a separate, lesser duty in Article 50(3): deployers of an emotion recognition system that is not prohibited must inform the people exposed to it. Do not confuse the two. Satisfying Article 50 does nothing for you if Article 5 applies.

The dates, as of 27 October 2026

A great deal of August coverage stated that the emotion recognition ban “took effect” on 2 August 2026. It did not.

The last two rows come from the Digital Omnibus on AI, Regulation (EU) 2026/1744. It was published in the Official Journal on 24 July 2026 and entered into force on 27 July 2026, so the postponement is final. It left Article 5(1)(f) alone. The exposure for voice-based emotion inference in an EU workplace is therefore not new: the prohibition has applied since February 2025, and fines have been available since August 2025. How quickly national authorities enforce is a separate question that varies by member state.

What this means for the tools we review

Of the 28 AI meeting assistants we rank, three ship features that put this question in play: Read.ai, whose engagement and sentiment scoring was its original product; Avoma, which extracts buyer sentiment as part of its revenue intelligence; and Fireflies.ai, which includes sentiment analysis in its conversation intelligence suite.

None of the three publishes, as far as we can find, a clear statement of whether their sentiment inference runs on audio characteristics or on transcript text. That is not an accusation. It is a documentation gap, and every European buyer of these tools should close it in writing. We have added a note to each of those three reviews rather than adjusting scores, because we do not know which implementation each uses, and guessing would be worse than saying so.

The questions to actually ask your vendor

If you are deploying a meeting assistant to employees in the EU, put these in an email and keep the reply.

Does any feature infer emotional state? Get a yes or no covering sentiment scoring, engagement analytics, mood tracking, and any coaching feature that grades tone.

If yes: does it infer from audio characteristics, or from transcript text? This is the determinative question. Ask for a technical answer, not a marketing one.

Can the feature be disabled at the workspace or tenant level? For most organisations, the cleanest response is to turn it off for EU staff. If the vendor cannot switch it off per region, that is itself a finding.

Which entity is the provider and which is the deployer for this feature? Article 5 binds both. You do not get to point at the vendor.

What is the contractual position on Article 5? Reputable vendors will have thought about this by now. Ones that have not are telling you something.

The broader pattern

Something consistent is happening across the legal picture this year. In the Otter.ai lawsuit a US court held, at the pleading stage, that a vendor which independently collects, retains and uses meeting recordings for its own commercial purposes can be treated as a third-party eavesdropper. Here, European law says certain inferences about employees are off the table regardless of what anyone consents to. (This post was first published on 7 August 2026; we added the Otter reference and the Omnibus dates in October.)

Both point the same direction: the law is becoming less interested in whether you clicked agree, and more interested in what the software actually does with what it hears. Architectures that minimise what leaves the room age well under that pressure. Hedy runs speech recognition on your device, can run its AI there too with Local AI on supported hardware, and offers EU data residency when you choose its cloud, so an EU buyer can keep audio processing under its own control. That does not replace asking any vendor, Hedy included, the audio-or-transcript question above. For more, see our GDPR and EU data residency guide, our privacy guide and the lawsuit tracker.

Sources: Regulation (EU) 2024/1689 (Articles 3(39), 5(1)(f), 50, 99, 113); the Commission’s guidelines on prohibited AI practices (February 2025); Regulation (EU) 2026/1744, OJ L, 24 July 2026.

This article is analysis, not legal advice. The application of Article 5(1)(f) to any specific product depends on technical facts about that product and on guidance that continues to develop. Take advice on your own deployment.