Compliance GuideEU DSA

Digital Services Act compliance guide

A service-tier guide to DSA controls for intermediary services, hosting providers, online platforms, online marketplaces, and designated VLOPs or VLOSEs.

Use it to assign notice-and-action, complaint handling, statement-of-reasons, transparency reporting, advertising, recommender, trader traceability, risk, audit, and evidence responsibilities.

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

Structured answer sets in this page tree.

Primary sources
9

Cited legal and guidance references.

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

DSA compliance starts with service classification. The same product can contain several covered services, so teams should classify each service surface before assigning controls: intermediary service, hosting service, online platform, online marketplace that lets consumers conclude distance contracts with traders, online search engine, or a Commission-designated very large online platform or very large online search engine. For most services, the main supervisor is the relevant national Digital Services Coordinator, but for designated VLOPs and VLOSEs the European Commission has exclusive supervision and enforcement for systemic-risk obligations. If obligations are missed, the Commission and national authorities can investigate, require changes, and impose sanctions; Commission fines for VLOPs and VLOSEs can reach 6% of the provider's total worldwide annual turnover.

Section 1

Classify the DSA service tier before assigning controls

Build a service inventory around what the product does for recipients in the EU. Intermediary services need baseline governance such as points of contact, terms-and-conditions transparency, and content moderation transparency where moderation occurs. Hosting services add notice-and-action and statements of reasons. Online platforms add user complaint and dispute routes, misuse controls, transparency reporting, advertising and recommender disclosures, and protections for minors where relevant.

Marketplace-style online platforms that let consumers conclude distance contracts with traders need a separate trader file and product-listing control set. VLOPs and VLOSEs are a different tier: the 45 million average-monthly-active-recipient threshold and Commission designation trigger systemic-risk, audit, data-access, compliance-function, ad-repository, and enhanced transparency obligations.

  • Inventory each EU-facing service, user journey, and hosted-content surface separately; do not classify a whole group company once and reuse it for every product.
  • Record whether the service only stores user information, also disseminates it to the public, lets consumers transact with traders, or operates as an online search engine.
  • Keep average monthly active recipient calculations and publication evidence for online platforms and online search engines because those numbers can affect VLOP/VLOSE designation.
  • Escalate products with mixed roles, EU targeting, marketplaces, ads, recommenders, minors, or rapid growth because several DSA control sets may apply at the same time.
Section 2

Run notice-and-action and statements of reasons as evidence-producing workflows

Hosting services need a notice-and-action mechanism that lets people notify specific items they consider illegal. The compliance record should show where the mechanism appears in the product, what information the notice form requests, how notices are routed, how trusted-flagger notices are prioritised when applicable, and how the team decides whether to remove, disable access to, restrict visibility of, or leave content available.

When a hosting provider restricts content or an account because content is illegal or violates terms, the DSA statement-of-reasons process should produce a user notice and, for online platforms, a submission record for the Commission's DSA Transparency Database without personal data. The evidence should connect the moderation decision, legal or terms basis, restriction type, redress route, decision owner, automation status, and database submission status.

  • Keep notice intake logs with URL or content identifiers, allegation category, submitter type, trusted-flagger status, timestamps, triage result, reviewer, and final measure.
  • Keep statement-of-reasons records for removals, visibility restrictions, account suspensions, service restrictions, and monetisation restrictions covered by Article 17.
  • For online platforms, reconcile statement-of-reasons records against DSA Transparency Database submission logs and personal-data scrubbing checks.
  • Measure automation use in moderation so transparency reports can distinguish notices and measures processed solely by automated means from those not processed solely by automated means.
Section 3

Give online-platform users real complaint and redress routes

Online platforms need an internal complaint-handling system for users and notice submitters to challenge moderation decisions covered by Article 20. Access must last at least six months after the decision notice, complaints must be electronic and free of charge, and final complaint decisions must not be made solely by automated means.

The complaint workflow should also surface out-of-court dispute settlement information. Certified bodies can handle disputes about content moderation decisions, including rejected illegal-content notices. Transparency evidence should capture complaint outcomes, reversals, median handling time, out-of-court disputes, and suspensions for manifestly illegal content or manifestly unfounded notices and complaints.

  • Link every appealable moderation decision to a complaint window, complaint channel, user-facing reason, and available redress options.
  • Keep complaint records showing the original decision, complainant category, grounds, reviewer, outcome, reversal reason if any, and notification timestamp.
  • Track out-of-court dispute settlement cases separately from internal complaints, including body selected, result, whether the platform implemented the decision, fees, and timing.
  • Define misuse policies for repeated manifestly illegal content and repeated manifestly unfounded notices or complaints before suspending users or notice processing.
Section 4

Control ads, recommender systems, minors, and marketplace traders

Online platforms that show ads need real-time ad labels and disclosures for the person on whose behalf the ad is presented, the payer if different, and meaningful targeting parameters. Platforms with recommender systems need plain-language terms describing main parameters and any user options to modify or influence them. Platforms accessible to minors need proportionate privacy, safety, and security measures and must not use profiling-based advertising to minors when they know with reasonable certainty that the recipient is a minor.

Marketplaces that let EU consumers conclude distance contracts with traders should treat trader traceability as an onboarding gate. Before a trader can offer products or services, the platform should collect and assess trader identity, contact, payment account, register details where applicable, and a self-certification to offer only products or services compliant with EU law. Listing interfaces should let traders provide required pre-contractual, product-safety, compliance, labelling, and marking information.

  • Keep ad-rendering evidence showing label placement, sponsor, payer, targeting-parameter disclosure, and user access to parameter controls.
  • Keep recommender-system records with the main ranking parameters, user-facing explanations, available user choices, and testing evidence for each relevant surface.
  • For services accessible to minors, keep design reviews, age-signal assumptions, profiling-ad controls, safety measures, and residual-risk decisions.
  • For marketplaces, keep trader due-diligence files, reliability checks against official or reliable sources, trader correction requests, suspensions, and product-listing compliance checks.
Section 5

Prepare VLOP and VLOSE evidence before designation pressure arrives

A platform or search engine at or above 45 million average monthly active recipients in the EU can be designated by the Commission as a VLOP or VLOSE. Once designated, the service must treat DSA compliance as a systemic-risk governance programme, not only a content moderation process. Risk assessments must cover illegal content, fundamental-rights effects, civic discourse and elections, public security, public health, minors, gender-based violence, and physical or mental wellbeing where relevant.

VLOP/VLOSE evidence should be ready for regulator requests, independent audits, public reporting, and vetted researcher access. The record should include risk assessments, mitigation measures, management-body review, independent compliance function materials, annual audit reports, audit implementation reports, ad repository controls, non-profiling recommender options, data-access procedures, and Article 42 transparency report inputs.

  • Preserve supporting documents for systemic-risk assessments for at least three years and be able to provide them to the Commission or Digital Services Coordinator on request.
  • Run mitigation tracking for content moderation, recommender systems, advertising systems, interface design, trusted-flagger cooperation, out-of-court dispute implementation, child-safety tools, and manipulated-media markings where applicable.
  • Plan annual independent audits and a one-month audit implementation report process for any audit report that is not positive.
  • Publish VLOP/VLOSE reports and public versions of risk, mitigation, audit, and audit implementation materials within the DSA timing rules, while managing confidential information.
Section 6

Minimum DSA compliance evidence pack

A useful DSA evidence pack should be organised by service tier, not by department. Legal can own interpretation, but product, trust and safety, marketplace operations, ads, data science, engineering, support, and compliance teams need retrievable records for the controls they run.

Do not keep only policy text. Keep operational proof: live interface captures, form schemas, moderation samples, complaint outcomes, database submission logs, report workpapers, trader files, recommender and ad configuration records, risk registers, audit materials, and management approvals.

What is the first DSA compliance step for an EU-facing digital service?

Classify each service surface by DSA tier before assigning controls. A hosting service, online platform, marketplace, search engine, and designated VLOP or VLOSE have different obligations, and a single product can contain more than one covered service.

What evidence should a DSA notice-and-action workflow keep?

Keep the notice, content identifier, allegation, submitter type, trusted-flagger status if applicable, triage timestamp, reviewer, decision, measure taken or not taken, user notice, statement of reasons, redress information, and Transparency Database submission status for online platforms.

When do VLOP and VLOSE obligations become a separate DSA workstream?

They become a separate workstream when an online platform or search engine reaches the 45 million average monthly active recipient threshold in the EU and is designated by the Commission, after which systemic-risk, audit, data-access, compliance-function, ad-repository, and enhanced reporting duties apply.

  • Service classification memo covering EU targeting, service category, user roles, online-platform status, marketplace status, search status, AMAR calculations, and VLOP/VLOSE escalation triggers.
  • Content moderation register covering notices, trusted-flagger routing, orders, own-initiative moderation, statements of reasons, automation use, user notifications, and database submissions.
  • User redress register covering internal complaints, out-of-court disputes, court-route disclosures, reversals, median times, and misuse suspensions.
  • Transparency reporting workpapers covering Article 15, Article 24, and, where designated, Article 42 tables, including automated-moderation accuracy and language-specific staffing data where required.
  • Marketplace and product-safety files covering trader identity, reliability checks, self-certifications, product and service listing fields, illegal-product notices, consumer notifications, and post-relationship deletion timing.
  • VLOP/VLOSE governance files covering annual risk assessment, mitigation testing, independent audits, audit implementation reports, compliance-function reporting, ad repository controls, researcher data access, and management-body review.
Primary sources

References and citations

digital-strategy.ec.europa.eu
Referenced sections
  • Commission source explaining that users can contest platform moderation decisions through internal complaints, certified dispute bodies, or courts.
"Users can contest moderation decisions"
digital-strategy.ec.europa.eu
Referenced sections
  • Commission FAQ explaining that hosting services issue statements of reasons and online platforms send them to the DSA Transparency Database.
"all providers of hosting services"
digital-strategy.ec.europa.eu
Referenced sections
  • Commission overview naming covered service examples such as marketplaces, social networks, app stores, and travel or accommodation platforms.
"marketplaces, social media networks, app stores"
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 Transparency Reporting Obligations by Provider Tier
A grounded 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
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 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.