Back to the blog

DSA Notice and Action Procedure. Why One Paragraph in Your Terms and Conditions Will Not Protect You

Learn how to build a DSA notice and action process for user content, from service classification and reporting forms to moderation decisions, appeals and records.

Your terms and conditions contain a single paragraph on reports: “email us, we will respond within 14 days, and in justified cases we will remove the content”. That is not a notice and action procedure. It is a contact inbox with a deadline — backed by an exemption from liability for everything your users publish.

Regulation (EU) 2022/2065 — the Digital Services Act (DSA) — fully applicable since 17 February 2024, requires every provider of a hosting service that stores user content to implement a separate, multi-component notice and action mechanism. Not a paragraph. Not a clause. A separate document with a form, a hierarchy of measures, statements of reasons for decisions, and a three-tier appeal process.

If you operate a marketplace with user feedback, an app with reviews, a platform offering e-publications, a SaaS product with a community component, or a classified ads service, this article will show you what the DSA requires across seven areas: from service classification and the reporting form to appeals and the register of reports. You will also learn why, when designing a reporting form, you are determining the point at which your liability for user content begins.

Key concepts you need to know

Before we move on to the specifics, establish a common language with your team. The DSA introduces terminology that directly affects your obligations.

Concept What it means for your company
Hosting service You store user content (ratings, reviews, comments, photos, lists). You are subject to Articles 16–18 of the DSA
Online platform User content is publicly visible — you are also subject to Articles 20–24 of the DSA (appeals, ADR, misuse)
Notice and action mechanism The procedure under Article 16 of the DSA: a defined input (form), legal effect (actual knowledge), and output (decision + statement of reasons + appeal)
Actual knowledge (Article 6 of the DSA) The point at which a provider loses its exemption from liability for user content if it fails to act expeditiously
Exemption from liability Article 6 of the DSA: you are not liable for user content as long as you have no knowledge of it — a complete notice gives rise to that knowledge
Digital Services Coordinator In Poland — the President of UKE. The authority supervising compliance with the DSA, imposing penalties, and certifying ADR bodies
Trusted flagger An entity certified by the President of UKE whose notices you process as a priority and without undue delay (Article 22 of the DSA)

Area 1: service classification — it determines the scope of your obligations

Before you write even a single sentence of the procedure, you must answer three questions. The answers determine which provisions of the DSA apply to you.

Question If yes If no
Do you store user content (ratings, reviews, comments, photos, profiles)? You are a hosting service provider → Articles 16–18 of the DSA The DSA notice and action rules do not apply to you
Is user content publicly visible (to other users, not only to its author)? You are an online platform → additional obligations under Articles 20–24 of the DSA You are a hosting service, but not a platform → Articles 20–24 do not apply
Is your company a micro or small enterprise (fewer than 50 employees and turnover/balance sheet total of up to EUR 10 million)? Exemption from Articles 20–28 of the DSA (except Article 24(3)), but note: if you voluntarily publish a full platform procedure, it will be contractually binding on you The full scope of platform obligations applies to you

Example: an app in which ratings and reviews are visible to everyone is an online platform. The same app, if notes and lists are visible only to their author, is a hosting service but not a platform. The difference is the entirety of Article 20, with its six-month appeal period, Article 21 (ADR), Article 22 (trusted flaggers), and Article 24 (reporting).

Record the classification result in a file note and include the date. If your company relies on the exemption under Article 19 of the DSA, check when it may lose it. After losing micro or small enterprise status, you have a 12-month grace period to implement the additional obligations (Regulation (EU) 2022/2065 — EUR-Lex PL).

A note for VC-backed startups: the mere fact that a fund invests in the company does not automatically mean that it loses its SME status. What matters is whether the relationship with the investor creates a partner or linked enterprise within the meaning of the Annex to Commission Recommendation 2003/361/EC. If so, the investor’s data must be added to your own when assessing the thresholds. Check this before assuming that the exemption under Article 19 still applies to you.

Area 2: a separate document — why terms and conditions are not enough

Based on the market templates analysed, a robust notice and action procedure is approximately 11,500 characters long and contains 11 numbered sections. That is not the kind of material you add to your terms and conditions.

The DSA requires the reporting mechanism to be easy to access and user-friendly (Article 16(1)). A paragraph buried on page 12 of the terms and conditions does not pass that test — even if it is substantively correct.

What does this mean in practice?

  1. Move the notice and action procedure out of the terms and conditions into a separate document at its own URL
  2. Leave a short reference in the terms and conditions, along with the information on moderation policies required by Article 14 of the DSA
  3. Link to the procedure in at least three places: in the website footer, in the account/app settings, and via a report button next to every piece of user content — the last of these is what genuinely meets the user-friendliness test
  4. Introduce document versioning with dates and archive previous versions — in a dispute over a decision made a year ago, it is the procedure in force on the date of that decision that matters, not the current one

A separate document also offers an operational advantage: you can update it without amending the terms and conditions and without requiring users to accept them again under the Consumer Rights Act.

Contact us if you would like to verify whether your current documentation meets the DSA requirements.

Area 3: the reporting form — this is where liability begins

A form that collects only “describe the problem” and “your email address” does not allow you to assess illegality or determine when the liability clock under Article 6 of the DSA started running. Risk management then becomes guesswork.

Article 16(2) of the DSA specifies four mandatory elements of a complete notice:

Element What it must contain Why it matters
1. Explanation of illegality A sufficiently substantiated explanation of why the content is illegal Without it, you cannot assess whether the notice gives rise to actual knowledge
2. Location of the content The exact electronic location (URL or equivalent) Without it, the moderator does not know which content is being reported
3. Details of the person submitting the notice Name/company name + email address Enables follow-up contact and limits misuse
4. Good-faith statement Confirmation that the person submitting the notice believes in good faith that the information and allegations it contains are accurate and complete A formal requirement under Article 16(2)(d)

Exception: notices concerning offences referred to in Articles 3–7 of Directive 2011/93/EU (sexual abuse and sexual exploitation of children) do not require the details of the person submitting the notice. The procedure must provide for this exception.

Locating content in a mobile app

If your app does not use URLs, you can meet the exact location requirement by using a content identifier automatically transmitted through the report button next to the content. For email reports, add mandatory fields for the content identifier, content author, and publication date.

Incomplete and anonymous notices

The procedure should address both scenarios:

  1. Incomplete notice with contact details provided — send a request for the missing information and record in the register that the Article 6 clock has not yet started
  2. Anonymous notice — it is not prohibited and must not be deleted. However, it is not complete within the meaning of Article 16(3), so it does not in itself trigger the presumption of knowledge. State this explicitly: the notice will be reviewed, but the person who submitted it will not receive a response because there are no contact details to which it can be sent
  3. Incomplete notice without contact details, but allowing the content to be identified — assess it on its merits, because actual knowledge of illegality may also arise outside the Article 16 mechanism

One sentence worth remembering: when designing a reporting form, you are determining the point at which your liability for user content begins. A complete notice under Article 16(2) is considered to give rise to actual knowledge for the purposes of Article 6 of the DSA if it enables a diligent provider to identify the illegality without a detailed legal examination (Regulation (EU) 2022/2065 — Article 16(3)).

Area 4: triage — two tracks, not one queue

A single 14-day deadline for all notices is wrong in both directions: it is too long for potentially illegal content and too strict for purely contractual matters.

The DSA requires notices to be divided into two tracks as soon as they are received:

Track Examples Time limit Risk of failing to act
Potentially illegal content Infringement of copyright, trade marks, personal rights, image rights, criminal law, unfair competition, personal data protection Act expeditiously — the DSA does not specify a numerical deadline. Do not state a fixed deadline Loss of the exemption from liability under Article 6 — you become liable for user content as if it were your own
Breach of the terms and conditions Spam, off-topic content, profanity below the legal threshold, repeated publication of the same content Contractual deadline (e.g. 14 days from receipt of a complete notice) — include one, but verify whether your organisation can realistically meet it Breach of contract with the user, but no loss of the exemption from liability

Mixed cases — a notice combining a technical problem with an allegation that content is illegal — still fall within the DSA procedure and must follow the stricter track.

A third category of cases: payment complaints, login issues, refunds. State in the procedure that this category is not covered by the notice and action mechanism and provide the address of the appropriate channel. Without this distinction, genuine notices of illegality become buried among invoice tickets.

You should also tailor the categories of reportable content to your business model. For example, a service offering digital content and e-publications should address the distribution of illegal copies and the circumvention of technological protection measures. Copying a generic list from someone else’s template is not enough.

Area 5: the decision and statement of reasons — a form, not a letter

A statement such as “the content was removed because it breached the terms and conditions” does not meet the requirements of Article 17(3) of the DSA. For online platforms, statements of reasons are also submitted to the European Commission’s public database after personal data has been removed — they cease to be private correspondence with a user and become documents that can be compared with thousands of others (DSA Transparency Database).

Hierarchy of measures

Before making a decision, work through the hierarchy from the least to the most severe measure:

  1. Leaving the content unchanged (rejecting the notice)
  2. Labelling the content (e.g. “disputed content”)
  3. Restricting visibility (demotion)
  4. Removing the content or disabling access to it
  5. Restricting account features
  6. Suspending the account for a specified period
  7. Closing the account
  8. Suspending payments (in monetisation models)

Configure your moderation tool to require a record of why a less severe measure was rejected. Without this, you will not be able to demonstrate the proportionality required by Article 14(4) of the DSA.

Statement of reasons template — six fields

Article 17(3) of the DSA requires a statement of reasons containing at least:

Field What to enter
1. Facts and circumstances A description of the content and conduct that led to the decision
2. Legal or contractual basis A legal provision (e.g. Article 116 of the Copyright Act) or a specific provision of the terms and conditions
3. Classification of the content Whether the content is illegal or incompatible with the terms and conditions — and why
4. Territorial scope and duration Removal throughout the EU vs. geoblocking in one country; suspension for 7 days vs. indefinite suspension
5. Information on automation Whether the content was detected by an automated filter and a human merely approved the decision — this constitutes automated detection and must be disclosed
6. Redress options Information on internal appeals, ADR, and judicial redress

Ensure that the statement of reasons is sent no later than when the measure is applied. Verify whether the system has the user’s electronic contact details at all. Record the absence of such details in the register.

Area 6: a three-tier appeal process

The market standard is a 14-day complaint handled by the same team that made the decision. The DSA requires something entirely different.

Tier 1: internal complaint-handling system (Article 20 of the DSA)

This applies to online platforms (not hosting services alone). Requirements:

  1. Free of charge
  2. Available for at least 6 months after the decision — not 14 days
  3. Reviewed by someone other than the person who made the original decision
  4. Not handled exclusively through automation — you may use AI for preliminary analysis, but the decision must be reviewed by a human
  5. Available not only to the author of the content, but also to the person whose notice was rejected — this other party is regularly omitted from terms and conditions

Tier 2: out-of-court dispute settlement (Article 21 of the DSA)

  1. The user refers the dispute to a body certified by the Digital Services Coordinator (in Poland — the President of UKE)
  2. The decision is not binding on the parties
  3. The platform bears the costs if the dispute is resolved in the user’s favour
  4. The user chooses the body independently — the platform cannot impose one

State the right to ADR in the procedure and link to the current lists maintained by the President of UKE and the European Commission. Make it clear that ADR does not preclude judicial redress. If, at the time the procedure is published, there is no certified body for your category of disputes, state this explicitly and indicate an alternative (UKE — out-of-court dispute settlement).

Tier 3: complaint to the President of UKE and judicial redress

Article 53 of the DSA gives users the right to lodge a complaint against a provider with the Digital Services Coordinator. Article 54 of the DSA provides a right to compensation for damage resulting from a breach of the Regulation’s obligations. Both remedies should be included in the information on redress options.

Area 7: register, reporting, and contact channels

Register of notices and decisions

Without a register, you will not be able to demonstrate due diligence in a dispute, prepare the reports required by Article 15 of the DSA, or monitor compliance with your own deadlines. The register should contain:

  1. The date the notice was received
  2. The reporting channel (form, email, in-app button)
  3. An assessment of completeness under Article 16(2)
  4. The triage track (illegal content vs. breach of the terms and conditions)
  5. The date and substance of the decision
  6. The basis for the decision (legal provision or provision of the terms and conditions)
  7. Information on the use of automated tools
  8. The date the statement of reasons was sent
  9. The appeal and its outcome

Three different contact arrangements — do not confuse them

In three consecutive articles, the DSA establishes three distinct functions:

Article Function For whom Language
Article 11 Point of contact for authorities The Commission, coordinators, the European Board for Digital Services Polish and English
Article 12 Point of contact for users Recipients of the service — without requiring the exclusive use of automated tools Polish
Article 13 Legal representative in the EU Only for providers not established in the Union As required by the authority

Two common mistakes: a company established in Poland names a legal representative in the document even though it does not need one. Or the opposite — an app based outside the EU that offers services to Polish users provides only an email address and fails to appoint a representative, in breach of Article 13 of the DSA.

You should also separate the inbox for orders from authorities (Articles 9–10 of the DSA) from the queue of user notices. An authority’s order has its own procedure and deadline — it should not become buried in a ticket queue.

Policy against misuse (Article 23 of the DSA)

This applies to online platforms. Describe it in the terms and conditions — clearly, in detail, and with examples:

  1. Misuse of the reporting mechanism — suspension of the processing of notices from a person submitting manifestly unfounded notices. Example parameters: at least 5 manifestly unfounded notices within 30 days
  2. Frequent provision of infringing content — suspension of the service for the recipient. Example parameters: at least 3 instances of infringing content published within 30 days despite a prior warning
  3. The assessment of misuse must consider the absolute numbers, the proportion relative to the total, the gravity of the misuse, and intent — not arithmetic alone

Remember: a published threshold works both ways. It disciplines the user, but it also prevents you from suspending an account below your own threshold without additional justification.

Team training

Train your support and trust & safety teams on one key principle: a complete notice gives rise to knowledge of potential illegality, and the risk of liability starts running from that point. A notice queue is not a technical support ticket queue. Prioritisation must take account of the legal regime, not only the order in which notices were received.

Add a technical feature that allows notices from trusted flaggers to be identified upon receipt (Article 22 of the DSA) — rather than trying to determine their status from the content of an email. Notices from these entities must be processed as a priority and without undue delay (UKE — trusted flaggers).

Penalties and consequences — the risks of having no procedure

Type of sanction Legal basis Amount or effect
Fine for breaching DSA obligations Article 52 of the DSA Up to 6% of annual worldwide turnover
Fine for incorrect or misleading information Article 52 of the DSA Up to 1% of annual worldwide turnover
Periodic penalty payments Article 52 of the DSA Up to 5% of average daily worldwide turnover
Loss of the exemption from liability Article 6 of the DSA You become liable to third parties for user content as if it were your own
User complaint to the President of UKE Article 53 of the DSA Supervisory proceedings against the provider
Compensation Article 54 of the DSA The user’s right to compensation for damage resulting from a breach
Contractual risk Published procedure A numerical deadline stated in the procedure becomes a contractual commitment — repeatedly missing it constitutes a breach of contract

In Poland, the Digital Services Coordinator is the President of UKE, who, from 6 November 2026, performs supervisory tasks, including imposing administrative fines and issuing orders to cease infringements (President of UKE — new responsibilities and powers).

The DSA and other regulations — what the procedure does not replace

The DSA notice and action procedure does not replace:

  1. Consumer complaints under the Consumer Rights Act — these concern the lack of conformity of goods or digital services with the contract, not content moderation
  2. Obligations under the GDPR — collecting the details of the person submitting a notice (Article 16(2)(c) of the DSA) requires a separate legal basis under Article 6(1) of the GDPR. The identity of the person submitting the notice may be disclosed to the author of the content only where necessary to establish illegality (e.g. in intellectual property infringement cases)
  3. The P2B Regulation (2019/1150) — in B2B relationships with a platform’s business users. The DSA does not repeal the P2B Regulation. Both may apply in parallel: P2B to disputes concerning the terms of the business relationship, and the DSA to moderation obligations
  4. The AI Act (Regulation 2024/1689) — if you use automated moderation, you must separately ensure transparency about algorithmic tools in the terms and conditions (DSA), provide a statement of reasons for every decision to the user (Article 17 of the DSA), and ensure the lawful processing of data (GDPR). Using an AI model does not exempt you from the obligation to provide reasons

Implementation checklist

No. Action Priority
1 Classify the service: hosting service or platform, SME status, expiry date of the Article 19 exemption Essential
2 Move the procedure out of the terms and conditions into a separate document at its own URL Essential
3 Link to the procedure in the footer, account settings, and via a button next to every piece of content Essential
4 Redesign the form around the four elements required by Article 16(2) Essential
5 Provide a way to locate content in the mobile app (automatic identifier) Essential
6 Introduce the exception to the requirement for the details of the person submitting the notice (Directive 2011/93/EU) Essential
7 Divide triage into two tracks: illegal content vs. breach of the terms and conditions Essential
8 Do not state a fixed deadline for illegal content; state a contractual deadline for breaches of the terms and conditions Essential
9 Implement automatic acknowledgement of receipt of a notice Essential
10 Build a hierarchy of measures requiring the rejection of a less severe measure to be recorded Essential
11 Prepare a statement of reasons template with the six fields required by Article 17(3) Essential
12 Provide free internal appeals for at least 6 months (for platforms) Essential
13 Describe ADR, complaints to the President of UKE, and judicial redress Essential
14 Separate the point of contact for users (Article 12) from the point of contact for authorities (Article 11) Essential
15 Set up a register of notices and decisions Essential
16 Train the team: complete notice = start of liability Essential
17 Describe the misuse policy, with thresholds and examples, in the terms and conditions Recommended
18 Add identification of trusted flagger notices upon receipt Recommended
19 Introduce versioning and archiving of the procedure Recommended
20 Tailor the categories of reportable content to your business model Recommended

A DSA procedure is a product and operational project, not an editorial task

The DSA is not an obligation you can meet with a single paragraph in your terms and conditions. It is a project encompassing a legal document, a form, the UX of the report button, a moderation tool, a register, team training, and reporting.

The main cost lies not in drafting the document but in building the process: a report button next to every piece of content that automatically transmits its identifier, a form meeting Article 16(2), a statement of reasons template with mandatory fields, a register of notices feeding into reports, a separate inbox for authorities, and staff resources for appeals maintained for at least 6 months after each decision.

On the savings side: retaining the exemption from liability under Article 6, reducing the risk of fines of up to 6% of worldwide turnover, and keeping customer service queries out of the DSA channel.

If you operate a service with user content and want to put your notice and action procedure in order — from service classification through the form and statement of reasons template to the appeal process and register of notices — contact us. We will help you build a mechanism tailored to your business model rather than copied from someone else’s template.

Frequently asked questions

Is my service an online platform within the meaning of the DSA, or merely a hosting service — and what is the difference?

If user content (ratings, reviews, comments, photos) is publicly visible — to other users, not only to its author — your service is an online platform. You are then subject to the additional obligations under Articles 20–24 of the DSA: a six-month internal appeal period, out-of-court dispute settlement, priority processing of notices from trusted flaggers, and reporting. If the content is visible only to its author, you are a hosting service provider and Articles 16–18 apply to you, but Articles 20–24 do not.

We are a small company — does the exemption under Article 19 of the DSA mean that I can omit most obligations?

Micro and small enterprises (fewer than 50 employees and turnover/balance sheet total of up to EUR 10 million) are exempt from Articles 20–28 of the DSA. You must still implement the notice and action mechanism under Article 16, provide statements of reasons for moderation decisions under Article 17, and describe your moderation policies under Article 14. Note: if you voluntarily publish a full platform procedure, it will be contractually binding on you — even if you formally qualify for the exemption. After losing SME status, you have 12 months to implement the additional obligations.

At what point do I become liable for user content?

From the moment a complete notice under Article 16(2) of the DSA enables you — as a diligent provider — to identify the illegality of the content without a detailed legal examination. It is not the moment an email arrives or the moment a moderator makes a decision. It is the moment a notice containing all four mandatory elements enters your system. If you fail to act expeditiously after that point, you lose the exemption from liability under Article 6 of the DSA.

Can I keep a single 14-day deadline for all notices?

No. For potentially illegal content, the DSA requires you to act expeditiously and does not specify a numerical deadline. Stating 14 days gives you a false sense of security — if the content is manifestly illegal and you wait 14 days, you may lose the exemption from liability. State a numerical deadline only for breaches of the terms and conditions (the contractual track), calculated from receipt of a complete notice.

What should I do with an anonymous notice — reject it or review it?

Review it — anonymous notices are not prohibited and must not be deleted. However, such a notice is not complete within the meaning of Article 16(3) of the DSA, so it does not in itself trigger the presumption of actual knowledge. State this explicitly in the procedure: the notice will be reviewed, but the person who submitted it will not receive a response because they did not provide contact details. If the notice makes it possible to identify potentially illegal content, assess it on its merits, because actual knowledge may also arise outside the formal Article 16 mechanism.

Will my statements of reasons be public?

If you are an online platform — yes. Article 24(5) of the DSA requires the statements of reasons referred to in Article 17 to be submitted to the European Commission’s Transparency Database after personal data has been removed. A statement of reasons ceases to be private correspondence with a user and becomes a document that can be compared with thousands of others. Draft statements of reasons carefully: the supervisory authority and researchers may use them to assess the quality of your moderation.

Related services

How we can help

RECOMMENDED

You may also be interested in

Selected examples of projects in which we supported businesses on legal matters, from regulatory and compliance advice to technology projects, transactions and day-to-day business support.