By · Last updated 2026-04-09

返回博客法律科技

FOIA积压危机:政府文件自动化脱敏实践

2024财年美国FOIA申请量达150万件,同比增长25%,积压量增长33%至267,056件待处理请求,政府为此耗资7.23亿美元。

April 9, 20268 分钟阅读
FOIA automationgovernment document redactionpublic records compliancebatch Word processingfederal agency efficiency

联邦FOIA积压危机

2024财年,美国联邦机构共收到150万件FOIA申请,同比增长25%。待处理积压量增长33%至267,056件,各机构预计为此耗资7.23亿美元

这一数字揭示出严峻的产能缺口。全联邦机构共有约5,638名FOIA工作人员,面对每年150万件申请,人均处理量约为266件,折合每个工作日刚过一件。对于体量庞大、情况复杂的申请,几乎没有任何处理余地;面对33%的积压增速,更是毫无缓冲空间。而许多机构正在裁减人员,局面愈发严峻。

每份申请为何耗时如此之长

联邦文件大多以Word格式存储:法律备忘录、政策决定和往来函件均保存为Word文件。工作人员必须逐页阅读、逐条适用豁免条款,完成后还须审核校对方可发布。

仅第6类豁免(Exemption 6)就涵盖姓名、地址、社会保障号和出生日期。一份50页的文件中,可能有数十个数据点各需独立审查判断。将这一工作量乘以数千份文件,处理时间的压力便成为结构性问题,而非偶发困境。

人员减少、体量不变——积压的数学账算不过来。

自动化带来的改变

ATF(酒精、烟草、枪械和炸药管理局)在其处理流程中引入自动化脱敏工具后,生产效率提升了20%至30%。这是真实的成果,对于仍在全人工审核的机构而言,实际效益可能还要更高。

文件的自动扫描速度极快:系统识别姓名、证件号及其他受保护信息并逐一标记,工作人员只需核查标记项,而无需逐行通读。扫描耗时以秒计算,人工时间转而用于需要专业判断的场景——这才是人工真正创造价值的地方。

对于一批涉及政策决定的8,000份文件,这种工作方式的转变,决定着在正常人员配备下任务是否可行。

为工作选择合适的工具

政府FOIA工作有明确的需求:文件必须保持Word格式,格式在处理过程中必须完整保留,修订记录、脚注和嵌入对象均须完好无损——文件损坏将给申请人提供质疑的依据。

大批量申请需要批处理能力,每次运行处理数百份文件是基本门槛,而非上限。机构内各工作人员还须始终适用相同的豁免规则,这就需要统一锁定的预设配置。

基于预设的脱敏工作流正是为此而设计:一套预设覆盖第6类豁免下的姓名、地址和社会保障号,另一套覆盖第5类豁免下的审议性材料。工作人员选择合适的预设并审核结果,而无需在每份文件上从头做出每一类别的判断。如需了解更全面的合规图景,请参阅安全与合规概览

ATF的实践成果清楚说明了这意味着什么:同一团队,产出提升20%至30%。当申请量以每年25%的速度增长而人员编制停滞不前时,这样的效益至关重要。

积压问题不会自行消解,但遏制它的工具已经触手可及。

数据来源

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

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