PII detection and redaction for AI systems in Europe.
Guard scans, detects, and redacts personally identifiable information before it reaches your AI models — or leaves your systems. Available as an MCP server for agentic AI workflows and as a REST API for any stack. Built for the EU: Spain, Ireland, Germany, France, and Italy.
Native to agentic AI and to any existing stack.
Guard ships as an MCP server — so AI agents call it as a native tool with no custom integration. It also ships as a standard REST API for any backend, pipeline, or SDK workflow.
Guard exposes a set of MCP tools that any MCP-compatible AI client — Claude, Cursor, or your own agent — can call directly. No SDK, no integration code. The agent decides when to scan; Guard runs transparently inside the tool loop.
- Works with Claude, Cursor, and any MCP client
- guard_scan · guard_audit · guard_locales tools
- Automatic jurisdiction detection from input
- Signed audit record returned with every call
A stateless HTTPS API. Drop Guard into your LLM pipeline as a pre-processing step and your models never see raw PII. Python and Node.js SDKs available for preview participants.
- POST /v1/scan · GET /v1/audit
- Python SDK · pip install provenancecode-guard
- Node.js SDK · npm install @provenancecode/guard
- Full OpenAPI spec included
Guard as a tool inside your agent's reasoning loop.
MCP (Model Context Protocol) lets AI models call external tools natively — the same way they call a web search or a code interpreter. Guard exposes three MCP tools. When an agent processes text that might contain personal data, it calls guard_scan automatically. No middleware. No custom integration. Privacy by design, enforced at the agent layer.
Every PII type that matters in European law.
Guard's entity recognition is tuned to the identity document formats, national ID schemas, and data patterns that regulators in each EU market actually require you to protect. Generic models miss them. Guard doesn't.
ES: DNI/NIE · IE: PPSN · DE: Personalausweis · FR: CNI · IT: Codice Fiscale. Format-aware — validates checksum patterns, not just regex.
IBAN (ES/IE/DE/FR/IT prefixes), payment card numbers, bank account references, and VAT numbers across all five jurisdictions.
Postal addresses, postcode formats, phone number patterns (+34, +353, +49, +33, +39), and IP addresses for each market.
Health data, biometric references, religious or political indicators. Flagged under GDPR Article 9 with an elevated risk score.
Email addresses, usernames, device IDs, cookies, and OAuth tokens — the identifiers that make users individually reachable.
Block (██████), synthetic substitution (same format, no real PII), or tokenisation for reversible de-anonymisation. Specified per call.
Five markets. One API. Same GDPR standard.
Each EU market has its own identity document formats, phone patterns, and local compliance obligations layered on top of GDPR. Guard handles jurisdiction detection automatically — pass the locale hint if you have it, or let Guard infer it from the text.
Built against the regulation, not around it.
Article 5 (data minimisation) · Article 25 (privacy by design) · Article 32 (security of processing). Guard provides the technical measure that satisfies all three when PII passes through AI systems.
High-risk AI systems processing personal data require documented safeguards. Guard produces a signed audit record for every scan — machine-readable evidence for your conformity assessment.
AEPD · DPC · BfDI · CNIL · Garante. Each national supervisory authority can request evidence that PII was protected. Guard's audit trail is structured to answer that question directly.
Scan. Detect. Redact. Record.
The same four steps whether you call Guard via MCP or via the REST API. The difference is who initiates the call — your agent, or your application code.
Built for teams processing European personal data with AI.
You're accountable under GDPR Article 37. Your organisation has deployed AI tools that process personal data. You need a documented, auditable technical control — not a policy statement.
PII leaking into LLM context windows is a data breach risk. Guard is the technical control that prevents personal data from reaching third-party AI APIs — and proves it with a signed record.
You're building LLM-powered features for users in Spain, Ireland, Germany, France, or Italy. Guard is the pre-processing layer — via MCP or API — that makes it safe and compliant to ship.
When a DPA investigation starts, you need evidence. Guard's signed audit records show, for every AI interaction, what PII was detected, what was redacted, and which GDPR provision applied.
Request access. Know exactly what happens next.
One provenance standard across your full AI stack.
Guard protects data before it enters AI. Verity governs AI-generated code at the Git layer. Agent OS governs AI agent actions at runtime. All three share the same signed audit record format — one consistent compliance trail, end to end.