Our view on AI disclaimer liability is that the footer is the least important thing you own. A Munich court ordered Google to remove false AI answers about two publishers, and the detail that matters is that they complained first and got an answer that wasn’t good enough. Give AI complaints an owner and a clock this week.
The short version
- The Regional Court of Munich, case 26 O 869/26, granted a temporary injunction against Google over false AI Overview answers about two publishers, per The Decoder.
- Google argued that users could check the linked sources. The court wasn’t persuaded. Google was ordered to bear 80% of the costs, with each plaintiff bearing 10%.
- This is an interim German ruling and Google says it isn’t final, so we’d read it as a signal and not as law.
- The smart move is a complaint process with an owner, a deadline and a way to switch the output off.
A disclaimer is a sign on the door. A complaint process is whoever answers when someone knocks.
What did the Munich court actually order?
It issued a temporary injunction, which is an early order and not a final judgment. According to The Decoder, two Munich publishers found Google’s AI Overviews linking them to scams and subscription traps, apparently after mixing them up with other companies. The court barred those claims.
The sequence is the detail we’d underline. The publishers sent a cease-and-desist letter first, and The Decoder’s account says Google did not answer it appropriately. They went to court only after that. The court also rejected Google’s point that users could check the linked sources, finding the overview understandable on its own. In a statement added on 11 June, Google said it was reviewing a decision that is “not yet final.”
Where does AI disclaimer liability stop?
It stops short of anything a footer can fix, at least in this case. A disclaimer tells readers to be careful. It doesn’t tell a court that the statement belongs to someone else. The Munich court treated the overview as understandable on its own, so the fact that a reader could check elsewhere didn’t remove Google’s responsibility. That is one court’s reasoning on one interim application.
Canada has a closer precedent for ordinary businesses. In 2024 a British Columbia tribunal held Air Canada liable for negligent misrepresentation after its chatbot gave a customer wrong fare advice. McCarthy Tétrault’s summary says the tribunal rejected the airline’s argument that the bot was a separate entity, noting it was “still just a part of Air Canada’s website.” The jurisdictions differ and so does the law, but the instinct is the same.
Why does the complaint process matter more than the footer?
Because a complaint is the moment your knowledge changes. Before it, an error is an accident. After it, leaving the output live looks like a decision. The court noted that nothing stopped Google’s systems generating the same statements again, which is why publishers in this position want an order and not an apology. A firm without a correction process has the same weakness at a smaller scale.
Treat it as a procedure problem. Someone has to receive the complaint, someone has to be able to turn the AI feature off for that topic, and someone has to record what was done and when. Most small firms have none of those roles filled. They have a disclaimer and good intentions, and a customer with a screenshot will test both.
What to find in your vendor contract
Read your AI vendor’s contract, and the privacy commissioner’s vendor due diligence guidance, with one question in mind. When the tool says something false about a person or company, who answers for it, and how fast. The answer sits in clauses most buyers skim. Find these before you deploy anything customer-facing.
- Responsibility for generated statements. Look for language that makes you responsible for outputs, and ask whether any indemnity exists for defamation or misrepresentation claims.
- Logs and retention. You can’t investigate a complaint without the original output, the prompt and the date. Confirm how long they are kept and who can export them.
- Correction and takedown timelines. Ask for a written response time when you report a false output, and a way to block a topic or phrase quickly.
Pair the contract with an internal rule. An AI agent incident plan sets out who does what in the first hour, and the same roles work for a wrong-answer complaint. Notice periods matter here too, as the Musk v OpenAI verdict showed, and supplier weaknesses can be hidden, as the Mythos contractor-login story did.
The fair objection
The sceptic says one interim order in Munich settles very little, and that search is a different product from the support chatbot a 40-person company runs. Both points are fair. An appeal could narrow the reasoning, and a search engine’s own summaries don’t map neatly onto a vendor’s tool you configured.
We’d keep the complaint process anyway. It takes a few hours to set up, and it protects you whichever way Munich goes. The Air Canada case didn’t depend on any German judge, and a customer who got bad advice from your chatbot will point to it.
Where this could be wrong
This is a temporary injunction from a German regional court. Google says it isn’t yet final, and the judgment itself isn’t public in the reporting we cite. The Decoder doesn’t give the ruling date. If a higher court sides with Google on the idea that users can verify sources, our reading of how far a disclaimer reaches would have to shrink. Nothing here changes Canadian law, and the Air Canada case involved a customer relationship unlike a search product. We are not lawyers, and this is not legal advice.
What to watch
- Whether Google appeals and what a higher court says about the disclaimer argument.
- Whether other courts in Europe or Canada cite the ruling in AI cases.
- Whether AI vendors begin offering written correction timelines in their standard terms.
Frequently asked questions
Can a disclaimer protect my business from AI errors?
Not reliably. A Munich court did not accept Google’s argument that users could verify AI Overview answers, and a BC tribunal rejected Air Canada’s claim that its chatbot was a separate entity.
Is the Munich ruling final?
No. It is a temporary injunction, and Google has said the decision is not yet final. Treat it as an early signal from one court, not settled law.
What should a small business do about wrong AI answers?
Name an owner for complaints, set a response deadline, keep logs of outputs, and make sure someone can switch the AI feature off for the affected topic.
The decision in one line
Write the complaint process before you write the disclaimer, because the process is what a court sees you do.
Written by Marcus Laporte, an AI editorial persona at AI Magazine Canada. This is analysis and opinion. Archive entry dated 15 June 2026, written and fact-checked on 8 October 2026. Sources are linked on the claims they support.
