Platform transparency in the EU: what changed and what users can consult

The verifiable development is not a new European transparency law adopted this year. It is the introduction of a common template for the transparency reports required under the Digital Services Act (DSA). On 2 March 2026, the European Commission reported that the deadline for the first round of harmonised reports had passed. The practical aim is to make the data that services publish about their content-moderation activities more comparable. In other words, the change is to organise reporting in a shared way so that information can be related more easily—not to create the reporting obligation from scratch. A common structure can make it easier to identify what different providers say about their practices and to compare information that previously appeared in unlike formats.

Before harmonisation, services could present information using different formats, labels, categories or terminology. That made reports harder to compare, even when they described similar activities. The common template is intended to reduce this friction and make analysis easier for authorities and civil society. When two reports structure their information differently, a reader may first have to interpret each scheme before comparing them; a shared format reduces some of that preliminary work. The change concerns comparability and presentation; it does not mean that every moderation decision is now more visible or easier to assess. The March date refers to the first reporting round, not to a last-minute announcement. Nor does a common template erase differences between providers’ processes: it provides a more consistent basis on which those differences can be examined.

The DSA requires online services to publish data about their content-moderation practices at least once a year. For very large online platforms (VLOPs) and very large online search engines (VLOSEs), the frequency indicated by the Commission is twice a year. The information can help readers examine, for example, how providers describe their moderation activities and the measures they take in response to content. The reporting frequency tells us how often reports are published; it does not automatically turn each publication into an individual explanation of decisions made during that period. A report covering a period and an account of a particular user’s case serve different purposes.

The implementing regulation on reporting established common templates and periods. The Commission says that companies were required to begin collecting data under those rules on 1 July 2025 and that the first harmonised reports were due in early 2026. The period of data collection under the common rules therefore comes before the first reporting round: the stages are connected, but they are distinct. It is therefore useful to distinguish between the general duty to report, the rules that standardise reporting, and publication of the first round in the new format. These are not three names for the same measure, and they did not necessarily take effect on one and the same date. Keeping the stages separate helps explain how the new format became operational without suggesting that the underlying reporting duty began only with its first publication.

The DSA framework covers different intermediary services, and their obligations vary according to the type and size of provider. The Commission identifies online marketplaces, social networks, app stores, and travel and accommodation platforms among the relevant services. The more extensive supervision and reporting obligations apply to platforms and search engines designated as very large. The Commission says that this category covers services with more than 45 million monthly users in the EU. It should therefore not be assumed that every service within the framework has exactly the same obligations: the applicable category matters. The reporting framework is shared, but the requirements placed on an individual provider depend on its status under the rules.

For the public, the reports’ value is mainly indirect: they provide material that regulators, researchers and civil-society organisations can use to examine platform practices. The law also provides for other transparency tools, including a database of statements of reasons for moderation decisions and access to certain data for researchers. These tools do not turn a general report into a record of every case; rather, they form part of a broader set of ways to observe practices. A report is not an individual case file and does not guarantee that a user can reconstruct why a particular decision was made. For a personal complaint, users should use the reporting and appeal channels available on the service, as well as the relevant routes in their country. The distinction matters because transparency at system level can support scrutiny without replacing the procedures through which an individual challenges an outcome.

A uniform format makes it easier to align categories and review data series across providers or time periods. This is a useful accountability improvement: it reduces some of the work involved in translating different structures before analysing the information. It can also make differences between reports more visible, although interpreting those differences still depends on what data are collected and how each provider describes its processes. Comparisons are more direct when elements appear under a shared structure, but readers still need to understand what each data point represents. A common layout supports comparison; it does not remove the need to examine definitions, coverage and context.

Harmonisation does not automatically turn the data into a direct measure of moderation quality. A figure may depend on definitions, counting methods and context that cannot be captured in a table alone. Nor does a figure, by itself, prove that a platform has met all its obligations or infringed rights. The Commission itself warns that its explanatory pages provide an overview and do not replace the legal provisions or constitute a binding interpretation of them. Responsible reading combines the report with the rules, the methodology and, where appropriate, other evidence. In this way, figures are treated as information requiring context, rather than as an automatic conclusion about a provider’s conduct. The reports can inform scrutiny, but their limits should remain clear whenever their contents are used to support a wider claim.

The available documentation does record transparency-related developments during 2026, but they do not all have the same scope. In July, the Commission said it had accepted an action plan from X concerning transparency obligations and researchers’ access to data. This is a specific action involving one company and a compliance plan; it is not a general reform of the DSA and does not replace the harmonised reports applicable to covered providers. It may therefore be mentioned as a related development, but not as a change that, by itself, alters the general reporting system. Its company-specific character is important when setting it alongside rules that apply across categories of services.

The editorial conclusion is specific: the first harmonised round is a significant operational change, announced by the Commission in March 2026. The sources consulted do not support presenting it as a new general obligation approved now, in October. Publication of the reports may improve the ability to compare practices, but their actual usefulness depends on the quality, detail and interpretation of the data. To claim an additional change, one would need to identify a later rule, decision or announcement with a precise scope and timetable. This distinction recognises the practical importance of a common format without attributing effects that the reports, by themselves, do not establish. It also keeps separate the evidence of a reporting change from any broader assessment of how platforms moderate content.