Separate the DSA's general content-governance duties from the Terrorist Content Online Regulation's removal-order workflow for hosting services.
This comparison helps route notices, authority orders, user explanations, evidence preservation, transparency reporting, and escalation ownership without merging two different legal tests.
The Digital Services Act and Terrorist Content Online Regulation can both govern one moderation event, but the trigger and clock differ. Use the DSA for the hosting service's general notice-and-action, explanation, complaint, transparency, and systemic-risk duties. Use Regulation (EU) 2021/784, which has applied since 7 June 2022, when a competent authority issues a : the provider must remove the identified content or disable access in all Member States as soon as possible and within one hour of receipt, subject to the Regulation's impossibility, clarification, review, and redress safeguards.
Side-by-side comparison
DSA vs Terrorist Content Online Regulation
Use these rows to decide which regime controls the work, what evidence proves compliance, and which team should own the next action.
Horizontal EU framework for intermediary services, including hosting and online platforms. It governs content-moderation process design, user-facing explanations, complaint routes, transparency reporting, and systemic-risk governance for very large services.
Second framework
Terrorist Content Online Regulation
Targeted EU framework for hosting service providers that receive terrorist-content removal orders. It requires an authority-order workflow, fast action, evidence preservation, complaint handling, and competent-authority communication.
Intermediary services, hosting services, online platforms, online marketplaces, and very large online platforms or search engines, depending on the service feature and DSA tier.
Primary TCO text for hosting service providers and terrorist-content removal orders.
hosting service providers
A service can be in DSA scope without receiving TCO removal orders; TCO readiness becomes critical when the service hosts user content and may receive authority orders.
A DSA workflow is triggered by the service tier, user notices, trusted flagger notices, own-initiative moderation, user complaints, transparency-report cycles, or VLOP/VLOSE designation.
Primary DSA text for notice-and-action, complaints, trusted flaggers, transparency reports, and VLOP/VLOSE obligations.
notice and action
A TCO workflow is triggered by a competent-authority removal order, and may also require follow-up around preservation, complaint handling, and specific measures where the Regulation applies.
DSA timing depends on the obligation: notices and complaints need prompt operational handling, statements of reasons follow moderation restrictions, transparency reports follow reporting cycles, and VLOP/VLOSE duties follow designation and recurring risk-governance work.
Commission source for statement-of-reasons submission and transparency database workflow.
statements of reasons
TCO removal orders are incident-speed work; the regulation is designed around removal or disabling of access within one hour after receipt of a valid removal order.
Primary TCO text for the one-hour removal or disabling expectation after receipt of a removal order.
within one hour
A daily or weekly DSA moderation review cadence is not enough for TCO; the removal-order channel needs on-call coverage and timestamped deadline calculation.
The DSA requires hosting providers to provide clear statements of reasons when they restrict user content, and online platforms must support internal complaint handling for covered moderation decisions. Article 19 excludes qualifying micro and small platform providers from the Section 3 complaint duties, with a 12-month continuation after loss of status, except for designated VLOPs; it does not remove hosting duties under Article 17.
Commission source explaining DSA statements of reasons and Article 24(5) database submission by online platforms.
clear and specific information
TCO has its own notification and complaint context around removed or disabled terrorist content, subject to the Regulation's safeguards and authority constraints.
DSA records should show service classification, notice source, moderation facts, legal or terms basis, statement of reasons, complaint outcome, transparency-report metrics, and VLOP/VLOSE risk evidence where applicable.
Primary DSA text for moderation, statement, complaint, reporting, and risk-assessment records.
content moderation
TCO records should show the authenticated removal order, issuing authority, receipt time, deadline, exact content locator, action in all Member States, authority response, six-month preservation period or extension, content-provider notice, complaint handling, cross-border scrutiny, and court correspondence.
Primary TCO text for removal-order records, evidence preservation, complaints, and authority communication.
preservation
Shared moderation tooling is acceptable only if it exports a record that preserves the legal basis, authority source, timestamp, action, reviewer, and appeal or complaint route.
Digital Services Coordinators supervise DSA matters at Member State level, with the Commission directly supervising designated VLOPs and VLOSEs for the enhanced duties.
A platform or search engine with average monthly active recipients in the Union equal to or higher than 45 million can be designated as a VLOP or VLOSE and must then manage enhanced DSA risks, audits, data access, advertising, recommender, and transparency obligations.
DSA ownership usually spans legal, trust and safety, policy, product, marketplace operations, transparency reporting, data governance, and VLOP/VLOSE risk owners where applicable.
Primary DSA text for the obligations that drive cross-functional ownership.
terms and conditions
TCO ownership needs legal escalation, trust-and-safety operations, incident response, authority-response owners, and engineering support for fast removal, disabling, preservation, and audit logging.
Intermediary services, hosting services, online platforms, online marketplaces, and very large online platforms or search engines, depending on the service feature and DSA tier.
Primary TCO text for hosting service providers and terrorist-content removal orders.
hosting service providers
Operational implication
A service can be in DSA scope without receiving TCO removal orders; TCO readiness becomes critical when the service hosts user content and may receive authority orders.
Supports the TCO removal-order side of the implication.
removal orders
Workflow triggers
Digital Services Act
A DSA workflow is triggered by the service tier, user notices, trusted flagger notices, own-initiative moderation, user complaints, transparency-report cycles, or VLOP/VLOSE designation.
Primary DSA text for notice-and-action, complaints, trusted flaggers, transparency reports, and VLOP/VLOSE obligations.
notice and action
Terrorist Content Online Regulation
A TCO workflow is triggered by a competent-authority removal order, and may also require follow-up around preservation, complaint handling, and specific measures where the Regulation applies.
Supports separate authority-order intake for terrorist-content removal orders.
removal order
Timing and deadlines
Digital Services Act
DSA timing depends on the obligation: notices and complaints need prompt operational handling, statements of reasons follow moderation restrictions, transparency reports follow reporting cycles, and VLOP/VLOSE duties follow designation and recurring risk-governance work.
Commission source for statement-of-reasons submission and transparency database workflow.
statements of reasons
Terrorist Content Online Regulation
TCO removal orders are incident-speed work; the regulation is designed around removal or disabling of access within one hour after receipt of a valid removal order.
Primary TCO text for the one-hour removal or disabling expectation after receipt of a removal order.
within one hour
Operational implication
A daily or weekly DSA moderation review cadence is not enough for TCO; the removal-order channel needs on-call coverage and timestamped deadline calculation.
Supports incident-speed ownership and timestamped evidence for TCO removal orders.
one hour
Core obligations
Digital Services Act
The DSA requires hosting providers to provide clear statements of reasons when they restrict user content, and online platforms must support internal complaint handling for covered moderation decisions. Article 19 excludes qualifying micro and small platform providers from the Section 3 complaint duties, with a 12-month continuation after loss of status, except for designated VLOPs; it does not remove hosting duties under Article 17.
Commission source explaining DSA statements of reasons and Article 24(5) database submission by online platforms.
clear and specific information
Terrorist Content Online Regulation
TCO has its own notification and complaint context around removed or disabled terrorist content, subject to the Regulation's safeguards and authority constraints.
Supports keeping TCO notification and complaint handling distinct.
removal order
Evidence record
Digital Services Act
DSA records should show service classification, notice source, moderation facts, legal or terms basis, statement of reasons, complaint outcome, transparency-report metrics, and VLOP/VLOSE risk evidence where applicable.
Primary DSA text for moderation, statement, complaint, reporting, and risk-assessment records.
content moderation
Terrorist Content Online Regulation
TCO records should show the authenticated removal order, issuing authority, receipt time, deadline, exact content locator, action in all Member States, authority response, six-month preservation period or extension, content-provider notice, complaint handling, cross-border scrutiny, and court correspondence.
Primary TCO text for removal-order records, evidence preservation, complaints, and authority communication.
preservation
Operational implication
Shared moderation tooling is acceptable only if it exports a record that preserves the legal basis, authority source, timestamp, action, reviewer, and appeal or complaint route.
Supports separate record fields for authority orders and preservation.
evidence
Authorities
Digital Services Act
Digital Services Coordinators supervise DSA matters at Member State level, with the Commission directly supervising designated VLOPs and VLOSEs for the enhanced duties.
A platform or search engine with average monthly active recipients in the Union equal to or higher than 45 million can be designated as a VLOP or VLOSE and must then manage enhanced DSA risks, audits, data access, advertising, recommender, and transparency obligations.
DSA ownership usually spans legal, trust and safety, policy, product, marketplace operations, transparency reporting, data governance, and VLOP/VLOSE risk owners where applicable.
Primary DSA text for the obligations that drive cross-functional ownership.
terms and conditions
Terrorist Content Online Regulation
TCO ownership needs legal escalation, trust-and-safety operations, incident response, authority-response owners, and engineering support for fast removal, disabling, preservation, and audit logging.
Use the DSA track for service classification, notice-and-action design, statements of reasons, internal complaints, transparency reporting, trusted flagger handling, and VLOP/VLOSE systemic-risk governance.
Use the TCO track for competent-authority removal orders, one-hour response readiness, evidence preservation, TCO complaint handling, and authority communication.
Reuse moderation tooling only when each exported record identifies the legal basis, trigger source, authority or notice sender, timestamp, action, reviewer, notification status, and complaint route.
Escalate immediately when a moderation item is both a DSA content decision and a TCO authority order, because the TCO clock and evidence duties are separate.
Primary TCO text for the terrorist-content removal-order side of the decision rule.
terrorist content online
1
Section 1
Use the DSA for content-governance design, not as a substitute for removal-order readiness
A DSA notice can tell a hosting provider that a user or trusted flagger believes content is illegal. A is different: it is an authority order under a separate Regulation and needs a response workflow that can authenticate the order, verify the addressee and deadline, locate the exact content, remove it or disable access in all Member States, preserve the required material, notify the authority, and record what was done.
The Terrorist Content Online (TCO) Regulation covers hosting services that store and disseminate user-provided material to the public at the content provider's request and have a substantial connection to the EU. It does not cover mere conduit or caching services, infrastructure layers that do not store the material, email or private messaging, or cloud infrastructure that is not used to make stored material public at the content provider's direct request. A social network, public video or image-sharing service, public file-sharing service, or public-facing cloud feature can be in scope; classify each service surface on its actual use.
One moderation queue is not enough. DSA notice-and-action records, statement-of-reasons templates, and complaint outcomes are useful evidence, but they do not prove that the service can receive and execute a within the required clock.
Keep DSA notices, DSA own-initiative moderation, and TCO removal orders as separate intake categories.
Require every moderation record to show the legal basis, source of the trigger, reviewer, action, timestamp, user notice status, and appeal or complaint route.
Escalate authority orders to legal and trust-and-safety operations immediately; do not wait for ordinary DSA complaint or transparency-report cycles.
For the first removal order from an authority, expect information about procedures and deadlines at least 12 hours in advance unless the authority identifies a duly justified emergency. The one-hour clock still runs from receipt of the order.
Primary DSA text for intermediary-service classifications, notice-and-action mechanisms, statements of reasons, complaint handling, transparency reporting, and VLOP/VLOSE systemic-risk duties.
Primary TCO text for hosting-service removal orders, one-hour action expectations, preservation duties, complaint handling, and competent-authority communication.
terrorist content online
2
Section 2
Evidence should prove which regime controlled the action
For DSA moderation, evidence normally starts with service classification, terms-and-conditions rules, notice intake, moderation decision facts, statement-of-reasons delivery, internal complaint outcomes, transparency-report inputs, and any very large online platform (VLOP) or very large online search engine (VLOSE) risk-assessment material.
For TCO, the minimum useful record is different: the removal order, authenticated receiving channel, authority details, receipt timestamp, exact URL or other locator, deadline calculation, removal or disabling action across Member States, response to the authority, preservation period, content-provider notification handling, complaint handling, and any cross-border scrutiny or court challenge.
Preserve removed terrorist content and related data needed for review, complaints, or terrorism investigations for six months. A competent authority or court may request a further specified period when relevant proceedings are still underway. If force majeure or a de facto impossibility prevents action, or the order has manifest errors or insufficient information, notify the issuing authority without undue delay using the Regulation's process; do not silently treat the order as an ordinary moderation ticket.
Do not cite a DSA statement of reasons as the only evidence for a TCO removal order.
Do not bury TCO authority correspondence inside ordinary user-notice queues.
Use shared tooling only if the exported record keeps the DSA and TCO legal bases separate.
For a cross-border order, preserve the ability to reinstate content. The provider or content provider may request scrutiny by the authority in the provider's Member State of main establishment within 48 hours, but that safeguard does not pause the one-hour action requirement.
Commission FAQ explaining Article 17 statements of reasons and Article 24(5) submission of online-platform statements to the DSA Transparency Database.
Primary TCO text for records linked to removal orders, evidence preservation, complaints, and authority notices.
removal orders
3
Section 3
Authorities and ownership should stay separate
The DSA supervision model uses Digital Services Coordinators, the European Commission, and the European Board for Digital Services, with direct Commission supervision for designated VLOPs and VLOSEs. That points ownership toward legal, trust and safety, policy, product, compliance, transparency reporting, data governance, and risk teams.
The TCO workflow needs an incident-style owner as well as legal oversight. The receiving team must be able to authenticate the authority channel, act on the content, preserve required records, respond to complaints, and brief leadership without disrupting ordinary DSA user-notice and complaint operations.
Assign one accountable owner for DSA service classification and transparency reporting.
Assign a separate on-call owner for TCO removal-order intake, verification, action logging, and authority response.
Give product and engineering owners shared responsibility for moderation tooling fields that both regimes need, such as timestamps, action type, legal basis, and reviewer identity.
Primary TCO text for competent-authority removal orders and provider response duties.
competent authorities
4
Section 4
Very large service duties add governance, not a replacement for TCO
Platforms and search engines with average monthly active recipients in the Union equal to or higher than 45 million can be designated as VLOPs or VLOSEs and then face additional DSA obligations, including systemic-risk assessment, mitigation, independent audit, advertising and recommender-system transparency, and researcher data-access duties.
Those duties can improve terrorist-content risk governance, especially where content moderation systems or recommender systems amplify illegal content. They still do not replace the separate TCO order-handling workflow: a VLOP risk file and a removal-order action log answer different questions.
TCO can also require a separate prevention workstream. When a competent authority establishes that a hosting provider is exposed to terrorist content, Article 5 requires the provider to take specific measures that are diligent, proportionate, non-discriminatory, and protective of fundamental rights. The provider chooses the measures, and the authority cannot impose a general monitoring obligation or require automated tools. If the provider took or was required to take TCO action during a calendar year, Article 7 requires a public transparency report before 1 March of the following year.
Use VLOP/VLOSE risk assessment to evaluate content-moderation process risks, automation, resourcing, and escalation gaps.
Use the TCO register to prove receipt, action, preservation, complaint handling, and authority communication for each removal order.
Review both workstreams after material product launches, moderation automation changes, new EU market entries, or authority escalations.
Articles 5 and 7 support the authority exposure decision, provider-selected specific measures, safeguards against general monitoring and mandatory automation, and the annual transparency report deadline.
before 1 March of the following year
5
Section 5
Terrorist content is a defined category, not a label for controversial speech
The TCO Regulation covers material that meets its definition of terrorist content, including material that incites or solicits terrorist offences, solicits participation in a terrorist group, provides instruction for terrorist offences, or threatens a terrorist offence under the stated conditions. The order must explain why the identified material qualifies and provide an exact URL plus any other information needed to locate it.
Material disseminated to the public for educational, journalistic, artistic, research, or terrorism-prevention purposes is not terrorist content under the Regulation when that is its true purpose. Polemic or controversial views in public debate are not enough on their own. Preserve the authority's classification and the content context instead of asking moderators to infer terrorist status from a topic, speaker, or keyword.
Check the order's legal basis, statement of reasons, content locator, timestamp, authentication, and redress information.
Keep contextual evidence needed for a complaint, cross-border scrutiny, or judicial review, subject to access controls and the six-month preservation rule.
Do not use TCO handling to bypass the DSA explanation and complaint duties that independently apply to the service's own moderation decision.
Articles 1 to 3 define the scope and terrorist-content category, exclude genuine educational, journalistic, artistic, research, and counter-terrorism material, and specify the required contents of a removal order.
shall not be considered to be terrorist content
Recommended next step
Build a two-track evidence workflow
Sorena can help turn this comparison into intake categories, owner assignments, required evidence fields, escalation rules, and cited-source review steps for DSA and terrorist-content operations.
Primary legal source for terrorist-content removal orders, hosting-provider response duties, evidence preservation, complaint handling, and competent-authority communication.
Primary TCO text for hosting-service removal orders, one-hour action expectations, preservation duties, complaint handling, and competent-authority communication.
Primary TCO text for records linked to removal orders, evidence preservation, complaints, and authority notices.
Show 20 more
Primary TCO text for competent-authority removal orders and provider response duties.
Articles 5 and 7 support the authority exposure decision, provider-selected specific measures, safeguards against general monitoring and mandatory automation, and the annual transparency report deadline.
Articles 1 to 3 define the scope and terrorist-content category, exclude genuine educational, journalistic, artistic, research, and counter-terrorism material, and specify the required contents of a removal order.
Primary TCO text for hosting service providers and terrorist-content removal orders.
Supports the TCO removal-order side of the implication.
Primary TCO text for competent-authority removal orders and related follow-up duties.
Supports separate authority-order intake for terrorist-content removal orders.
Primary TCO text for the one-hour removal or disabling expectation after receipt of a removal order.
Supports incident-speed ownership and timestamped evidence for TCO removal orders.
Primary TCO text for user-notification and complaint-related safeguards connected to removal orders.
Supports keeping TCO notification and complaint handling distinct.
Primary TCO text for removal-order records, evidence preservation, complaints, and authority communication.
Supports separate record fields for authority orders and preservation.
Primary TCO text for competent authorities and removal-order communication.
Supports TCO authority-routing records.
Primary TCO text for removal-order duties that apply independently from DSA VLOP/VLOSE designation.
Supports retaining a separate TCO order log.
Primary TCO text for the duties that require legal, operational, and technical order-response ownership.
Supports separate TCO execution ownership.
Primary TCO text for the terrorist-content removal-order side of the decision rule.
Primary legal source for DSA intermediary-service tiers, notice-and-action, statements of reasons, complaint handling, transparency reporting, authorities, and VLOP/VLOSE governance.
Primary DSA text for intermediary-service classifications, notice-and-action mechanisms, statements of reasons, complaint handling, transparency reporting, and VLOP/VLOSE systemic-risk duties.
Primary DSA text for VLOP/VLOSE systemic-risk assessment, mitigation, audit, and transparency obligations.
Show 9 more
Primary DSA text for service definitions and tiered obligations.
Supports the DSA service-classification side of the implication.
Primary DSA text for notice-and-action, complaints, trusted flaggers, transparency reports, and VLOP/VLOSE obligations.
Supports separating DSA notice intake from other moderation triggers.
Primary DSA text for moderation, statement, complaint, reporting, and risk-assessment records.
Supports record fields needed for DSA moderation decisions.
Primary DSA text for the obligations that drive cross-functional ownership.
Supports separate DSA governance ownership.
Primary DSA text for the DSA side of the decision rule.
Commission explanation of DSA statement-of-reasons records and online-platform submission to the public DSA Transparency Database.
Commission FAQ explaining Article 17 statements of reasons and Article 24(5) submission of online-platform statements to the DSA Transparency Database.
Commission source for statement-of-reasons submission and transparency database workflow.
Show 2 more
Commission source explaining DSA statements of reasons and Article 24(5) database submission by online platforms.
Supports keeping DSA statements of reasons distinct from other removal-order communications.