DSA is not one report for every digital service. creates annual public reporting for covered intermediary services, Article 24 adds online-platform reporting fields and active-recipient publication, Article 24(5) sends covered platform statements of reasons into the Commission database, and adds six-month reporting and extra disclosures for designated very large online platforms and search engines.
1
Section 1
Provider-tier map for DSA transparency reporting
Start by classifying the service before collecting numbers. The baseline report applies to providers of intermediary services unless Article 15(2) excludes a qualifying micro or small provider that is not a VLOP; it is not optional merely because a covered provider reports zero moderation activity. Recommendation 2003/361/EC sets the size tests: fewer than 10 staff and no more than EUR 2 million annual turnover or balance-sheet total for a microenterprise, and fewer than 50 staff and no more than EUR 10 million for a small enterprise, after counting partner and linked enterprises as required. Hosting services then have additional notice-and-action fields, online platforms have additional dispute and misuse-suspension fields, and VLOPs or VLOSEs have enhanced reporting.
A useful reporting register should therefore hold one row per service, not one row per legal entity. The row should identify whether the service is an intermediary service, hosting service, online platform, online search engine, VLOP, or VLOSE; whether a micro or small enterprise exclusion is being relied on; the reporting period; the public report URL; and the evidence system that produced each figure.
Intermediary services: publish at least annual machine-readable reports on content moderation, including Member State authority orders, own-initiative moderation, internal complaints where relevant, and automated moderation information.
Hosting services: add Article 16 notice metrics, including alleged illegal-content categories, trusted-flagger notices, action basis, automated processing, and median time to act.
Online platforms: add out-of-court dispute settlement outcomes, median completion time, share of implemented outcomes, and suspensions for manifestly illegal content or manifestly unfounded notices or complaints.
VLOPs and VLOSEs: report at least every six months and add Member State active-recipient figures. VLOPs also add the fields for moderation staffing, qualifications, linguistic expertise, and language-level accuracy indicators. Separately track Article 42(4) transmission and publication of risk, mitigation, audit, audit-implementation, and consultation materials.
Requires DSA transparency reports to use the CSV or XLSX templates in Annex I and sets harmonised reporting periods, publication timing, and retention.
Defines the staff, turnover, balance-sheet, partner-enterprise, and linked-enterprise tests used by the Article 15(2) reporting exclusion.
2
Section 2
Report fields and cadence to build into the data model
The report is a content-moderation report, so its source data should come from moderation, notice, order, complaint, automation, and policy-enforcement systems rather than from a narrative compliance memo. The implementing regulation makes the report operational by providing templates and requiring public availability no later than two months after the end of the relevant reporting period.
For non-VLOP intermediary, hosting, and online-platform reports, the harmonised yearly reporting period is 1 January through 31 December. The first full annual cycle under the official templates is 1 January through 31 December 2026; the shortened 2025 cycle used transitional instructions, with Annex I required for data from 1 July 2025. For VLOPs and VLOSEs, the first template-based period was 1 July through 31 December 2025, followed by six-month periods of 1 January through 30 June and 1 July through 31 December. The first harmonised reports were due by the end of February 2026. Reports must remain publicly available for at least five years after publication, including updated versions.
Orders: count Member State judicial or administrative orders, category of illegal content, issuing Member State, median acknowledgement time, and median time to give effect to the order.
Notices: count Article 16 notices, trusted-flagger notices, specific items reported, action taken, whether the action was based on law or terms, automated processing, and median time to act.
Own-initiative moderation: report restriction types such as removal, disabling, demotion, visibility restriction, monetary restriction, account restriction, and the detection method used.
Complaints and redress: report complaint bases, decisions, median decision time, reversals, out-of-court dispute settlement outcomes, and implementation share.
Automation: record qualitative descriptions, precise purposes, accuracy indicators, possible error rates, safeguards, and which notice or measure counts were processed solely by automated means.
Annex I and Annex II provide the report templates and instructions for order, notice, own-initiative moderation, complaint, automation, staffing, and active-recipient fields.
Commission overview of DSA transparency reports, active-recipient publication, statements of reasons, transparency database, and VLOP/VLOSE report links.
Transparency reports
3
Section 3
Active-recipient publication is separate from the transparency report
Article 24(2) requires covered providers of online platforms and online search engines to publish, for each service, average monthly active recipients in the Union at least every six months. Article 19 can exclude qualifying micro and small online-platform providers from Article 24(2), while expressly retaining Article 24(3). This publication is relevant to possible VLOP or VLOSE designation, but it is not the same deliverable as the annual report.
Keep the calculation evidence separate from the moderation report evidence. The record should show the six-month measurement window, service boundary, inclusion and exclusion logic, data sources, deduplication method, public page URL, publication date, and any response sent to the Digital Services Coordinator of establishment or the Commission if they request updated or substantiating information.
Publish figures per online platform or online search engine in a publicly available section of the online interface.
Update the figures at least once every six months and preserve the calculation memo used for each publication.
Treat service-boundary changes, acquisitions, major launches, or changes to counting methodology as reassessment triggers.
For VLOPs and VLOSEs, also prepare reporting of average monthly active recipients for each Member State.
Article 24(2) requires six-month publication of average monthly active recipients, and Article 33 uses active-recipient data for VLOP and VLOSE designation.
Commission overview explains the 45 million EU user threshold, six-month user-number updates, designation effects, and enhanced duties for very large services.
over 45 million users
4
Section 4
Statements of reasons and the Commission transparency database
Article 17 requires hosting services to give affected recipients clear and specific statements of reasons when they remove, disable access to, demote, restrict visibility, suspend, terminate, or otherwise restrict monetary payments, or otherwise restrict user-provided information because it is alleged to be illegal or incompatible with terms. (Article 24(5)) then requires online platforms covered by that provision to submit those decisions and statements of reasons to the Commission database without undue delay and without personal data; Article 19 can exclude qualifying micro and small providers from that platform-section duty.
This database obligation should be managed as an event stream, not as an annual report appendix. Moderation systems need enough structured fields to produce the recipient notice, submit the platform statement to the database, suppress personal data from the submission, and reconcile rejected or corrected submissions.
Before including a moderation event, apply Article 17's delivery and exclusion rules: the relevant recipient contact details must be known, the notice is due at the latest when the restriction is imposed, and deceptive high-volume commercial content and Article 9 orders are excluded. Keep the recipient notice and database event as separate records.
Capture the restriction type, territorial scope where relevant, duration where relevant, facts and circumstances, notice or own-initiative origin, automated-means information, legal ground or terms ground, and user redress information.
Do not send personal data to the Commission database; keep redress information for the affected recipient rather than treating it as a public database field.
Use submission logs to reconcile moderation decisions against database delivery, schema errors, corrections, and late submissions.
Preserve database exports or checks showing that the submitted statement can be found, downloaded, or accounted for through the Commission's published database tooling.
Article 17 specifies statement-of-reasons content, while Article 24(5) requires online platforms to submit decisions and statements to the Commission database without personal data.
Commission FAQ explains what statements of reasons are, which providers submit them, what the public database contains, and how database retention and downloads work.
publicly accessible and machine-readable
5
Section 5
VLOP and VLOSE reporting evidence
Designated VLOPs and VLOSEs need the baseline reporting evidence, but adds evidence that smaller providers do not need to publish in the same way. For VLOPs, the transparency report must specify moderation human resources by EU official language, qualifications and linguistic expertise, training and support, and language-level indicators for automated-means accuracy. VLOPs and VLOSEs also report Member State active-recipient data.
also requires designated services to transmit and make public risk assessment, mitigation, audit, and audit implementation reports within the DSA rule structure, subject to the public-report redaction route where publication would disclose confidential information, create significant service-security vulnerabilities, undermine public security, or harm recipients.
Maintain full-time equivalent (FTE) and contractor evidence for internal and external moderation resources, including language coverage and qualifications.
Keep training records, reviewer-support materials, quality checks, and language-level accuracy metrics next to the numbers reported in the template.
Tie each six-month transparency report to the service designation date, reporting period, public URL, and any corrected version.
For risk and audit reporting, keep both the public version and the complete version sent to the Digital Services Coordinator of establishment and the Commission, plus the reasons for any public redaction.
Commission overview describes VLOP/VLOSE designation, the four-month compliance window after designation, and obligations such as audits, data access, recommender options, and ad repositories.
four months to comply
6
Section 6
Evidence checklist before publication
Before publishing a DSA transparency report, test whether every public number can be traced back to a service, reporting period, legal field, source system, extraction query, owner approval, and version. The implementing regulation's template should be treated as the report specification, not as a final formatting step.
The highest-risk gaps are mismatched service tiers, annual reports that omit online-platform fields, moderation systems that cannot distinguish law-based actions from terms-based actions, automated-moderation metrics without error or accuracy context, and statement-of-reasons pipelines that lack personal-data controls.
Is the DSA active-recipient publication the same as the annual transparency report?
No. Article 24(2) requires online platforms and online search engines to publish average monthly active recipients in the Union at least every six months. separately requires public transparency reports on content moderation at least once a year, and requires VLOPs and VLOSEs to publish transparency reports at least every six months.
Do all hosting services submit statements of reasons to the Commission database?
Article 17 applies to hosting services when they issue moderation decisions covered by that article, but Article 24(5) requires covered online platforms to submit those decisions and statements of reasons to the Commission database. Article 19 can exclude qualifying micro and small online-platform providers from Article 24(5). Submitted information must not contain personal data.
What changed with Implementing Regulation (EU) 2024/2835?
It provides harmonised CSV and XLSX transparency-report templates, sets annual and six-month reporting periods, requires reports no later than two months after the reporting period ends, and requires at least five years of public availability. The templates applied to content-moderation data collected from 1 July 2025. The first template-based VLOP/VLOSE period was 1 July to 31 December 2025, while the first full harmonised annual cycle for other covered providers is 1 January to 31 December 2026.
Provider-tier memo: service type, micro or small enterprise position if relevant, VLOP/VLOSE designation status, and applicable DSA articles.
Template map: each , 24, and 42 field mapped to a source system, data owner, extraction query, QA check, and public report row.
Publication file: public ODF CSV report, human-readable explanation where used, publication URL, publication date, version label, and five-year retention control.
evidence: six-month active-recipient calculation, service boundary, methodology notes, public page URL, and any authority request or response.
VLOP/VLOSE evidence: six-month report package, Member State table, and risk and audit report publication or redaction record; for a VLOP, also keep moderation staffing and language coverage records.
Supports evidence controls for statement-of-reasons submission, public search and downloads, personal-data exclusion, and database retention behavior.
remove any personal data
Recommended next step
Map provider tier, report fields, source systems, and publication evidence
Sorena can help translate DSA Articles 15, 24, and 42 into service-level report inventories, data-field mappings, statement-of-reasons checks, active-recipient evidence, and publication controls.
Primary legal source for Articles 15, 17, 24, 33, and 42 on transparency reports, statements of reasons, active-recipient publication, VLOP/VLOSE designation, and enhanced reporting.
Articles 15, 24, and 42 define the provider-tier reporting obligations, online-platform additions, active-recipient publication, statements-of-reasons submission, and VLOP/VLOSE reporting duties.
Article 24(2) requires six-month publication of average monthly active recipients, and Article 33 uses active-recipient data for VLOP and VLOSE designation.
Show 2 more
Article 17 specifies statement-of-reasons content, while Article 24(5) requires online platforms to submit decisions and statements to the Commission database without personal data.
Article 42 sets six-month VLOP/VLOSE reporting, VLOP moderation-resource fields, Member State active-recipient reporting, and risk, mitigation, audit, and audit-implementation publication rules.
Requires DSA transparency reports to use the CSV or XLSX templates in Annex I and sets harmonised reporting periods, publication timing, and retention.
Annex I and Annex II provide the report templates and instructions for order, notice, own-initiative moderation, complaint, automation, staffing, and active-recipient fields.
Show 1 more
Supports the evidence checklist for templates, reporting periods, publication deadline, report retention, updated versions, and field-level reporting instructions.
Commission FAQ for statement-of-reasons content, online-platform submission to the DSA Transparency Database, public access, downloads, and retention.
Commission FAQ explains what statements of reasons are, which providers submit them, what the public database contains, and how database retention and downloads work.
Supports evidence controls for statement-of-reasons submission, public search and downloads, personal-data exclusion, and database retention behavior.
Commission overview of the 45 million EU user threshold, six-month user-number updates, designation effects, and enhanced VLOP/VLOSE obligations.
Commission overview explains the 45 million EU user threshold, six-month user-number updates, designation effects, and enhanced duties for very large services.
Commission overview describes VLOP/VLOSE designation, the four-month compliance window after designation, and obligations such as audits, data access, recommender options, and ad repositories.