By George Curta · Last updated 2026-06-30
PII Anonymization API for Developers
An anonymization API is a developer endpoint that strips PII from text inside your own pipelines. Ship privacy-first applications with anonym.legal's REST endpoints for CI/CD integration, MCP Server for AI tools, and consistent anonymization across 48 languages.
과제
개발팀은 현실적인 테스트 데이터와 데이터 보호 사이의 지속적인 긴장에 직면합니다:
- •프로덕션 데이터에는 직접 사용할 수 없는 민감한 PII가 포함되어 있음
- •합성 데이터는 의미 있는 테스트에 필요한 현실감이 부족한 경우가 많음
- •수동 익명화는 시간이 많이 걸리고 오류가 발생하기 쉬움
- •다양한 환경에서 일관되고 재현 가능한 데이터가 필요함
# Anonymize test data in CI/CD pipeline
curl -X POST https://anonym.legal/api/presidio/anonymize \
-H "Authorization: Bearer $API_TOKEN" \
-H "Content-Type: application/json" \
-d '{"text": "Contact john@company.com", "anonymizers": {"DEFAULT": {"type": "replace"}}}'해결책
RESTful API로 PII 익명화를 개발 워크플로에 직접 통합하세요.
REST API
모든 스택과 통합할 수 있는 간단한 JSON API. 단일 요청으로 분석 및 익명화.
CI/CD 지원
파이프라인에서 테스트 데이터 생성을 자동화하세요. 매번 일관된 결과.
재현 가능
동일한 입력, 동일한 출력. 신뢰할 수 있는 테스트를 위한 결정론적 결과.
빠름
분당 수천 개의 레코드 처리. GPU 불필요.
API Endpoints
Simple REST API with bearer token authentication. Integrate in minutes.
| Endpoint | Method | Description |
|---|---|---|
| /api/presidio/analyze | POST | Detect PII entities in text |
| /api/presidio/anonymize | POST | Anonymize detected entities |
| /api/image | POST | Redact PII from images |
| /api/structured | POST | Process CSV/Excel files |
| /api/presidio/entities | GET | List supported entity types |
Integration Options
REST API
Standard REST endpoints with JSON payloads. Works with any language or framework.
- Bearer token authentication
- Batch processing support
- Webhook callbacks (Pro+)
MCP Server
Model Context Protocol integration for AI tools like Claude Desktop and VS Code.
- analyze, anonymize, deanonymize tools
- estimate_cost for pricing transparency
- Multi-language support in tool calls
Built for developers
Limitations / Important note
- Rate limits and endpoint availability depend on your plan; build in retry/backoff handling.
- Detection results are probabilistic; validate before automated downstream use. This is not legal advice.
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 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
- 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.