DSA Transparency Database: who must submit statements of reasons and how
Online platforms submit every statement of reasons under Art. 17 DSA to a public database run by the Commission. This guide covers who has to, how to register, when the webform or the API fits, and why personal data must stay out.
When your app removes content or suspends an account, you send the affected user a statement of reasons under Art. 17 DSA. If your app is an online platform, the same decision also goes to the Commission’s DSA Transparency Database, where anyone can search it.
What the database is and what goes in
Art. 24(5) DSA reads:
Providers of online platforms shall, without undue delay, submit to the Commission the decisions and the statements of reasons referred to in Article 17(1) for the inclusion in a publicly accessible machine-readable database managed by the Commission. Providers of online platforms shall ensure that the information submitted does not contain personal data.
So every decision that triggers a statement of reasons under Art. 17 is submitted: removing, disabling or demoting content, suspending payments, suspending or terminating accounts. According to the Commission’s Q&A, the database is public and machine-readable; anyone can search, read and download statements of reasons.
An entry mirrors the mandatory details of Art. 17(3). The API documentation lists these required fields, among others:
| Field | Meaning |
|---|---|
decision_visibility, decision_monetary, decision_provision, decision_account |
type of restriction, at least one |
decision_ground |
illegal content or breach of terms and conditions |
category |
category of the violation |
content_type |
type of content, such as text or image |
decision_facts |
the facts in plain words |
source_type |
what triggered it: a notice, own initiative and so on |
automated_detection, automated_decision |
use of automated means |
territorial_scope |
where the restriction applies |
content_date, application_date |
date of the content and of the measure |
puid |
unique identifier of the entry on your platform |
What a good statement contains is covered in the guide on statements of reasons under Art. 17 DSA.
Who has to submit
The duty applies to online platforms: hosting services that disseminate user content to the public. An app that only stores private notes is a hosting service but not a platform. Where the line runs is explained in Hosting service or online platform?
Exempt are micro and small enterprises (Art. 19(1) DSA), meaning fewer than 50 staff and no more than EUR 10 million in turnover or balance sheet total. Two details:
- If you grow out of that status, the exemption continues for 12 months (Art. 19(1), second sentence).
- Very large online platforms are never exempt (Art. 19(2)).
The Commission’s onboarding documentation also makes clear that each online platform is registered separately, even when one provider runs several. Three community apps mean three registrations.
Onboarding through your Digital Services Coordinator
You do not get access from the Commission directly but through the Digital Services Coordinator (DSC) of your Member State. The onboarding documentation describes two ways in:
- Contact your DSC directly.
- Fill in the EU survey on Art. 24(5) DSA. Your DSC then contacts you with the details.
After that:
- You get access to a sandbox to test your submissions.
- You need two EU Login accounts per platform: one for the sandbox, one for production. The email addresses should be platform-specific rather than personal, and differ between the two environments.
- Once your tests pass, your DSC moves you to production.
The Commission keeps a list of Digital Services Coordinators.
Webform or API
The Commission says you can submit “via either the webform or the API, according to your technical capabilities”.
The webform is fine if you make a handful of decisions a month. You type each statement in by hand. At higher volume it becomes a source of errors.
The API is meant for everything else:
- You generate a token in your profile and send it as
Authorization: Bearer …. A new token invalidates the old one. - Single entries go to
/api/v1/statement, several to/api/v1/statements, up to 100 per call. - If one entry in a batch is invalid, none are created. You resend the whole batch.
- The
puidmay only contain letters, digits, hyphens and underscores, and must be unique on your platform.
Build in retries and record for each decision whether and when it was submitted. Otherwise you will not know what is missing when your coordinator asks.
No personal data
The second sentence of Art. 24(5) is strict: the information submitted must not contain personal data. The API documentation repeats this, and the responsibility is the provider’s, not the Commission’s.
In practice:
- No names, usernames or email addresses in the free text of
decision_facts. Write “A user posted …” rather than “@jane_doe posted …”. - No quotes from content that identify a person, such as a comment containing someone’s real name.
- No user IDs as
puid. Use your own random identifier per decision that cannot be traced back to an account. - No links to profiles or content in your app.
Two versions of the text
The statement to the affected user can be personal (“Your comment from 3 October …”). The database version must be anonymous. Either write two versions, or build your templates so the database version needs no personal details.
Example: Germany
Platforms with their establishment or legal representative in Germany register through a form on the provider portal of the German DSC at the Bundesnetzagentur. The coordinator has been running an onboarding campaign since 2024. According to its June 2026 report to its advisory board, it has written to more than 100 providers; more than two thirds have since onboarded, some of the rest are exempt as micro or small enterprises, others are still being checked, and fine hearings are being prepared against four providers. Under section 33 of the Digitale-Dienste-Gesetz, failing to submit can be fined up to EUR 100,000, and submitting personal data up to EUR 300,000.
Alongside the database, the yearly transparency report applies. Using the same case data for both saves you doing the work twice.
How to do this with Limenia
In Limenia you set up submission to the Transparency Database per app. Submissions contain no IDs from your app and no content. More on the DSA notice and action page.
Sources
- Regulation (EU) 2022/2065 (Digital Services Act), Art. 17, 19 and 24, EUR-Lexeur-lex.europa.eu
- DSA Transparency Database: onboarding documentationtransparency.dsa.ec.europa.eu
- DSA Transparency Database: API documentationtransparency.dsa.ec.europa.eu
- European Commission: DSA Transparency Database, questions and answersdigital-strategy.ec.europa.eu
- European Commission: Digital Services Coordinatorsdigital-strategy.ec.europa.eu
- German Digital Services Coordinator: information for providers (German)dsc.bund.de
- Report of the German DSC to its advisory board, June 2026 (PDF, German)bundesnetzagentur.de
- Section 33 Digitale-Dienste-Gesetz (German fines, German)gesetze-im-internet.de