FAQEU DSA

DSA illegal-content notices Article 16 FAQ

An illegal-content notice under the EU Digital Services Act should identify the specific content, explain why it is alleged to be illegal, give contact and good-faith confirmation details where required, and trigger a documented notice-and-action response.

This page helps separate an Article 16 notice from a general user report, notice, authority order, or ordinary terms complaint.

Author
Sorena AI
Published
May 9, 2026
Updated
Oct 15, 2026
Overview

This FAQ explains what a hosting service or online platform should capture when it receives a notice alleging under Article 16 of the EU Digital Services Act, and how that notice connects to decision notices, statements of reasons, handling, complaint routes, and transparency records.

Search this module

Find a question or answer quickly

3 of 3 questions
Question 1

What must a DSA illegal-content notice contain?

Article 16 requires providers of hosting services to offer easy-to-access, user-friendly electronic mechanisms for notices about specific items of information that a person or entity considers .

means information that is itself unlawful or is unlawful because it relates to an illegal activity, including the sale of products or provision of services that do not comply with EU law or Member State law consistent with EU law. A report alleging only that content violates platform terms is not an Article 16 illegal-content notice unless it also alleges illegality.

A notice gives rise to actual knowledge or awareness for the specific item only when it is precise and substantiated enough for a diligent hosting provider to identify the illegality without a detailed legal examination. That rule does not turn the notice mechanism into a general monitoring duty.

  • Capture the reasoned explanation of why the notifier alleges the information is .
  • Capture the exact electronic location, such as the URL or URLs, plus any content-type-specific details needed to identify the item.
  • Capture the notifier's name and email address unless the Article 16 exception for certain child sexual abuse or exploitation offences applies.
  • Capture the notifier's statement that they believe, in good faith, that the information and allegations are accurate and complete.
  • Record whether the notice is sufficiently precise and adequately substantiated, because only sufficiently specific notices can create actual knowledge or awareness for the specific item.

How should a DSA Article 16 illegal-content notice be handled?

Handle it as a structured notice-and-action record: verify that the notice identifies a specific hosted item, includes a substantiated illegality explanation, gives the exact electronic location, includes required notifier details and good-faith confirmation, then process the notice in a timely, diligent, non-arbitrary, and objective way.

Does every user report become DSA actual knowledge of ?

No. Under the DSA, a notice gives rise to actual knowledge or awareness only for the specific item of information when it allows a diligent hosting provider to identify the illegality without a detailed legal examination.

Can a notifier omit their name and email address?

Usually no. Article 16 requires the notifier's name and email address, but it makes an exception for information considered to involve offences covered by Articles 3 to 7 of Directive 2011/93/EU on child sexual abuse and exploitation. The exception removes those two required fields; it does not reduce the need to identify the content and substantiate the alleged illegality.

Question 2

What must happen after the notice is submitted?

If the notice contains the notifier's electronic contact information, the hosting service must confirm receipt without undue delay and later notify the notifier of the decision on the reported information, including available redress routes.

If automated means are used for processing or decision-making, that use must be disclosed in the decision notification. If the provider restricts content because it is illegal or incompatible with terms, Article 17 may also require a clear and specific statement of reasons to the affected recipient. An Article 9 authority order to act against follows a separate DSA route and should not be processed as an ordinary Article 16 notice.

Article 17 delivery applies only when the provider knows the affected recipient's relevant electronic contact details, and the explanation is due at the latest when the restriction is imposed. Deceptive high-volume commercial content and Article 9 authority orders are excluded from Article 17. Keep that assessment separate from the Article 16 decision message sent to the notifier.

  • Send a receipt acknowledgement without undue delay when electronic contact details are available.
  • Decide the notice in a timely, diligent, non-arbitrary, and objective manner.
  • Tell the notifier the decision and redress possibilities without undue delay.
  • Tell the notifier when automated means were used for processing or decision-making.
  • When restricting content, prepare the Article 17 statement of reasons for the affected recipient, including restriction type, facts and circumstances, legal or contractual ground, automation use where applicable, and redress information.

Does a DSA notice decision also require a statement of reasons?

Often, yes. Article 16 requires the provider to notify the notifier of its decision on the reported information. Separately, Article 17 requires a clear and specific statement of reasons to the affected recipient when the provider removes, disables, demotes, restricts visibility, suspends payments, limits service access, or suspends an account because the recipient's information is or violates terms.

What redress route should be recorded for a DSA illegal-content notice decision?

At minimum, record the redress information sent with the Article 16 decision notification. For online platforms, Article 20 also requires an internal complaint-handling system for at least six months after certain notice and moderation decisions, and Article 17 statements of reasons must include clear redress information.

Question 3

How do trusted flaggers and records change the workflow?

A notice is still submitted through the Article 16 mechanism, but Article 22 requires online platforms to give priority to notices from trusted flaggers acting within their designated area of expertise and to process and decide them without undue delay.

status does not transfer the moderation decision to the flagger. The Commission explains that trusted flaggers notify platforms of content they consider illegal, while providers remain responsible for deciding on notices and removing content where justified.

Check provider-size treatment before applying the additional platform workflows. The Article 19 micro or small enterprise exclusion can remove Article 20 internal complaints, Article 22 trusted-flagger priority and Article 24(5) database submission, subject to its 12-month post-loss and designated-VLOP rules. It does not remove the hosting service's Article 16 notice mechanism or Article 17 duties.

  • Tag whether the notifier is a designated and whether the notice falls within the flagger's area of expertise.
  • Route qualifying notices for priority processing and decision without undue delay.
  • Keep support for any escalation to the awarding Digital Services Coordinator when a submits a significant number of insufficiently precise, inaccurate, or inadequately substantiated notices.
  • For transparency reporting, preserve counts of Article 16 notices by type of alleged , notices, actions taken under law versus terms, automated processing, and median action time.
  • For online platforms, preserve statement-of-reasons submission status and ensure submissions to the Commission database do not contain personal data.

Do DSA notices automatically require content removal?

No. notices receive priority handling when submitted within the flagger's designated expertise, but the provider still decides the notice and removes or restricts content only where justified under law or its terms.

What records should a DSA illegal-content notice file keep?

Keep the notice text and required Article 16 fields, sufficiency assessment, acknowledgement timestamp, review owner, decision and rationale, automation use, notifier decision message, affected-recipient statement of reasons where applicable, redress information, complaint outcome where applicable, status, and transparency-reporting categories.

Recommended next step

Build an Article 16 notice record that links intake, decision, redress, and reporting

Sorena can help convert Article 16 notice fields, trusted flagger routing, statement-of-reasons requirements, and transparency-reporting categories into a reusable moderation operations checklist.

Primary sources

References and citations

eur-lex.europa.eu4 citations
Referenced sections
  • Primary legal source for Article 16 notice-and-action requirements, Article 17 statements of reasons, Article 20 complaints, Article 22 trusted flaggers, and Article 15 transparency records.
  • Article 3(h) defines illegal content, while Article 16 sets the electronic notice mechanism, required notice elements, child-sexual-abuse-field exception, and actual-knowledge test.
  • Articles 16, 17, and 20 support the acknowledgement, decision communication, statement-of-reasons, automation disclosure, and internal complaint-handling points.
Show 1 more
  • Articles 15 and 22 support notice metrics, trusted flagger priority handling, annual trusted flagger reporting, and misuse escalation to the awarding Digital Services Coordinator.
"Notice and action mechanisms"
More quoted passages
"sufficiently precise and adequately substantiated notices"
"notify that individual or entity of its decision"
"notices submitted by trusted flaggers"
digital-strategy.ec.europa.eu2 citations
Referenced sections
  • Commission FAQ explaining statements of reasons, public database submission by online platforms, personal-data exclusion, and database retention context.
  • Explains that Article 17 statements of reasons help users understand and challenge content moderation decisions, and that online platforms submit statements of reasons to the Commission database.
"DSA Transparency Database"
More quoted passages
"clear and specific information, called statements of reasons"
digital-strategy.ec.europa.eu2 citations
Referenced sections
  • Commission source for trusted flagger designation, priority treatment, annual reports, and provider responsibility for notice decisions.
  • Commission explanation of trusted flagger role, designation by national Digital Services Coordinators, EU-wide validity, priority treatment, and provider responsibility for the final decision.
"Trusted flaggers under the Digital Services Act"
More quoted passages
"Providers have the sole responsibility to decide upon notices"
Show all related guides (35)

DSA Applicability Test: classify intermediary services, platforms, marketplaces, VLOPs and VLOSEs

A cited 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 official source evidence.

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 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 source-cited 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 source-cited DSA notice-and-action workflow covering notice intake, completeness checks, trusted flaggers, decisions, user communications, statements of reasons, appeals, and records.

DSA researcher data access for VLOPs and VLOSEs

Article 40 DSA guide to vetted researcher access for VLOPs and VLOSEs under Regulation (EU) 2025/2050: requests, data catalogues, security, deadlines, and 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 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-cited 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 Transparency Reporting Obligations by Provider Tier

A source-cited guide to EU Digital Services Act transparency reports, active-recipient publication, statements-of-reasons submissions, VLOP/VLOSE reports, templates, cadence, and evidence.

DSA VLOP and VLOSE Risk Assessments and Mitigation Guide

A source-cited 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 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

An official source 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 cited 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: reports, statements of reasons and user counts

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.