Rightshold™ Sign up

Answers · AI evidence

Who is responsible when an AI chatbot makes up false claims about a real person, and what can that person do?

Last updated

TL;DR: It's still being decided, case by case. In the US, the first ruling went to the AI company: in Walters v. OpenAI (Gwinnett County Superior Court, Georgia, May 19, 2025), the judge granted OpenAI summary judgment over ChatGPT's invented embezzlement claim against a radio host, for three independent reasons: the one person who saw it was a journalist who had been warned the output could be wrong and knew it was false, Walters couldn't show fault, and he conceded he had no damages. That ruling turned on its facts. As of Eugene Volokh's September 2026 count there have been nine US libel-by-AI cases: one settled (Starbuck v. Meta, August 2025), one sent to arbitration, and six still going, including Starbuck v. Google and Keene v. Google, where motions to dismiss were denied, and Wolf River Electric's suit over a Google AI Overview, which was sent back to Minnesota state court. In Europe, noyb filed a GDPR complaint in Norway in March 2025 after ChatGPT described a private man as a convicted child murderer, arguing that made-up output about a person breaks the GDPR's accuracy principle. Whatever route a person takes, the case starts with proof of exactly what the AI said, to whom and when.

What should I check, step by step?

1. Save the output the moment you see it: export or copy the full conversation, the question that produced it, the product and model shown, and the date and time. A screenshot alone is the weakest form because it's easy to edit.

  1. Keep the conversation's share link if the product offers one, but don't rely on it alone: a share link can stop working if the conversation is deleted. Hash the exported file and get an independent timestamp on the hash, so you can show later the copy wasn't changed.
  2. Record who else saw it. Defamation needs publication to someone other than you; in Walters the only reader was the journalist who prompted it, and that mattered. Customers, partners or a search results page that showed it to the public are a different situation.
  3. Write down the harm as it happens: lost contracts, cancelled orders, messages from people who believed it. Walters conceded he had no actual damages, which was one of the three reasons he lost.
  4. Ask the company to correct it, in writing, and keep the request and any reply. Georgia law required a correction or retraction request before seeking punitive damages, and the Starbuck cases put weight on repeated notices that went unfixed.
  5. In the EU or EEA, you can file a data protection complaint under the GDPR's accuracy and rectification rights, as noyb did in Norway, alongside or instead of a defamation claim.
  6. Check again over time and keep each result. Answers change between model versions, and a later model that uses web search may stop repeating the claim, so your saved copy may be the only record.
  7. If you run an AI product that answers questions about people, keep a server-side record of each answer (request, model, output and a hash), so you can show what your product actually said when someone complains.
  8. Talk to a lawyer before suing or publicly accusing the company. Defamation rules, public-figure status and deadlines differ by state and country.

Can you sue OpenAI if ChatGPT makes up false claims about you?

Journalist Frederick Riehl asked ChatGPT to summarize a real lawsuit. After he gave it a link it said it couldn't open, it produced a different, invented summary saying gun-rights activist Mark Walters had embezzled from the Second Amendment Foundation. Walters sued OpenAI for libel.

What AI defamation lawsuits have there been so far?

Volokh's September 14, 2026 count lists nine US libel-by-AI cases since 2023: Walters (summary judgment for OpenAI); Battle v. Microsoft (sent to arbitration and resolved there); Starbuck v. Meta (settled); Keene v. Google and Starbuck v. Google (motions to dismiss denied, so the cases go forward); LTL LED v. Google, the Wolf River Electric case (going forward after the federal court sent it back to state court); and Murray v. Alphabet and two Grybniak cases against Google and xAI (filed, no judicial action yet).

How do I prove what an AI chatbot said about me?

Every one of these cases needs the same thing before any legal question: what exactly the AI said, in response to what, and when. The person harmed usually has only a screenshot or a share link, and the AI company's copy is under its control and may be kept only for a limited time.

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 AI chatbot answer about me: a hash of my question, a hash of the exact exported answer, the product and model it showed, and when I saw it, so I can show later the copy wasn't changed.”

One-click setup

{
  "tool": "record_ai_run",
  "arguments": {
    "model": "<model name the product showed>",
    "provider": "<AI company>",
    "prompt_sha256": "<sha256 of your exact question>",
    "output_sha256": "<sha256 of the exported answer file>",
    "params": {
      "share_link_saved": true,
      "export_format": "txt"
    },
    "ran_at": "2026-11-10T07:00:00Z"
  }
}

Rightshold doesn't contact AI companies, remove outputs, or decide whether something is defamatory or who is responsible. A receipt proves what was recorded and when Rightshold recorded it, not that the AI produced it or that the claim is false. The cases above are reported as of the dates given and may have moved since. Not legal advice; talk to a lawyer about your situation.

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}}'