By · Last updated 2026-03-12

返回博客法律科技

电子证据开示制裁:AI遮盖过度的法律风险

在Athletics Investment Group诉Schnitzer Steel案(2024年)中,不当遮盖引发了证据开示制裁。AI工具精确率仅为22.7%,法律团队面临真实的法律责任。

March 12, 202610 分钟阅读
e-discovery sanctionsredaction liabilityAI redaction precisiondocument reviewlegal technology

2026年更新

遮盖失败的两种方式

法律团队面临两种失败模式,均会产生真实的法律责任。

遮盖不足会暴露必须保密的特权数据或个人信息——当事方披露了本有权利、往往也有义务保护的材料。

过度遮盖则隐藏了对方律师有权查阅的事实。法院将此视为妨碍司法行为,属于可受制裁的证据开示违规。

重视召回率而非精确率的AI工具在设计上会导致第二个问题:将文件80%的内容涂黑的AI引擎确实不会遗漏任何内容,但结果毫无用处,还可能引发法院制裁。

两种失败模式的终点相同:法官、解释和费用。

Schnitzer Steel案(2024年)

Athletics Investment Group诉Schnitzer Steel(2024年)展示了法院如何处理不当文件扣押。

一方提交了带有大量标记的文件,对方律师提出异议。法院审查材料后认定标记超出了法律允许的范围。

结果:依据联邦民事诉讼规则第37条实施制裁。提交方为存在缺陷的程序付出了代价。

此类制裁并不新鲜,法院多年来一直在使用。这个案件的突出之处在于时机:AI辅助审查已在诉讼中普及,案件提出了一个关键问题:法律团队在将AI工具投入生产使用前是否检验过其精确率?

22.7%的精确率问题

Presidio是由微软开发的开源PII检测引擎,在文件审查工具中被广泛使用。在法庭文件和合同上的测试显示其精确率为22.7%

精确率衡量阳性标记正确的频率。在22.7%的精确率下,每100个标记中约77个是误报——这些内容按任何适用标准都不敏感。

对于电子证据开示,计算是直接的:以该精确率处理的10,000份文件会有数千个无依据的标记。提交方面临与Schnitzer Steel被告相同的风险:被质疑的提交物、法院审查和可能的制裁。

精确率优先的审查

法院在审查争议标记时提出一个狭义问题:每处标记是否有特权、保密规则或法院命令支持?法院不会问提交方的工具是否尽可能多地标记内容。

没有适当依据的标记就是证据开示违规,无论是人工还是AI作出的都一样。

对于律师来说,这意味着AI审查工具需要以精确率——真正享有特权的标记比例——而非仅以召回率来衡量。一个在22.7%精确率下达到90%召回率的工具捕获了更多敏感内容,但也为77.3%的误报创造了审查负担。当这种审查没有发生时,广泛的过度扣押随之而来。

Schnitzer Steel案之后,每一处提交中的标记都是向法院发出的声明:这一内容是合法扣押的。该声明必须经得起审查。

请参阅AI精确率在法律文件审查中的指南律师-委托人特权与AI了解更多背景。

参考资料

准备好保护您的数据了吗?

开始使用 285 种实体类型在 48 种语言中匿名化 PII。

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.