| Scope boundary | Intermediary services, hosting services, online platforms, online marketplaces, and very large online platforms or search engines, depending on the service feature and DSA tier. | Hosting service providers in relation to terrorist content covered by the TCO Regulation and removal orders issued by competent authorities. | 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. |
|---|
| Covered actors | 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. | 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. | Treat user notices and authority orders as different intake types even when they concern the same item of content. |
|---|
| Trigger | 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. | 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. | 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. |
|---|
| Core obligations | 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. | TCO has its own notification and complaint context around removed or disabled terrorist content, subject to the Regulation's safeguards and authority constraints. | Use separate message templates: DSA statements of reasons are not automatically sufficient for a TCO removal-order notice or complaint record. |
|---|
| Evidence record | 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. | TCO records should show the removal order, issuing authority, receipt time, deadline, content identifier, action taken, evidence-preservation decision, complaint handling, and authority correspondence. | 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. |
|---|
| Timing and deadlines | Digital Services Coordinators supervise DSA matters at Member State level, with the Commission directly supervising designated VLOPs and VLOSEs for the enhanced duties. | Competent authorities under the TCO Regulation issue removal orders and handle related authority communications. | Route authority correspondence by legal framework so a DSA supervisory inquiry and a TCO removal order do not land in the same unresolved queue. |
|---|
| Enforcement | A platform or search engine with more than 45 million monthly users in the EU can be designated as a VLOP or VLOSE and must manage enhanced DSA risks, audits, data access, advertising, recommender, and transparency obligations. | TCO does not become a VLOP/VLOSE risk program; it remains a removal-order and terrorist-content workflow even for very large services. | Use VLOP/VLOSE governance to test moderation-system resilience, but keep a separate TCO incident log for each authority order. |
|---|
| Overlap and reuse | DSA ownership usually spans legal, trust and safety, policy, product, marketplace operations, transparency reporting, data governance, and VLOP/VLOSE risk owners where applicable. | 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. | Name two accountable owners: one for DSA governance and reporting, and one for TCO removal-order execution and evidence retrieval. |
|---|
| Practical decision rule | Intermediary services, hosting services, online platforms, online marketplaces, and very large online platforms or search engines, depending on the service feature and DSA tier. | Hosting service providers in relation to terrorist content covered by the TCO Regulation and removal orders issued by competent authorities. | 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. |
|---|