A DSA statement of reasons is the explanation Article 17 of the Digital Services Act requires a hosting service to give a user whenever it restricts their content or account because the content is illegal or breaks its terms. It must say what you did, why, on what legal or contractual ground, whether automation was involved, and how the user can challenge it. Online platforms that are not micro or small enterprises must also submit each statement, without personal data, to the Commission's DSA Transparency Database.
This guide covers when a statement is required, what it must contain, the database, and how complaints and out-of-court dispute settlement fit in. It is general information, not legal advice.
When DSA Article 17 requires a statement of reasons
Article 17 applies to every hosting service, regardless of size. You must provide a clear and specific statement of reasons to each affected user for any of these restrictions, imposed on the ground that the information is illegal or incompatible with your terms:
- restricting visibility of content: removal, disabling access, or demotion
- suspending, terminating or restricting monetary payments
- suspending or terminating the service in whole or in part
- suspending or terminating the user's account
Demotion and demonetisation are easy to forget. If you quietly push a creator's uploads down your rankings or freeze their earnings because of a rule breach, that is a restriction that needs a statement.
The duty applies only where you know the user's relevant electronic contact details, and it does not apply to deceptive high-volume commercial content such as spam. You must provide the statement at the latest when the restriction is imposed, whether the decision came from a notice, as described in our guide to DSA notice and action, or from your own moderation.
What a statement of reasons must contain
Article 17(3) of the DSA lists the minimum content:
- what the decision involves: removal, disabling, demotion or another restriction, and where relevant its territorial scope and duration
- the facts and circumstances relied on, including, where relevant, whether the decision followed a notice or your own voluntary investigation, and, where strictly necessary, the identity of the notifier
- whether automated means were used, including whether the content was detected or the decision made automatically
- where the decision concerns allegedly illegal content, the legal ground relied on and why the content is considered illegal on that ground
- where the decision is based on your terms, the contractual ground relied on and why the content is considered incompatible with it
- clear and user-friendly information on redress: your internal complaint system, out-of-court dispute settlement and judicial redress
The statement must be clear and easily comprehensible, and precise enough for the user to exercise their right to challenge it.
Example statement
We have removed your video [title/ID] from our service in all countries, on 12 October 2026. A user reported it on 11 October 2026. Our moderation team reviewed it manually and found that it breaches section 4.2 of our Terms of Service, which requires written consent records for every performer shown. We did not receive those records when requested. No automated system was used to make this decision. You can appeal through our complaints form within six months. You may also refer the dispute to a certified out-of-court dispute settlement body, or go to court.
That illustrative template names the action, scope, date, trigger, ground, the role of automation and the redress options. Build a small set of templates by category and fill the specifics per case.
DSA transparency database submission
Article 24(5) requires providers of online platforms to submit their Article 17 decisions and statements, without undue delay, to the DSA Transparency Database run by the Commission. It is public and machine-readable, and the submissions must not contain personal data. Platforms submit through an API or a web form; the database's own documentation explains onboarding.
Who submits, and who does not:
| Provider | Statement to user (Art 17) | Database submission (Art 24(5)) |
|---|---|---|
| Hosting service, not an online platform | Yes | No |
| Online platform, micro or small enterprise | Yes | No (Article 19 exemption) |
| Online platform, medium or large | Yes | Yes |
| Very large online platform | Yes | Yes |
DSA internal complaint handling and dispute settlement
Article 20 requires online platforms to give users access, for at least six months after a decision, to an effective internal complaint-handling system that is electronic and free of charge. Complaints must be handled in a timely, non-discriminatory, diligent and non-arbitrary way, decisions must not be taken solely by automated means, and you must reverse decisions without undue delay where the complaint shows they were wrong.
Article 21 lets users take disputes to certified out-of-court dispute settlement bodies. Platforms must engage in good faith, and if the body decides in the user's favour, the platform pays the fees.
Both duties sit in the online platform section, so micro and small platforms are exempt. Many still offer a basic appeal route, because a statement of reasons must point to whatever redress exists and a simple appeal process reduces chargebacks, social media complaints and legal threats from creators who lose access to income. Our guide to a content moderation policy for adult platforms shows how to wire appeals into your policy.
Content removal explanation under the DSA: practical tips
- Cite the exact rule. "Breach of our terms" is not specific enough. Name the clause.
- Do not over-share. Only identify the notifier where strictly necessary, and never where it could put them at risk, as with intimate image complaints.
- Record the statement. Keep a copy with the moderation log; it feeds your transparency figures.
- Handle bans carefully. Account terminations hit creators' livelihoods. Users on the receiving end, as in our guide to an OnlyFans account ban, look first for exactly this explanation.
Frequently asked questions
Do I need a statement of reasons for spam removal?
Not for deceptive high-volume commercial content, which Article 17 excludes. Ordinary rule breaches by real users, however minor, still need one if you have their contact details.
Can the statement be sent automatically?
Yes. Sending is often automated; what matters is that the content is specific to the case, accurate about whether automation was used to detect or decide, and includes the redress options.
What if the restriction applies only in some countries?
Say so. The statement must state the territorial scope, for example "unavailable in France and Germany following a national legal requirement", and the legal ground for each.
Does a statement of reasons go to the person who reported the content?
No. The statement goes to the user whose content or account was restricted. The reporter receives a separate notification of your decision under Article 16.
Next steps
Draft templates for your five most common restrictions and test them against the Article 17(3) list. Then check whether you also owe a transparency report in our guide to DSA transparency report requirements, and see the wider picture in our Digital Services Act guide.