By · Last updated 2026-04-08

返回博客法律科技

法律文件脱敏:格式保留问题的解决方案

Bloomberg Law 2024年调查显示,73%的法律专业人士在使用第三方脱敏工具时遭遇格式损坏。司法部爱泼斯坦档案的脱敏事件揭示了文本层的安全漏洞。

April 8, 20268 分钟阅读
legal document redactionWord formatting preservationlaw firm complianceABA redaction standardscourt document preparation

Word文档格式与法律脱敏

2026年更新版

大多数脱敏工具是为PDF设计的,并非为Word文件开发的。当您对.docx文件运行这些工具时,它们会先进行格式转换——从Word转为PDF,或转为其他格式。格式损坏正是在这一环节发生的。

Bloomberg Law 2024年调查发现,73%的法律专业人士表示在使用第三方脱敏工具时遭遇格式损坏。这绝非小问题:法院提交的文件有严格规定,包括页边距、字体、行距和页码;劳动仲裁陈述必须与原件格式一致;专家证人报告需要整洁的排版才能显示可信度。格式错误会在任何人阅读内容之前就引发问题。

当工具破坏段落样式或表格结构时,文档必须手动重建。一项20分钟的工作可能产生2至4小时的修复工作,彻底抵消了自动化带来的时间节省。

PDF文本层问题

2025年1月,司法部发布爱泼斯坦档案时使用了黑色遮盖框。这些遮盖框在PDF视图中覆盖了文字,但文本层依然完整保留。任何人都可以将其复制粘贴到其他应用程序中,读取被隐藏的内容。

这与格式损坏并不相同,但两种失败有着相同的根本原因:工具只改变视觉层,而不触及数据层。

ABA第498号正式意见(2021年)要求律师具备使用技术的能力。ABA此后已将这一要求延伸至输出审查。提交有缺陷文件的律师可能已违反职业规则,即便错误是由工具造成的,责任仍归属于执业者。

原生编辑从根本上解决两个问题

解决方案是原生文档编辑。在Microsoft Word内部运行的工具使用Word对象模型,直接读写DOCX文件,无需格式转换,因此不会损坏格式。

原生Word集成提供四项具体保护:

样式保留。 段落样式——标题1、正文、正文文本——保持完整。编辑后的文本保留与原文相同的字体和字号。工具只改变内容,不改变文件格式。

表格结构保留。 Word表格使用合并单元格、自定义边框和特定布局规则。原生编辑保留所有这些设置。基于格式转换的工具往往会破坏或扁平化表格结构。

修订记录与批注。 许多法律文件处于审阅状态,包含对方律师的修订记录,以及合伙人和客户的批注。原生编辑保留所有这些元数据,而格式转换会将其删除。

页眉、页脚和脚注访问。 姓名可能出现在页眉中,案号可能出现在页脚中,关键事实可能出现在脚注中。原生编辑能够访问所有这些区域,而基于转换的工具往往会忽略它们。

处理结果是一份整洁、完整的文档,与输入时完全一致,可随时提交,无需手动修复。对于同时处理多个案件的团队而言,这种一致性至关重要——每份文件一次性通过法院要求。

如需了解合规全貌,请参见ABA标准与律师事务所合规要求。关于PDF文本层失败的真实案例,请参见PDF脱敏陷阱。成本数据请参见律师事务所Word插件脱敏成本

参考资料

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

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