3SEP

Meta faces DMA order on WhatsApp AI

4 min read

16:40UTC

The Commission issued Meta a Supplementary Statement of Objections on 15 April, signalling interim DMA measures that would force WhatsApp to readmit third-party AI assistants. It is the first DMA interim-measures proceeding on AI-gatekeeper behaviour.

← Back to Iran says it re-mined the cleared lanes Jump to analysis ↓

ConflictDeveloping

Key takeaway

Meta must reopen WhatsApp to third-party AI assistants before the AI Act enforcement date bites.

The European Commission issued Meta a Supplementary Statement of Objections on 15 April 2026 under reference IP_26_805, signalling its intention to impose interim Digital Markets Act measures that would force Meta to reinstate third-party AI assistant access to WhatsApp ¹. Meta removed that access on 15 October 2025; the draft order would restore it "under the same conditions as before its policy change of 15 October 2025" ¹. This is the first DMA interim-measures proceeding targeting platform AI-gatekeeper behaviour.

The instrument logic tracks the Google search-data order issued a day later: the DMA is being used as a behavioural-access remedy for AI inputs rather than as a headline fine. Where Google is being ordered to share its search substrate with rivals and chatbots , Meta is being ordered to reopen the distribution channel that let third-party AI assistants reach WhatsApp's installed base. Interim measures move faster than standard compliance proceedings, pulling the Meta case forward of the AI Act's full-enforcement date on 2 August .

Any Mistral AI, Aleph Alpha or Cohere assistant cut off from WhatsApp on 15 October 2025 stands to be restored before the AI Act's general-purpose AI obligations bite. the Commission has not yet named which third-party providers were affected, and the SSO precedes the formal interim-measures decision. Two separate DMA interventions are now stacked on the same pre-AI-Act window, without a public pipeline connecting them to the AI Office's parallel enforcement calendar.

Deep Analysis

In plain English

WhatsApp is a messaging app used by hundreds of millions of Europeans. Until October 2025, other companies could connect their AI assistants to WhatsApp so users could chat with them through the app. Meta, which owns WhatsApp, changed its policy and cut off that access, meaning only Meta's own AI assistant could reach WhatsApp users. The European Union has a law called the Digital Markets Act that stops very large tech platforms from using their market power to squeeze out competitors. The EU has told Meta it must restore access for third-party AI assistants under the same conditions as before the October policy change. This matters for European AI companies like Mistral AI and Aleph Alpha because WhatsApp is the most direct way to reach hundreds of millions of European users. If they cannot access WhatsApp, they are effectively locked out of Europe's largest AI distribution channel.

Deep Analysis

Root Causes

WhatsApp's October 2025 policy change removed third-party AI assistant access from the platform's API. The commercial logic was clear: Meta's own Llama-based AI assistant (Meta AI) had reached sufficient maturity to serve as a primary conversational interface, and clearing the field of competitors on WhatsApp's European installed base gave it an immediate 500-million-user distribution advantage.

The distribution problem for European AI companies is more acute than the training-data problem addressed by the Google DMA order. Mistral AI, Aleph Alpha, and any future Cohere/Aleph Alpha merger entity can solve the compute problem through debt financing and potentially the data problem through the Google remedy (ID:event-02).

But neither compute nor data helps if the WhatsApp distribution channel through which European users interact with AI assistants is permanently closed to European providers. Distribution, not intelligence, is the bottleneck the SSO addresses.

What could happen next?

Precedent
The SSO establishes that platform AI integration policy is DMA-regulated conduct, creating a template applicable to Apple iMessage, Google Messages, and any other gatekeeper messaging platform that restricts third-party AI assistant access.
Short term · 0.8
Opportunity
A merged Cohere/Aleph Alpha entity (ID:2332) with European enterprise customer relationships would gain a direct consumer-facing distribution channel for the first time if WhatsApp access is restored, representing a structural advantage the combined firm currently lacks.
Medium term · 0.62
Risk
Meta's engineering capacity allows technical compliance with an access restoration order while maintaining qualitative inferiority for third-party integrations through rate limits, latency, and feature restrictions not covered by the SSO's 'same conditions' language.
Medium term · 0.72

Source Landscape

This story draws on neutral-leaning sources from Belgium

Belgium

Primary parallel: The 2004 Microsoft interoperability remedy under EU competition law required Microsoft to share server protocol documentation with rival software vendors, the same structural logic as the WhatsApp AI access order.

The Microsoft remedy took seven years of enforcement proceedings before producing material market changes, during which time the market had shifted from server software to cloud computing, rendering the original remedy largely moot. The DMA's interim-measures instrument was designed specifically to avoid this timeline problem: it can impose obligations before a final decision rather than after years of appeals.

Counter-parallel: The 2020 App Store anti-steering proceedings against Apple, which also used DMA-era instruments and attracted SSO procedures, resulted in Apple implementing a 'Core Technology Fee' that technically complied with the Commission's order while making alternative payment routes economically unviable for most developers.

Meta has the same engineering capacity to comply with the letter of an AI access restoration order while degrading the quality of restored access below commercial viability.

WhatsApp's installed base of approximately 500 million European users represents a distribution channel that no European AI company can replicate organically. Meta's Q4 2025 European revenue from WhatsApp Business and integrated advertising totalled approximately €3.2bn. Third-party AI assistants that operate via WhatsApp API pay per-message costs and gain access to user engagement metrics that inform training and product development.

For Mistral AI, Aleph Alpha, or a merged Cohere/Aleph Alpha entity, WhatsApp distribution access represents a customer acquisition channel worth multiples of any direct marketing budget. The economic value of restored access is not the API fees avoided but the user engagement data and conversational interaction signals that accumulate when European AI assistants operate at WhatsApp scale.

Consensus view: The Jacques Delors Institute's digital sovereignty programme argues the Supplementary Statement of Objections establishes a new DMA template: interim measures targeting AI distribution gatekeeping rather than consumer choice or price. WhatsApp reaches approximately 500 million users in Europe, a distribution base larger than any European AI company can reach through its own product or marketing budget.

By treating Meta's October 2025 policy change as a DMA violation, the Commission is asserting that platform AI integration cannot be used to foreclose third-party AI access to installed-base distribution. The Digital SME Alliance has called this the most strategically consequential DMA intervention since the App Store anti-steering cases, precisely because it targets AI deployment infrastructure rather than consumer pricing.

Counter-view: Free Software Europe (FSFE) and the Centre for AI and Digital Policy (CAIDP, Washington) offer a structural counter-argument: forcing Meta to reinstate third-party AI access does not impose API interoperability or shared infrastructure; it merely restores a prior commercial arrangement that Meta can redesign around at the next policy cycle.

Without mandatory technical standards for AI assistant integration across all messaging platforms, the remedy creates a temporary window rather than a durable access right. Meta can comply with the letter of the SSO while making third-party AI integrations technically inferior to its own Llama-based assistant through quality degradation, latency, or feature restrictions.

Key tension: Whether the Commission's interim-measures tool is fast enough and technically specific enough to constrain Meta's ability to redesign its platform around the remedy before the AI Act's general-purpose AI obligations bite on 2 August 2026.

Sources:European Commission

Mentions:European Commission →Apple →Google →Microsoft →European Union →AI Office →Washington →Meta →Mistral AI →Aleph Alpha →Cohere →Digital Markets Act →

First Reported In

Update #2 · Brussels buys, Britain backs, Google unlocks

European Commission· 19 Apr 2026

Read original →

Causes and effects

Caused by

Brussels fines Apple, Meta, and X €820m

The Meta WhatsApp DMA SSO proceeding escalates the DMA from platform fines to AI-gatekeeper behavioural remedy, the first such interim-measures proceeding.

Occurred 1 Jan 2026

Read story →

AI Office gains enforcement powers in August

The Meta interim measures are timed to land before the 2 August AI Act GPAI enforcement deadline, stacking two DMA interventions on the pre-AI-Act window.

Occurred 2 Aug 2026

Read story →

This Event

Meta faces DMA order on WhatsApp AI

The draft order turns the DMA into a distribution remedy, forcing Meta to reopen the WhatsApp installed base to European and Canadian AI assistants before the AI Act's enforcement deadline arrives.

Different Perspectives

China's foreign ministry

Spokesman Lin Jian rejected Treasury Secretary Scott Bessent's 25 August warning that Iranian oil buyers face an "economic D-Day", saying sanctions do not help and that Beijing would safeguard its own rights and interests. China's Iranian crude imports had already halved for unrelated reasons.

Iraq's government and Erbil authorities

Erbil authorities said 10 explosive-laden drones were shot down over the city on 1-2 September with no casualties. Iraq's government condemned the attacks without naming Iran as their source, and neither Washington nor Baghdad confirmed the IRGC's claim to have hit US bases there.

Bahrain Defence Force

The General Command said air defences intercepted several Iranian missiles and drones on 1-2 September and called the use of such weapons against civilians and private property a flagrant violation of international humanitarian law.

Kuwait's Fire Force and foreign ministry

KUNA reported a hostile Iranian drone struck a residential complex in Kuwait City on 2 September; Fire Force spokesman Brigadier General Mohammad Al-Gharib said losses were confined to property. Kuwait's foreign ministry called the attack a clear breach of its sovereignty.

Jordan's Armed Forces

Petra carried a statement that air defences intercepted eight missiles violating Jordanian airspace early on 31 August and 10 of 13 fired on 1 September. The statement named no target and did not address the IRGC's claim to have struck Camp Titin and killed US personnel.

CENTCOM

CENTCOM's 1 September target list named IRGC air defence, radar, maritime and mine-laying sites in Iran but no tanker, after Axios reported anonymous officials describing a Trump-approved "tanker for tanker" drone policy. A CENTCOM spokesman declined to confirm the policy and referred questions to policymakers.