By · Last updated 2026-03-22

Back to BlogLegal Tech

Defending Redactions: AI Scores in Court

A judge asked why 47% of a document was redacted. The answer 'the AI flagged it' is not legally defensible. Here's what defensible automated redaction.

March 22, 20268 minute read
defensible redactionAI confidence scorese-discovery audit trailprivilege log requirementslegal tech compliance

title: "Defending Redactions: AI Scores in Court" description: "A judge asked why 47% of a document was redacted. The answer 'the AI flagged it' is not legally defensible. Here's what defensible automated redaction looks like." category: legal-tech publishedAt: 2026-03-22 tags:

  • defensible redaction
  • AI confidence scores
  • e-discovery audit trail
  • privilege log requirements
  • legal tech compliance readingTime: 8

Updated for 2026

"The AI Did It" Fails in Court

AI tools have created a new legal risk. Lawyers often cannot explain why a system blocked content. When a judge asks, "the algorithm flagged it" is not enough.

FRCP Rule 26(b)(5) sets the bar. A party withholding material must state the claim. They must also describe the documents. That description must let the other side assess privilege — without revealing the content itself.

"The ML model removed it" fails that bar. The other side cannot tell what was detected. They cannot tell why.

Over-Redaction Drives Disputes

Morgan Lewis Q1 2025 e-discovery research flagged over-redaction as an active dispute source in federal courts. The trend links to high-sensitivity AI tools. These tools favor recall. They catch everything that might be sensitive.

The side effects are predictable. Dates near a name get blocked. Exhibit numbers get blocked. Context is ignored.

Opposing counsel then challenges each blocked item. The producing party must explain each one. No per-entity record means no explanation is available.

AI tools set to maximize recall are designed to catch everything. That design is appropriate for some use cases. For e-discovery productions, it creates liability.

When challenged items cannot be explained, courts may order re-production. Re-production costs time and money. In some cases it invites sanctions.

Three Things Defensible Systems Need

Courts review challenged items one by one. They ask a narrow question. What is the basis for this specific item in this specific document?

Most AI tools cannot answer that. Three features make it possible.

Per-entity confidence scores. Each blocked item must trace to a scored detection. "Name detected at 94% confidence" is defensible. "Flagged by ML" is not. For how scoring works in practice, see Why Binary PII Detection Fails Compliance.

Entity type classification. Each blocked item must map to a recognized type. Person name. SSN. Date of birth. That type goes in the privilege log. It explains the basis for withholding without revealing the content.

Threshold records. The configuration must be documented. Which sensitivity levels were used? Which entity types were in scope? Opposing counsel can request these records. The producing party must be ready to explain each choice.

The 83% Governance Mandate

IAPP 2025 research found that 83% of AI governance frameworks require data minimization at the AI input layer.

Earlier frameworks focused on AI outputs. Now they also cover what goes into AI systems. The shift is significant.

For legal teams, the impact is direct. The same minimization duty applies to AI review tools used on client files. Teams must reduce sensitive data before it reaches the tool.

Two duties now overlap. Confidence score records back privilege claims in disputes. Input minimization meets AI governance rules. Together they define the compliance baseline for AI-assisted legal work in 2025.

What the Audit Log Must Capture

The log must record six things for each document processed.

First: the document identifier. Second: entity type. Third: confidence score. Fourth: method applied — label or black box. Fifth: configuration version in use. Sixth: date and time of processing.

This log serves two purposes. It backs the privilege log when a production is challenged. It also shows regulators that sensitive data was minimized before it left the firm.

For how courts handle improper withholding and the sanctions that follow, see E-Discovery Sanctions: When AI Redaction Goes Too Far.

Building this log is not overhead. It is what lets a legal team defend its choices — to a judge, to opposing counsel, or to a data protection authority.

Sources

Ready to protect your data?

Start anonymizing PII with 285+ entity types across 48 languages.

About this page

We update this page when our platform or the law changes.

Read our founder note for how we work.

Each change shows up in the timestamp at the top.

Related reading

We follow these rules

  • GDPR (EU 2016/679).
  • ISO/IEC 27001:2022.
  • NIS2 (EU 2022/2555).
  • HIPAA safe harbor under 45 CFR § 164.514(b)(2).

Our promise

We do not sell your data.

We do not train models on your text.

We store your files in Germany.

You can delete your account at any time.

You own your work.

Where we run

Our servers live in Falkenstein, Germany.

We use Hetzner. They hold ISO 27001 certification.

All data stays in the EU.

Backups run every day.

Need help?

Email support@anonym.legal.

We reply within one business day.

How we test

We run a full check suite on every release.

Each surface gets its own sweep script and report.

Human reviewers spot-check the output each week.

We track recall and precision on a labelled set.

Bad runs block the deploy.

What we never do

  • We never sell your information to third parties.
  • We never train models on what you upload.
  • We never keep your work after you delete it.
  • We never share keys with any outside firm.
  • We never run ads inside the product.

Plans in plain words

We sell credits, not seats.

One credit covers one short job.

Long jobs use a few credits each.

You can top up at any time.

Unused credits roll over each month.

Read the plans page for current rates.

Who built this

A small team of engineers and lawyers built this.

We ship from Europe and work in the open.

Our founder note spells out why we started.

Where to start

How the parts fit

A browser add-on cleans text inside Chrome.

A Word plug-in handles drafts in Office.

A small desktop tool works on whole folders.

An agent protocol link feeds large models safely.

All four share one core engine and one rule set.

Words from our team

We started this work after a lunch about cookies.

One friend kept getting odd ads on her phone.

We asked why a court file leaked through a draft.

We sketched the first build on a napkin that week.

By month three we had a tiny demo for a friend.

She used it on her first case the next day.

Common questions we hear

Can the tool read scanned PDFs? Yes, with OCR.

Does it work on long files? Yes, in small chunks.

Can I roll my own rule set? Yes, save it as a preset.

Does it run offline? The desktop build runs offline.

Do you keep my files? No, the cloud build wipes after each run.

Will it learn from my work? No, we never train on inputs.

A short tour of the workflow

Upload a file or paste a snippet of prose.

Pick the entities you want gone from the draft.

Choose a method: replace, mask, hash, encrypt, or redact.

Press run and watch the side panel show each hit.

Skim the result and tweak any rule that misfired.

Save the cleaned file or send it to a teammate.