Notice and action duties

Trusted flaggers and misuse of reporting under Art. 22 and 23 DSA

Notices from trusted flaggers get priority; people who abuse the system get suspended. This guide covers what Art. 22 and 23 DSA require from online platforms and how to put both into practice in your app.

  • Status: October 2026
  • Updated
  • 7 min read

Two articles of the DSA deal with notifiers who are especially reliable or especially unreliable. Article 22 gives priority to recognised entities, the trusted flaggers. Article 23 protects your reporting system from misuse: by users who keep posting manifestly illegal content, and by people who flood it with unfounded notices.

The trusted flagger status is debated in public. This guide sticks to what it means for you as a provider.

What a trusted flagger is and who awards the status

A trusted flagger is an entity, never an individual (recital 61), that a Digital Services Coordinator has awarded the status under Art. 22(2). The coordinator of the Member State where the entity is established decides. The entity must show:

  • particular expertise and competence in detecting, identifying and notifying illegal content;
  • independence from any provider of online platforms;
  • that it submits notices diligently, accurately and objectively.

Trusted flaggers publish a report at least once a year on the notices they sent, broken down by provider, type of content and action taken (Art. 22(3)). Their status covers a designated area of expertise, such as hate speech, consumer protection or child sexual abuse material. Under recital 61 it should be recognised by all online platforms, even when it was awarded in another Member State.

What you must do as a platform

Art. 22(1) requires the “necessary technical and organisational measures” so that notices from trusted flaggers are

  • given priority, and
  • processed and decided upon without undue delay,

as long as the entity acts within its area of expertise and uses your regular notice mechanism under Art. 16. The law does not require a separate channel.

Priority doesn’t mean acting without review. You still decide yourself, diligently and objectively under Art. 16(6). Recital 62 notes, though, that well-substantiated notices from experts can be expected to be quicker to handle.

In practice you need:

  1. A register of the trusted flaggers that report to you, with their area of expertise.
  2. Reliable attribution: a notice only gets priority if it verifiably comes from that entity, for example through a dedicated account, a known email domain or access you set up for them. A checkbox saying “I am a trusted flagger” that anyone can tick is not enough.
  3. A queue rule that moves those notices to the top.

Where to find the list

The Commission publishes all entities with trusted flagger status in a public, machine-readable database (Art. 22(5)). On the page Trusted flaggers under the DSA you can filter by country and area of expertise and download the list as XLSX. At the time of writing, the list was last updated on 5 October 2026.

When an entity contacts you as a trusted flagger, check it against this list, including its area of expertise.

Example: Germany

In Germany, the Digital Services Coordinator at the Bundesnetzagentur awards the status. According to its June 2026 report, it had certified four entities out of 37 applications. Failing to give trusted flagger notices priority (Art. 22(1)) can be fined up to EUR 300,000 under § 33 DDG. Other Member States set their own penalties; the Commission lists all national Digital Services Coordinators.

When a trusted flagger sends poor notices

If you have information that a trusted flagger has submitted a significant number of insufficiently precise, inaccurate or inadequately substantiated notices, you must pass it to the coordinator that awarded the status, with the necessary explanations and supporting documents (Art. 22(6)). Findings from complaints under Art. 20 count too.

If the coordinator sees legitimate reasons to investigate, the status is suspended for the duration of the investigation. If the entity no longer meets the conditions, the coordinator revokes the status (Art. 22(7)).

To back this up, you need to be able to analyse outcomes of trusted flagger notices: how many you acted on, how many you rejected, and why.

The Commission is preparing guidelines under Art. 22(8) on paragraphs 2, 6 and 7. According to the German coordinator’s June 2026 report, they are due to be adopted before the end of 2026. We will update this guide when they are published.

Misuse by users: Art. 23

Art. 23 covers two kinds of misuse:

  • Para. 1: users who frequently provide manifestly illegal content. You suspend the provision of your service to them.
  • Para. 2: individuals, entities or complainants who frequently submit manifestly unfounded notices or complaints. You suspend the processing of their notices and complaints.

“Manifestly” is narrow. Under recital 63, content is manifestly illegal, and a notice manifestly unfounded, when that is evident to a layperson without any substantive analysis. Someone who reports a harmless cat photo comment as terrorist propaganda ten times qualifies. Someone who gets a borderline case wrong does not.

Warning first, then a suspension for a reasonable period

Both paragraphs require the same sequence:

  1. A prior warning. Under recital 64 it includes the reasons for the possible suspension and how to challenge it.
  2. A suspension for a reasonable period of time. The DSA sets no maximum. The suspension itself comes with a statement of reasons under Art. 17.

The suspension can be challenged through internal complaint handling; see internal complaint handling under Art. 20 DSA. Recital 64 also makes clear that Art. 23 doesn’t stop you from taking other or stricter measures under your terms, for example for child sexual abuse material.

The four criteria

You assess misuse case by case, in a timely, diligent and objective manner. Art. 23(3) lists at least four circumstances:

Criterion Art. 23(3) Example
Absolute numbers (a) twelve manifestly unfounded notices in one week
Relative proportion (b) eleven out of twelve of this person’s notices were manifestly unfounded
Gravity and consequences (c) the nature of the illegal content, harm to those affected
Intention, where identifiable (d) notices aimed at one particular person

Criteria (a) and (b) need numbers: how many of someone’s notices you rejected and how many they sent in total. You need to be able to count this per notifier, including notifiers without an account. Online platforms also report suspension figures in their transparency report (Art. 24(1)(b)).

What goes into your terms

Art. 23(4) requires you to set out your misuse policy clearly and in detail in your terms and conditions, with examples of

  • the facts and circumstances you take into account when assessing misuse, and
  • the duration of the suspension.

An example clause might start: “If someone reports content several times within 30 days that clearly contains no violation, and this applies to most of their reports, we will first warn them. If it continues, we will not process their reports for 14 days, and for longer if it happens again.” The numbers are an illustration, not a requirement. What else belongs in your terms is covered in DSA points of contact and terms and conditions for apps.

Does this apply to you?

Art. 22 and 23 apply to online platforms. Micro and small enterprises are exempt under Art. 19; see DSA exemptions for micro and small enterprises. Art. 16 still applies to every hosting service: a notice from a trusted flagger is first of all a notice that you handle with care; see notices under Art. 16 DSA.

For the full flow, see DSA notice and action for your app.

How to do this with Limenia

You add trusted flaggers in the dashboard. Their notices get at least high priority; your backend links a notice to a trusted flagger only from its own verified records. Limenia counts rejected notices per notifier, pseudonymously via a hash. Warnings and suspensions are always decided by a person. Limenia caps suspensions at 365 days; that is a product setting, not a legal requirement.

Sources

  1. Regulation (EU) 2022/2065 (Digital Services Act), Article 22, EUR-Lexeur-lex.europa.eu
  2. Regulation (EU) 2022/2065, Article 23, EUR-Lexeur-lex.europa.eu
  3. Regulation (EU) 2022/2065, Recitals 61 to 64, EUR-Lexeur-lex.europa.eu
  4. European Commission: Trusted flaggers under the DSA (list)digital-strategy.ec.europa.eu
  5. European Commission: Digital Services Coordinatorsdigital-strategy.ec.europa.eu
  6. Germany: report of the Digital Services Coordinator to its advisory board, June 2026 (PDF, German)bundesnetzagentur.de
  7. Germany: Digitale-Dienste-Gesetz (DDG), § 33 (fines)gesetze-im-internet.de

Frequently asked questions

Your question is not here? Write to us, a person will answer.

Go to the contact form

Can anyone become a trusted flagger?

No. Only entities, not individuals, can get the status (recital 61). They must have particular expertise, be independent of platforms and submit notices diligently, accurately and objectively (Art. 22(2)).

Do I have to act on every trusted flagger notice?

No. You handle them with priority, but you still decide yourself, diligently and objectively. Priority means reviewing faster, not removing automatically.

Does a trusted flagger from another EU country count for my app?

Yes. Recital 61 says the status should be recognised by all providers of online platforms, whichever Member State awarded it. Priority applies only within the entity’s designated area of expertise.

How long can I suspend someone for misuse?

Art. 23 speaks of a “reasonable period of time” and sets no maximum. The duration must fit the severity, and your terms must give examples of durations (Art. 23(4)).

What counts as “manifestly” illegal or unfounded?

According to recital 63, when it is evident to a layperson without any substantive analysis. Borderline cases that people can reasonably disagree on do not count.

Ready for your notice and action process?

Start your trial in a few minutes. If you would rather talk first, we show you Limenia in a demo.

Or write to us using the contact form