By · Last updated 2026-03-04

返回博客法律科技

2026年律师-委托人特权与AI

2026年2月,一家美国联邦法院裁定AI通信不受律师-委托人特权保护。

March 4, 20268 分钟阅读
attorney-client privilegeAI securitylaw firm compliancelegal tech

2026年更新

改变律所AI使用方式的裁决

2026年2月,一家美国联邦法院作出一项裁决,令每家律所的风险团队为之震动。裁决内容为:AI工具的聊天记录不受律师-委托人特权保护

相关事实:一名律师在使用AI助手准备委托人建议时将案件细节提交给了该工具。在随后的诉讼中,对方要求获得这些提交内容。该律师以特权为由提出异议。法院驳回了该异议。

法院的推理逻辑:律师-委托人特权保护律师与其委托人之间的通信。AI工具不是律师,也不是委托人。AI工具是一个第三方系统——是运营该工具的公司的软件。将委托人信息提交给AI工具,就是将其传递给第三方,这破坏了特权要求。

特权被破坏的时点

该裁决的关键不在于律师做了什么,而在于数据去往何处。

律师-委托人特权要求通信保持在受律师-委托人关系约束的人员之间的保密性。当委托人的案件细节离开这个封闭圈子——到达律所防火墙之外、到达AI提供商的服务器——特权就有可能被破坏。

该裁决正式确认了许多律所已经担心的做法:向外部AI工具提交委托人材料等同于放弃特权。

这实际上影响哪些工作

受影响的工作流程

  • 将委托人文件发送给AI进行摘要处理
  • 使用AI起草委托人通信内容
  • 在AI提示词中描述案件细节以获取法律研究建议
  • 将合同提交给AI进行审查,同时包含识别委托人的信息
  • 使用AI分析证据开示材料

不受影响的工作流程

  • 在本地运行的AI工具(数据不离开您的网络)
  • 已在律所内使用匿名化内容的工作流程
  • 向AI询问不涉及委托人具体信息的一般法律研究

技术解决方案

特权保护的技术解决方案的逻辑很简单:如果AI提供商永远不会收到委托人信息,就不存在特权破坏问题。

anonym.legal在任何内容到达AI提供商之前进行处理:

  1. 律师准备要发给AI的提示词(例如,"帮我起草一份委托人的诉状..."
  2. anonym.legal扫描内容中的委托人标识符:姓名、案件号、地址、诉讼细节
  3. 标识符被替换为令牌:[PERSON_1][CASE_ID_1][ADDRESS_1]
  4. 令牌化版本发送给AI
  5. AI响应中的令牌被替换为原始值

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.