By · Last updated 2026-03-05

返回博客法律科技

爱泼斯坦文件:高亮不是遮盖

2025年12月美国司法部公开的爱泼斯坦文件暴露了一个严重的遮盖失误:黑色高亮的PDF文本可通过复制粘贴读取。

March 5, 20267 分钟阅读
document redactionPDF redaction failurelegal complianceWord redaction

2025年12月的遮盖失败事件

2026年更新

2025年12月,美国司法部公开了爱泼斯坦文件。新闻报道迅速从内容本身转向了遮盖问题。

问题立即变得清晰:多个本应遮盖的段落用黑色高亮进行了"遮盖"处理。全选、复制、粘贴到任何文本编辑器中——被遮盖的文本完整地显现出来。

这是技术层面的遮盖失败。文字被视觉遮盖,但没有被移除。底层文本仍存在于PDF文件中。任何能够阅读PDF源代码或进行简单复制操作的人都可以访问这些内容。

为什么这种失败如此普遍

高亮遮盖失败源于对PDF格式工作原理的根本性误解。

PDF文件由层组成。文本层包含实际内容。PDF注释可以在文本上方添加矩形——高亮、黑色方块、任何颜色。这些注释是视觉覆盖层。它们不会修改底层的文本层。

当有人"遮盖"PDF中的文本时,他们往往是在添加一个黑色注释矩形,而不是移除文本。渲染时,黑色矩形遮住了文本,所以看不见了。但文本仍在那里。

Adobe Reader和其他PDF查看器在这一区别上没有直观提示。文档看起来已遮盖。用户假设数据已被移除。

遮盖失败的三种机制

机制1:高亮覆盖(爱泼斯坦文件案例)

  • 文本在上方添加黑色高亮
  • 底层文本完好无损
  • 复制粘贴可获取内容
  • 在任何文本提取工具中可见

机制2:图像未经光学字符识别(OCR)处理

  • 文档扫描后以图像保存
  • "遮盖"仅覆盖图像
  • 更高质量扫描可显示底层文本
  • 增强工具可提高对比度以显现内容

机制3:元数据保留

  • 即使文本被正确移除
  • Word修订历史可能包含已删除内容
  • 文档属性可能显示作者信息
  • 注释可能包含遮盖前的摘要

高调失败案例的模式

爱泼斯坦文件并非孤例。高亮-而非移除的遮盖失败在法律和政府文件中反复出现:

  • 2010年:维基解密获得的外交电报包含可提取的遮盖内容
  • 2021年:美国陆军文件因相同机制泄露遮盖内容
  • 多起联邦法院案例因类似失败而受到制裁

该模式表明,这不是孤立的用户错误,而是PDF工具如何呈现遮盖与文档遮盖实际要求之间的系统性错误认知。

符合技术标准的遮盖

技术上合规的遮盖需要移除底层文本层的内容,而非仅仅在其上添加覆盖层。

正确的方法:

  1. 识别需要遮盖的内容
  2. 从PDF文本层中删除内容(不仅仅是添加覆盖层)
  3. 如果文档包含图像,对图像应用像素级移除
  4. 在保存后的文档上验证遮盖效果——复制粘贴应产生空白或占位符
  5. 检查元数据以确保注释和修订历史中没有保留被遮盖内容

anonym.legal的方法通过替换而非遮盖来解决这个问题:文本中的PII在到达任何第三方之前就被替换为令牌,从根本上消除了遮盖失败的可能性。

请参阅安全合规页面了解令牌替换架构,以及法律合规文档了解该方法如何满足法庭级别的遮盖标准。

参考资料

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

开始使用 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.