AI Liability in Switzerland: Who Pays When Your AI Agent Errs?

In short
When an AI agent makes a mistake, the AI itself is not liable — your company is. Under Swiss Code of Obligations Articles 41, 55 and 97, the operator bears responsibility for auxiliary persons, including digital ones. OpenAI, Anthropic and Google all disclaim liability in their terms, leaving the gap with you.
When an agent that reviews invoices, answers customer emails or drafts contracts makes a mistake, the first question in the boardroom is usually: who pays for this? The short answer: not the AI. It has no legal personality, no assets and no liability a court could assign to it. Under current Swiss law, responsibility rests with the same company that deployed the agent — just as it would for a human employee.
The short answer: responsibility stays with the company
Swiss contract and tort law has no special provision for artificial intelligence. It does not need one: the existing liability rules are technology-neutral and treat an AI agent like any other tool or auxiliary person acting on a company's behalf. For boards and executive teams, this means the question is not whether liability exists, but how it is allocated — and whether it is insured.
Three articles in the Code of Obligations every board should know
Three provisions of the Swiss Code of Obligations (CO) form the foundation of any discussion about AI liability in Switzerland:
- Art. 41 CO (unlawful harm): Anyone who unlawfully causes damage to another is liable for it — regardless of whether a human or an AI agent triggered the error.
- Art. 55 CO (vicarious liability): A company is liable for damage caused by its auxiliary persons while carrying out their assigned tasks. The prevailing interpretation increasingly extends this to digital auxiliaries such as AI agents acting on the company's behalf.
- Art. 97 CO (contractual liability): Anyone who defectively performs a contractual obligation — for example toward a customer — is liable for the resulting damage, even if an AI system executed the process.
When AI is embedded in a physical product: the Product Liability Act
Once an AI system does not merely advise digitally but is embedded in a physical product — a machine control unit or a medical device, for instance — the Swiss Product Liability Act also applies. It holds the manufacturer liable regardless of fault when a defective product causes harm. For companies integrating AI components into their own products, this raises the bar for due diligence in model selection, testing and documentation.
The EU shifts the burden of proof: Directive 2024/2853
In November 2024, the EU adopted Directive 2024/2853, updating product liability for the AI era. The central change: in cases of damage caused by defective AI systems, the burden of proof is partially reversed. Claimants no longer need to prove in technical detail how an algorithm failed — manufacturers and operators increasingly need to demonstrate that their system was safe. Switzerland is not directly bound by this directive, but it becomes practically relevant for companies with customers or subsidiaries in the EU — and it signals the direction Swiss practice is likely to follow.
2024/2853
EU directive on AI product liability, in force since November 2024
Why the terms of service of ChatGPT, Claude and Gemini won't protect you
OpenAI, Anthropic and Google word their terms of service carefully: all three disclaim liability for errors, misinterpretations or damage arising from the use of their models. This is legally understandable — and it also means the liability risk does not stay with the model provider, but shifts to whoever deploys the model within a business process. If you build an AI agent on top of these models, you effectively inherit the responsibility the provider contractually disclaims.
The case that shows the direction: Nippon Life v. OpenAI
A case analysed by Stanford in 2026 — Nippon Life v. OpenAI — frames AI liability explicitly as a matter of product liability, not as an unprecedented grey zone. The reasoning follows a logic that is also relevant for Swiss companies: an AI system is treated like a product that can have a defect, for which whoever places it in commerce or deploys it is held accountable. For Swiss SMEs, this signals that international legal developments are clearly moving toward more, not less, responsibility for deploying companies.
The insurance gap: what your policies probably don't cover
Traditional general liability and professional indemnity policies were designed for human action — for mistakes an employee makes, not for autonomous decisions an agent makes across hundreds of transactions within seconds. Many policies contain exclusions or ambiguous wording when it comes to damage arising from automated or AI-supported decisions. This gap only becomes visible once a claim occurs — by which point it is too late to close it.
Governance starts at the boardroom table
Deploying AI agents operationally without first clarifying the liability question shifts a business risk onto the personal responsibility of board members and executives. A clear allocation of responsibility, documentation and insurance coverage is part of ordinary due diligence today — not an optional extra.
What this means for the board and executive management
Under Swiss corporate law, the board of directors bears overall responsibility for adequate risk control within the company. Deploying AI agents does not change this — it only shifts the nature of the risk. Automating processes today without clarifying liability, insurance coverage and governance structure means operating in a legal grey zone that neither the Code of Obligations nor the Product Liability Act will resolve for you.
The good news: none of this prevents the sensible use of AI agents in your own operations. It simply changes how carefully the rollout needs to be prepared — from model selection through contractual structuring to insurance coverage. That preparation is what decides whether AI liability remains a theoretical risk for your company or becomes a very real one.
Frequently asked questions
- Is the AI itself liable for its own mistakes?
- No. An AI has no legal personality in Switzerland and therefore cannot be held liable itself. Responsibility rests with the company that deploys the AI agent — analogous to liability for human employees under Articles 41 and 55 CO.
- What does vicarious liability under Article 55 CO mean specifically for AI agents?
- Article 55 CO obliges a company to be liable for damage caused by an auxiliary person while carrying out its tasks. This logic is increasingly applied to AI agents that make automated decisions or execute processes on the company's behalf.
- Does standard general liability insurance cover damage caused by AI agents?
- Not reliably. Many existing policies were designed for human action and contain gaps or exclusions for damage arising from automated or AI-supported decisions. Reviewing existing coverage before deploying AI agents in production is advisable.
- Does EU Directive 2024/2853 apply to Swiss companies?
- Not directly, since Switzerland is not an EU member state. However, it becomes practically relevant for companies with business activity, customers or subsidiaries in the EU, and it signals the direction in which AI liability questions are generally developing.
- Does the liability disclaimer of OpenAI, Anthropic or Google protect me?
- No. These providers explicitly disclaim their own liability for errors of their models in their terms of service. The risk remains with the company that deploys the AI within a business process.
Sources
- OR-Haftung für fehlerhafte KI-Entscheidungen in der Schweiz
- Wer haftet für KI, wenn sie einen Schaden verursacht?
- Directive (EU) 2024/2853 on Liability for Defective Products
- When AI acts on its own, who is responsible for mistakes? | Deloitte Switzerland
- Wer haftet, wenn die KI Fehler macht? | Prager Dreifuss
- OpenAI Services Agreement
- Designed to Cross: Why Nippon Life v. OpenAI Is a Product Liability Case
- AI Liability & Legal Framework in Switzerland | Swiss AI
Would you like to explore this topic for your company?
Check Availability