Rightshold™ Sign up

Answers · AI evidence

Does the new EU Product Liability Directive cover AI apps and chatbots, and what evidence will an AI company need if someone says its AI caused them harm?

Last updated

TL;DR: Yes. Directive (EU) 2024/2853 says software is a product, naming applications and AI systems, whether it's installed on a device or supplied as a service, and it applies to products placed on the EU market or put into service after 9 December 2026, the date by which EU countries must write it into national law. Liability is strict, so the injured person doesn't have to prove you were careless, but they do have to prove the product was defective, that they suffered damage and that the defect caused it. Two new rules change how that plays out for AI. A court can order you to disclose relevant evidence once the claimant has made a plausible case (Article 9), and if you don't, the product is presumed defective (Article 10(2)(a)). And where technical or scientific complexity makes proof excessively difficult, the court must presume defect, causation or both if the claimant shows they're likely (Article 10(4)). The Directive has limits: it compensates people, not companies, and only for death or personal injury (including medically recognised psychological harm), damage to property not used only for work, and destruction or corruption of data not used for professional purposes. Pure financial loss isn't covered. The separate AI Liability Directive was withdrawn in October 2025, so this is now the main EU no-fault route for harm from AI. In practice, what decides many cases will be what you can show your system did: which version was running, what it was given and what it produced.

What should I check, step by step?

1. List which of your AI products and features are offered in the EU, and which will be placed on the market or put into service after 9 December 2026. A substantial modification to an older product after that date can bring it under the new rules.

  1. Keep a release history: which model and version, system prompt, tool set and safety settings were live in each release, and when each update went out. The Directive treats software updates and machine-learning behaviour as part of the product while it stays within your control.
  2. Keep per-run records for outputs that could cause harm: a hash of the input, the model and settings, a hash of the output and the time. If you're ordered to disclose evidence about one incident, that's what you'll need to find.
  3. Be ready to produce evidence in a form a court can follow. Article 9(6) lets courts require disclosed evidence to be presented in an easily accessible and easily understandable manner.
  4. Separate what you'd disclose from your trade secrets. Disclosure is limited to what's necessary and proportionate, and courts can protect confidential information, but training data, algorithms and monitoring data could still be in scope.
  5. Keep shipping security fixes. The defence that a defect arose after release isn't available where it comes from software, including updates or a lack of updates needed to keep the product safe, that's within your control.
  6. Map your supply chain: model provider, your app, integrators, resellers and any EU importer or authorised representative. Distributors that can't name the responsible operator within a month of a request can be held liable themselves.
  7. Review contracts with model and tool providers for who bears what. Where several operators are liable for the same damage, the one that pays can seek recourse from the others under national law.
  8. Keep records for as long as a claim can be brought. The Commission says operators stay liable for 10 years after the product is placed on the market (25 years in some health cases), and victims have 3 years to bring a claim.
  9. Watch the national law in each country you sell into. Germany's government published its draft bill on 17 December 2025, and details can still vary by country. Talk to a lawyer about your products.

Does the EU Product Liability Directive apply to AI software and SaaS?

The Directive's recitals say software, such as operating systems, firmware, computer programs, applications or AI systems, is a product, irrespective of whether it is stored on a device, accessed through a communication network or cloud technologies, or supplied as software as a service. The recitals also say information itself isn't a product, so the rules don't apply to the content of digital files such as media files or e-books, or to the mere source code of software. How that line applies to an AI system's outputs hasn't been tested in court.

Can a court make an AI company disclose evidence under the EU Product Liability Directive?

Under Article 9, once a claimant has presented facts and evidence sufficient to support the plausibility of the claim, a court can order the defendant to disclose relevant evidence at its disposal. The defendant can ask for the same from the claimant. Courts must keep disclosure to what is necessary and proportionate and can protect trade secrets.

What happened to the EU AI Liability Directive?

The Commission proposed a separate AI Liability Directive in September 2022, with its own disclosure rules and a presumption of causality for fault-based claims. It listed the proposal for withdrawal in its February 2025 work programme, saying no agreement was foreseeable, and the withdrawal was published in the Official Journal on 6 October 2025. The Commission said it would assess whether to present a new proposal or take another approach.

What records should an AI company keep for EU product liability claims?

Both sides of a claim will turn on the same facts: what the system was given, which version answered and what it produced. A claimant usually has only a screenshot. If the company can't produce its own record of that run, it may face the presumption that follows a failure to disclose, or a court presuming defect because the system is too complex for the claimant to explain.

How do I ask Rightshold about this (free, no key)?

Add the MCP server https://www.rightshold.com/mcp to Claude, Cursor, ChatGPT, Grok or VS Code, then ask: “Record a signed receipt for this production answer from our app: a hash of the user's input, a hash of the exact output we returned, the model and the app release it ran on, so we can show later what this version produced.”

One-click setup

{
  "tool": "record_ai_run",
  "arguments": {
    "model": "<model id and dated version>",
    "provider": "<model provider>",
    "prompt_sha256": "<sha256 of the exact input sent to the model>",
    "output_sha256": "<sha256 of the exact output returned to the user>",
    "params": {
      "app_release": "<your release tag>",
      "system_prompt_sha256": "<sha256 of the system prompt>",
      "safety_config_sha256": "<sha256 of your safety settings>",
      "market": "EU"
    },
    "ran_at": "2026-11-10T12:00:00Z"
  }
}

Rightshold doesn't assess whether a product is defective, decide who is liable or advise on any country's transposition of the Directive. A receipt proves which hashes were recorded and when Rightshold recorded them. Article references are to Directive (EU) 2024/2853 as published; national laws implementing it may differ in detail. Not legal advice; talk to a lawyer about your products.

What are the sources?

Related

Not legal advice. JSON · Markdown · All answers

Get a free API key in one call

No card and no email needed. 100 free credits; the license and policy checks stay free without a key.

curl -s -X POST https://www.rightshold.com/v1/accounts/signup -H "Content-Type: application/json" -d '{"accept_terms":true}'
export RIGHTSHOLD_API_KEY=rs_...   # the api_key from the reply (shown once)
curl -s https://www.rightshold.com/v1/licenses/check -H "Authorization: Bearer $RIGHTSHOLD_API_KEY" \
  -H "Content-Type: application/json" -d '{"license":"MIT","intended_use":{"commercial_use":true}}'