By · Last updated 2026-04-22

返回博客法律科技

法律证据开示中的可逆加密

文件已经脱敏,法官却命令你提交原件。该怎么办?2024 年 GDPR 罚款总额达 12 亿欧元,创历史新高。

April 22, 20269 分钟阅读
legal discovery reversible encryptionpermanent redaction liabilitye-discovery original documentsspoliation sanctionsprivilege log documentation

title: "法律证据开示中的可逆加密" description: "文件已经脱敏,法官却命令你提交原件。该怎么办?2024 年 GDPR 罚款总额达 12 亿欧元,创历史新高。" category: legal-tech publishedAt: 2026-04-22 tags:

  • legal discovery reversible encryption
  • permanent redaction liability
  • e-discovery original documents
  • spoliation sanctions
  • privilege log documentation readingTime: 9

两项看似冲突的义务

法律团队同时承担着两项义务。

其一:向外部律师、共同律师和专家共享脱敏文件。客户姓名和第三方个人信息必须保密。

其二:当法院命令时,必须提交原始记录。《联邦民事诉讼规则》不允许律所篡改这些文件。

理论上,两者可以并存:在内部保留原件,向外部共享脱敏副本。

实践中,许多律所却在这一点上栽了跟头。他们使用的硬性删改工具会直接销毁源数据。他们保留的副本本身就是删改后的版本,根本不存在干净的原件。一旦法院命令下达,他们什么都拿不出来。

证据销毁的风险

无法提交法院命令的记录有一个法律术语:证据销毁(spoliation)。

法院可以采取多种惩罚措施:发出不利推论令、排除证据,情节严重时甚至可以驳回诉讼请求或直接判决。

Bloomberg Law 2025 年调查发现,73% 的律所在使用 AI 工具时未追踪个人信息的去向。这一盲区很可能同样存在于硬性删改工具的使用中——律所脱敏数据却无法还原。

2024 年 GDPR 罚款总额达 12 亿欧元。数据处理失当的代价是真实存在的。

可逆加密的解决方案

解决方案其实很简单:用可逆脱敏替代硬性删除。

AES-256-GCM 加密是确定性的。「John Smith」每次都映射到同一个令牌——在整个文件中,在相关文件之间,始终如一。密钥与文件分开存储。

对外共享脱敏文件;如果法院命令提交原件,密钥持有人在几分钟内即可完成解密并交付。

这一方案同样满足 FRCP Rule 26(b)(5) 关于特权日志的要求。该规则要求律所说明哪些内容被扣留、时间、经手人及理由——加密日志恰好提供了这一切。

了解令牌系统的完整工作原理,请阅读我们的合规概览,了解该流程如何满足司法义务。

制药行业案例

一家药企向合同研究机构(CRO)共享临床试验数据。

文件离开药企前,患者 ID 已完成脱敏。CRO 在干净的数据上开展工作。当 FDA 要求提交原始患者记录时,合规团队解密并提交,附带完整审计追踪。

审计结束后,通过密钥轮换终止 CRO 的访问权限——无论过去还是未来。离职的 CRO 员工无法访问历史记录。

这正是双重合规模型的精髓:共享期间保护数据,法院或监管机构要求时随时恢复原件。

更多适用场景,请参阅我们的安全保护概览

参考来源

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

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