What was published and who is affected
The documentation verified for this article does not support the claim that the European Commission announced a new round of reports on 24 September 2026. The Commission page included in the research is dated 24 March 2026 and describes the reports published at that time in the Code’s Transparency Centre. The platform providers it names include Google, Meta, Microsoft and TikTok. The Commission presents that publication as the first since the Code was recognised as a Code of Conduct under the Digital Services Act (DSA). The institutional and documentary development that can be substantiated is this: reports were published, but the sources verified here do not confirm the date or reporting period attributed to a supposed September round. The distinction matters because a date, a reporting interval and the contents of a publication are separate factual claims. Confirming one does not establish the others.
It should therefore not be assumed that the documents mentioned on that page cover the period from 1 January to 30 June 2026. The available information does not establish that interval for a round supposedly published on 24 September. The Centre brings together reports from different signatories, and the mention of four major companies does not necessarily mean they were the only participants. To interpret each document, it is worth checking which service it covers and which commitments it addresses: one company may operate several services with different functions. The unit of analysis matters: attributing to an entire company what is reported about a particular service can erase meaningful differences between its products and commitments. A sound reading starts by keeping the reporting entity, the service and the commitment distinct, rather than treating them as interchangeable.
What kind of information the reports provide
The Commission describes the reports published in March as documents detailing measures taken by signatories to reduce the spread of disinformation online. They should be read as accountability documents about commitments and reported actions, not as a uniform result that allows us to conclude, without further analysis, that one platform performed better than another. A reasonable object of comparison is the measures and the way they are reported, taking account of differences in services, commitments and indicators. Describing an action is not the same as demonstrating its effects. A report may explain what a signatory did; assessing what that measure achieved also requires evidence about its results. The distinction helps keep a statement about activity from being mistaken for a finding about impact.
The information verified for this article does not establish a reporting frequency or allow us to detail which services were covered by each of the reports cited by the Commission. The institutional page does mention providers such as Google, Meta, Microsoft and TikTok, alongside other types of signatory, but that is not enough to attribute the same scope or set of indicators to all of them. The existence of reports does not automatically make their data comparable: first, it is necessary to establish which service and commitment each document describes. Even when two reports address similar subjects, their units and definitions may differ. A figure in isolation is therefore insufficient: its meaning depends on how it was defined and on the scope to which it applies. Without that context, a numerical comparison can imply equivalence that the documents themselves do not establish.
Crises, elections and comparing reports
The information provided about a September round of reports does not make it possible to check which chapters it included or to attribute specific measures to each company. The verified Commission page describes the March publication, but it is not enough to establish which crises each report covered or whether every company addressed the same events. To support those claims, the relevant documents would need to be consulted and their data and definitions cited separately. That check avoids turning a general description of the Code into a claim about the contents of reports that could not be reviewed. It also makes clear why a reference to the reporting process cannot stand in for evidence about a particular episode or intervention.
Elections are a relevant topic in the Code’s history, but the sources verified here do not support claims about what companies did during a supposed January-to-June 2026 period. Findings from earlier rounds should not be carried over to a publication that could not be verified, and “elections” and “crises” should not be treated as synonyms. A useful comparison should specify the event, country, service and indicator. If reports do not share those units, the comparison should be limited to describing differences, rather than ranking results. This avoids equating information that may relate to different contexts or measures. A careful account can note what the documents say without implying that distinct situations provide like-for-like evidence.
In practice, readers can begin by identifying the commitment addressed in each section, the reporting period, the geographic scope and the unit of measurement. They can then note whether a report presents an action, a figure or a narrative explanation, and whether it provides enough context to interpret that information. The research materials provided do not include the full contents of every report from the March round, and they do not verify a September 2026 publication. It is therefore not possible to offer a reliable quantitative comparison of Google, Meta, Microsoft and TikTok for that supposed period. The absence of such a comparison does not settle which measures worked: it indicates that the available evidence cannot establish that. Keeping this limitation visible is more accurate than filling the gap with assumptions or transferring conclusions from other reporting periods.
Relationship with the Digital Services Act
The Commission says that integrating the Code into the DSA framework makes it a reference point for determining platforms’ compliance with the law. That regulatory link matters, but it does not mean that every report is an independent audit or that publication certifies that every commitment has been fulfilled. The Code’s reference function places it within the European regulatory framework; it does not in itself amount to a conclusion about the performance of each signatory or the outcome of a particular assessment. This distinction allows the institutional role of the Code to be described without making a separate claim about whether a company met its obligations.
The distinction avoids two simplistic readings. It would be inaccurate to treat the reports as communications unrelated to European regulation; it would also be inaccurate to present them as conclusive proof of compliance or effectiveness. The available source establishes the Code’s role as a reference point, but it does not determine the outcome of a legal assessment of each company. A conclusion about compliance would require specific evidence concerning the applicable obligations, the service, the commitment and the relevant assessment process. The framework and the assessment are related, but not interchangeable: knowing the Code’s function does not allow us to predict the outcome of a particular evaluation. A report can contribute information to scrutiny without itself resolving the legal question.
What the reports do not prove on their own
Publishing a report makes it possible to consult what a signatory says about its measures. On its own, it does not demonstrate that an action reduced exposure to false content, that it was applied consistently, or that its effects were the same across countries and services. Nor can the absence of a figure be taken to mean that no activity occurred. Assessing results requires definitions, comparable data, context and, where appropriate, independent evaluation. Reporting is not the same as verifying impact. Reading the scope of each claim helps separate what the document records from what would still need to be checked. A declaration about an action and evidence of the action’s effect answer different questions.
The limitation of this article is specific: the verified sources include the Commission’s institutional announcement of March 2026 and a Meta report dated March 2026, but not the full text of every report from that month or that of a supposed September round. For that reason, no figures, detailed initiatives or particular outcomes are attributed to the companies for that supposed period. This caution does not invalidate the informational value of the reports; it defines what can be supported by the evidence consulted. The documents are useful for examining commitments and transparency, provided their statements are not confused with direct proof of effectiveness. The reader can use them to understand what signatories say they have done, while keeping conclusions about impact and compliance proportionate to the material actually available.