By · Last updated 2026-02-23

返回博客法律科技

法院因遮盖失误对律师实施制裁

在Word中高亮显示文本并非真正的遮盖。法院正在因技术失误导致特权信息暴露而对律师实施制裁。

February 23, 20266 分钟阅读
legal redactione-discoverycourt sanctionsdocument security

两种遮盖失败模式

2026年更新

遮盖失败有两种形式,均可产生法律后果。

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

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

最常见的技术错误

Word高亮不是遮盖

最常见的错误:使用Microsoft Word的高亮功能"遮盖"文本。

这种方法存在根本性缺陷。文本仍存在于文档中。高亮只是视觉覆盖。接收者可以:

  • 选中并复制文本
  • 在Word中移除高亮格式
  • 使用PDF工具提取底层内容
  • 在编辑模式下打开文件查看所有内容

在一起典型案例中,一份法律文件以PDF形式发送,敏感词语似乎被"遮盖"了。对方律师在Adobe Reader中打开,全选,复制,粘贴到文本编辑器——所有"遮盖"内容一览无余。

PDF遮盖工具的局限性

许多PDF遮盖工具只在内容上叠加一个黑色矩形,底层文本并未移除。如果文件随后在编辑模式下打开或通过PDF编辑软件处理,内容会再次显现。

正确的PDF遮盖需要彻底移除底层文本层,而非仅仅在其上方叠加不透明层。

法院案例

2024年律师制裁事件:一名律师在多份证据开示文件中使用了Word高亮遮盖。对方律师识别出该技术错误,向法院提出申诉。法院要求律师解释其遮盖方法的"技术缺陷",并最终对产生额外诉讼成本的一方实施了制裁。

2025年Schnitzer Steel诉讼:法院认定遮盖范围超出法律允许,对当事方依据联邦民事诉讼规则第37条处以制裁。提交方为存在缺陷的程序付出了代价。

如需完整的案例分析,请参阅E-Discovery LLC关于相关性遮盖的分析

技术上合规的遮盖要求

必须满足的标准

内容彻底移除:底层文本必须被删除,不仅仅是被视觉覆盖。任何工具都不应让接收者能够访问"遮盖"内容。

格式完整性:遮盖后的文档在版式上应保持一致。突兀的空白区域可能暴露遮盖了内容,并可能提示遮盖数量。

元数据清除:Word文档包含修订历史、注释和作者信息。这些元数据在提交前必须清除,否则特权通信可能通过文档属性而非正文内容泄露。

可审计的方法论:律师必须能够解释每处遮盖的依据。FRCP第26(b)(5)条要求当事方说明主张依据,并描述被扣留的内容。"AI标记了它"无法满足这一要求。

anonym.legal方法与标准遮盖的对比

标准遮盖从文档中删除内容,内容永远消失。对于诉讼来说,这会产生取证证据保全义务问题——如果原始内容在保全义务生效后被删除,可能引发证据灭失风险。

anonym.legal的令牌方法保留可逆性:

  1. 敏感内容被替换为结构化令牌
  2. 令牌映射表存储在您的控制之下
  3. 令牌化文件提交给AI或第三方
  4. 如法律需要,原始内容可通过映射表恢复

这既满足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.