By George Curta · Last updated 2026-06-14
Vibe Coding 安全：防止 AI 生成代码中的 PII 泄露
Cursor、Windsurf 和 Claude Desktop 以高速发布生产代码 — 但没有 PII 保护措施。在敏感数据到达您的 AI IDE 之前进行匿名化处理，并从生成的代码中自动删除它。
为什么 Vibe 编码会产生 PII 风险
Vibe 编码加快了开发速度 — 但 Cursor 和 Windsurf 等 AI IDE 会吸收您整个代码库上下文，包括测试和 fixture 中使用的任何真实数据。PII 悄悄地泄露到模型上下文、日志和生成的输出中。
AI 辅助开发中的已知风险：
- CVE-2026-22708（Cursor IDE）： 打开文件中的凭证和 PII 数据未经过滤地传输到模型上下文。CVSS 8.1。
- LangChain CVE-2026-22708： CVSS 9.3 — 通过 RAG 文档进行的提示注入将 PII 注入到无意的模型输出和日志中。
- 8000+ 暴露的 MCP 服务器： 公开的 MCP 服务器扫描发现数千个处理原始 PII 而没有清理的服务器，违反了 GDPR 和 HIPAA。
为开发者工作流程而构建
原生 IDE 集成
MCP 服务器直接连接到 Cursor、Windsurf、Claude Desktop 和 VS Code。在您现有的工作流程中进行透明的 PII 匿名化。
285+ 实体类型
检测名称、电子邮件、API 密钥、凭证、SSN、IBAN 和 285+ 其他 PII 类型，跨越 48 种语言。
可逆匿名化
用一致的占位符替换 PII（例如 [PERSON_1]、[EMAIL_1]），以便 AI 生成的代码保持有效。一步去匿名化以恢复原始值。
零知识架构
您的加密密钥永远不会离开您的设备。anonym.legal 无法读取您的原始数据。使用 CSPRNG 支持的 AES-256-GCM 加密。
符合 GDPR 和 HIPAA
欧盟数据驻留。匿名化符合 GDPR 第 4(1) 条定义。为 DPA 询问和 HIPAA 合规性文档准备就绪的审计报告。
审计日志
每个匿名化事件都被记录 — 检测到的实体类型、时间戳和会话 ID — 用于合规审计。
在 5 分钟内设置
创建免费账户
在 anonym.legal 注册 — 免费层包括每月 200 个 token、所有 285+ 实体类型和 Pro 计划上的完整 MCP 服务器访问权限。
将 MCP 服务器添加到您的 IDE
将 anonym-legal MCP 服务器配置添加到您的 claude_desktop_config.json 或 Cursor 设置。一个 JSON 块 — 无需二进制安装。
在每个 AI 提示前进行匿名化
MCP 服务器拦截包含 PII 的提示，并在模型看到它们之前将实体替换为一致的占位符。完全透明。
去匿名化 AI 输出
将 AI 生成的代码粘贴到去匿名化端点（或 Chrome 扩展）以恢复原始值。您的真实数据从未接触过该模型。
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
- Common questions
- Glossary
- How tokens work
- Security posture
- Where we comply
- What we detect
- Case studies
- Release notes
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
- Open the web app and try a sample file.
- Learn how credits get counted.
- See current plans and limits.
- Meet the team behind the product.
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.