By · Last updated 2026-06-30

您的数据已经进入 ChatGPT

77% 的员工会将敏感数据粘贴到 AI 工具中。生成式 AI 已成为企业中排名第一的数据泄露渠道。anonym.legal 在 PII 到达 AI 模型之前予以拦截——在保障生产力的同时规避风险。

77%
的员工将数据粘贴到生成式 AI
32%
的数据泄露现通过 AI 发生
900K+
用户受 AI 对话窃取扩展影响

AI 数据危机已然来临

您的员工每天使用 ChatGPT、Claude 和 Copilot。他们提交的每一个提示都是潜在的数据泄露——而您对共享内容毫无可见性。

  • !67% 的 ChatGPT 使用通过个人账户在非受管设备上发生
  • !OpenAI 受联邦法院命令,须无限期保存所有对话
  • !两个拥有 90 万用户的 Chrome 扩展被发现窃取 AI 对话
  • !三星在源代码泄露后禁止使用 ChatGPT——员工仍通过个人设备使用

启用 AI,堵住泄露。

anonym.legal 在敏感数据到达 AI 模型之前予以拦截。您的团队保持完整的 AI 生产力,您的数据得到保护。

浏览器保护

在提示到达 ChatGPT、Claude、Gemini、Copilot、Perplexity 和 DeepSeek 之前予以拦截。适用于任何 AI 网站。

开发者工具保护

Model Context Protocol 服务器与 Claude Desktop 和 Cursor IDE 集成。开发者正常工作,数据受到保护。

数据永不离开您的设备

所有匿名化在您的浏览器中本地完成。零知识架构意味着我们无法看到您的数据。

285 种以上实体类型,48 种语言

检测 48 种语言中的姓名、电子邮件、社会安全号码、信用卡、地址及 285 种以上其他 PII 类型。

对比无效的其他方案

  • 适用于个人账户——您目前无法监控的 67% AI 使用情况
  • 仅本地处理——数据从不接触我们的服务器
  • 符合 Manifest V3 规范——符合现代 Chrome 安全标准
  • 零生产力损失——用户照常使用 AI
  • 价格实惠——提供免费套餐,付费套餐起价 €3/月

30 秒内保护您的 AI 工作流

Chrome 扩展免费使用,即时安装,无需注册。立即开始保护您团队的 AI 使用。

Limitations / Important note

  • Anonymizing prompts reduces but does not eliminate data exposure risk; review what you send to third-party AI providers.
  • Detection is probabilistic; high-stakes outputs should be human-reviewed. This is not legal advice.

How we measure — our methodology

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.

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 company HQ is in Saarbrücken, Germany. Our servers run in Hetzner's Falkenstein datacenter.

Hetzner holds 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.