Artifact GuideEU

DSA Transparency Reporting by Provider Tier

Map which DSA transparency-reporting duties apply to intermediary services, hosting services, online platforms, and designated VLOPs or VLOSEs.

Use this page to separate annual content-moderation reports, six-month active-recipient publication, statements-of-reasons database submissions, and enhanced VLOP/VLOSE reporting evidence.

Author
Sorena AI
Published
May 9, 2026
Updated
May 9, 2026
Sections
6

Structured answer sets in this page tree.

Primary sources
6

Cited legal and guidance references.

Publication metadata
Sorena AI
Published May 9, 2026
Updated May 9, 2026
Overview

DSA transparency reporting is not one report for every digital service. Article 15 creates annual public reporting for content moderation by intermediary services, Article 24 adds online-platform reporting fields and active-recipient publication, Article 24(5) sends platform statements of reasons into the Commission database, and Article 42 adds six-month reporting and extra disclosures for designated very large online platforms and search engines.

Section 1

Provider-tier map for DSA transparency reporting

Start by classifying the service before collecting numbers. The baseline Article 15 report applies to providers of intermediary services that engage in content moderation, subject to the DSA's micro and small enterprise exclusion where the provider is not a VLOP. Hosting services then have additional notice-and-action fields, online platforms have additional dispute and misuse-suspension fields, and VLOPs or VLOSEs have enhanced Article 42 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 the Article 42 fields for moderation staffing, qualifications, linguistic expertise, language-level accuracy indicators, Member State active-recipient figures, and risk, mitigation, audit, and audit-implementation reports.
Section 2

Report fields and cadence to build into the data model

The Article 15 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. For VLOPs and VLOSEs, the implementing regulation uses six-month periods of 1 January through 30 June and 1 July through 31 December. 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, monetisation 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.
Section 3

Active-recipient publication is separate from the transparency report

Article 24(2) requires 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. This publication is relevant to possible VLOP or VLOSE designation, but it is not the same deliverable as the annual Article 15 report.

Keep the AMAR calculation evidence separate from the moderation report evidence. The file 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 AMAR 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 Article 42 reporting of average monthly active recipients for each Member State.
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 or terminate monetisation, or otherwise restrict user-provided information because it is alleged to be illegal or incompatible with terms. Article 24(5) then requires online platforms to submit those decisions and statements of reasons to the Commission database without undue delay and without personal data.

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.

  • 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.
Section 5

VLOP and VLOSE reporting evidence

Designated VLOPs and VLOSEs need the baseline reporting evidence, but Article 42 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.

Article 42 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 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 Article 42 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.
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. Article 15 separately requires public transparency reports on content moderation at least once a year, and Article 42 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 online platforms to submit those decisions and statements of reasons to the Commission database. The 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 to be publicly available no later than two months after the reporting period ends, and requires reports to remain public for at least five years after publication.

  • Provider-tier memo: service type, micro or small enterprise position if relevant, VLOP/VLOSE designation status, and applicable DSA articles.
  • Template map: each Article 15, 24, and 42 field mapped to a source system, data owner, extraction query, QA check, and public report row.
  • Publication file: public CSV or XLSX report, human-readable explanation where used, publication URL, publication date, version label, and five-year retention control.
  • AMAR evidence: six-month active-recipient calculation, service boundary, methodology notes, public page URL, and any authority request or response.
  • Statement-of-reasons evidence: recipient notice template, database payload schema, personal-data suppression check, submission logs, and correction workflow.
  • VLOP/VLOSE evidence: six-month report package, Member State AMAR table, moderation staffing and language coverage records, risk and audit report publication or redaction record.
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 sources

References and citations

eur-lex.europa.eu
Referenced sections
  • Supports the evidence checklist for templates, reporting periods, publication deadline, report retention, updated versions, and field-level reporting instructions.
"at least five years"
digital-strategy.ec.europa.eu
Referenced sections
  • Supports evidence controls for statement-of-reasons submission, public search and downloads, personal-data exclusion, and database retention behavior.
"remove any personal data"
digital-strategy.ec.europa.eu
Referenced sections
  • 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"
eur-lex.europa.eu
Referenced sections
  • 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.
"thereafter at least every six months"
Related guides

Explore more topics

DSA Ads and Recommender Systems: transparency duties, user choice, and evidence
A grounded DSA guide to ad labels, targeting restrictions, recommender parameter disclosure, non-profiling options for VLOPs and VLOSEs, ad repositories, and compliance evidence.
DSA Applicability Test: classify intermediary services, platforms, marketplaces, VLOPs and VLOSEs
A source-grounded EU Digital Services Act applicability test for classifying intermediary services, hosting services, online platforms, marketplaces, VLOPs and VLOSEs.
DSA Article 28 minors protection guide for online platforms
EU Digital Services Act guide to Article 28 minors protection: platform scope, child-safety measures, targeted ads limits, recommender controls, and grounded evidence.
DSA average monthly active recipients: what platforms must publish
A grounded FAQ on average monthly active recipients under the EU Digital Services Act, including publication, EU recipient scope, the 45 million VLOP/VLOSE threshold, and evidence records.
DSA Complaint and Dispute Workflows for Online Platforms
Build DSA complaint, appeal, statement-of-reasons, and out-of-court dispute workflows for online platform moderation decisions.
DSA crisis response for VLOPs and VLOSEs
EU Digital Services Act crisis response guide for VLOPs and VLOSEs: Article 36 Commission decisions, Article 48 crisis protocols, mitigation, governance, requests for information, and records.
DSA Dark Patterns: interface design checks for online platforms
Article 25 DSA guidance for reviewing online platform interfaces for deceptive, manipulative, or choice-distorting design patterns.
DSA Enforcement and Penalties in the EU
How Digital Services Act enforcement works: Commission and Digital Services Coordinator roles, VLOP and VLOSE investigations, fines, periodic penalty payments, and evidence readiness.
DSA illegal content notices: what must be included?
A grounded FAQ on EU Digital Services Act illegal-content notices: Article 16 notice elements, acknowledgement, decision notices, trusted flagger priority, statements of reasons, and records.
DSA Marketplace Trader Traceability FAQ
Answer to what EU Digital Services Act Article 30 requires online marketplaces to collect, verify, display, retain, and evidence for trader traceability.
DSA Marketplace Trader Traceability Guide
EU Digital Services Act guide for online marketplaces collecting, checking, displaying, storing, and evidencing trader traceability information.
DSA notice and action plus statements of reasons guide
A grounded Digital Services Act guide for notice intake, moderation decisions, statements of reasons, DSA Transparency Database submission, complaints, appeals, trusted flaggers, and records.
DSA Notice and Action Workflow for Hosting Services and Online Platforms
A grounded DSA notice-and-action workflow covering notice intake, completeness checks, trusted flaggers, decisions, user communications, statements of reasons, appeals, and records.
DSA recommender transparency FAQ: Article 27 and VLOP options
What EU Digital Services Act recommender transparency requires: main parameters, user options, VLOP/VLOSE non-profiling choices, and evidence to keep.
DSA researcher data access for VLOPs and VLOSEs
Article 40 DSA guide to vetted researcher data access for VLOPs and VLOSEs: DSC requests, eligibility checks, amendment grounds, confidentiality, security, and evidence records.
DSA service tier classifier for platforms, marketplaces, VLOPs and VLOSEs
Classify a digital service under the EU Digital Services Act as intermediary, hosting, online platform, marketplace, VLOP or VLOSE, with EU recipient-count evidence and obligation outputs.
DSA statement of reasons FAQ
When DSA statements of reasons are required, what they must contain, when online platforms submit them to the DSA Transparency Database, and what appeal records to keep.
DSA statement of reasons log workflow for online platforms
Build a DSA statement of reasons log for moderation decisions, Transparency Database submission, complaint links, retention, and QA controls.
DSA transparency report template fields and cadence
A source-grounded template outline for Digital Services Act transparency reports, covering applicable service tiers, reporting periods, CSV/XLSX format, retention, statement-of-reasons links, and required evidence tables.
DSA VLOP and VLOSE Risk Assessments and Mitigation Guide
Grounded guide to Digital Services Act systemic risk assessments, mitigation measures, audits, transparency reports, data access, and governance evidence for VLOPs and VLOSEs.
DSA VLOP Audit Pack Workflow: Risk, Mitigation, Audit, and Transparency Records
Build a DSA VLOP or VLOSE audit pack covering Article 34 risk assessments, Article 35 mitigations, independent-audit evidence, transparency reports, data access, and compliance governance.
DSA VLOP Risk Assessment FAQ: Article 34, Mitigation, Audits
What VLOPs and VLOSEs must assess under the EU Digital Services Act, when to reassess, how Article 35 mitigation and annual audit evidence fit together, and what records to keep.
DSA vs DMA Platform Rules
Compare the EU Digital Services Act and Digital Markets Act by scope, designation thresholds, obligations, enforcement, evidence, and practical team ownership.
DSA vs GDPR: online-platform governance and personal-data obligations
Compare the EU Digital Services Act and EU GDPR by scope, ads, recommenders, minors, transparency, complaints, enforcement, and evidence.
DSA vs P2B Regulation: EU platform obligations compared
Compare the EU Digital Services Act with the Platform-to-Business Regulation for platform scope, business-user terms, content moderation, ranking transparency, complaints, enforcement, and evidence.
DSA vs Terrorist Content Online Regulation: notice-and-action vs removal orders
Compare DSA content-governance duties with the EU Terrorist Content Online Regulation removal-order workflow for scope, timing, evidence, authorities, and team ownership.
EU Digital Services Act checklist for platforms and hosting services
A grounded DSA checklist for classifying service tiers, notice-and-action, statements of reasons, complaints, transparency reports, ads, recommenders, trader traceability, VLOP/VLOSE duties, and evidence records.
EU Digital Services Act Compliance Guide
DSA compliance guide for intermediary services, hosting providers, online platforms, marketplaces, and VLOP/VLOSE teams: obligations, controls, and evidence to keep.
EU Digital Services Act FAQ: DSA scope, platform duties, VLOPs, reports, and penalties
Concise EU Digital Services Act FAQ covering intermediary-service scope, active-recipient thresholds, illegal-content notices, statements of reasons, trader traceability, recommender transparency, systemic-risk duties, reporting, penalties, and complaints.
EU Digital Services Act penalties and fines: caps and enforcement roles
DSA penalty caps and enforcement roles: Member State fines, Commission fines for VLOPs and VLOSEs, 1% procedural fines, and 5% periodic penalty payments.
EU Digital Services Act requirements by service tier
Overview of DSA obligations for intermediary services, hosting providers, online platforms, marketplaces, VLOPs and VLOSEs, including notices, complaints, ads, transparency reports, audits, data access and enforcement.
EU Digital Services Act service types and scope
Classify DSA service scope across mere conduit, caching, hosting, online platforms, marketplaces, online search engines, and VLOP/VLOSE threshold duties.
EU DSA deadlines and compliance calendar: application dates, reporting cycles, and VLOP clocks
Calendar view of grounded EU Digital Services Act dates: full application, user-number publication, VLOP/VLOSE designation clocks, statements of reasons, and transparency reporting cycles.
EU DSA Transparency Calendar: reporting, SoR database, AMAR updates
Build a DSA transparency calendar for annual reports, statement-of-reasons database submissions, active-recipient updates, and VLOP/VLOSE audit touchpoints.
EU DSA vs UK Online Safety Act: scope, duties, regulator, and evidence
Compare the EU Digital Services Act and UK Online Safety Act for platform scope, risk assessments, child protection, transparency, regulators, enforcement, and owners.