PII Deletion
Tagged PII, gone everywhere it touched an agent, in one action.
Prefactor is an agent evaluation platform for teams building AI agents: it observes every agent run from development to production, evaluates whether the agent did its job, and shows how to improve it.
Prefactor deletes personal data the moment it needs to: wherever it appears, across every run it touched. Detection and tagging happen continuously via data tagging; this is the action that removes what's tagged, plus the real-time redact, block, or escalate options for the moment PII shows up.
How do I delete personal data an AI agent has processed?
Delete by tag, everywhere at once. Prefactor detects personal data continuously as agents run, using pattern matching for structured data such as email addresses, card numbers and government IDs, and named-entity recognition for names and addresses. Each match is tagged, so deletion is a single action that removes every tagged field wherever it appears. When personal data first shows up, a policy can also redact it, block the action or escalate it in real time.
How PII gets tagged
Detection runs continuously through data tagging: pattern matching for structured PII, email addresses, card numbers, government IDs, and named-entity recognition for unstructured PII like names and addresses, applied to every agent interaction as it happens. The result is a PII tag on the field, not just a one-off alert, so it stays findable and deletable long after the run that produced it.
Deleting it: everywhere it touched an agent
Because tagging is what makes PII findable across every run, deletion is one action against the tag rather than a run-by-run cleanup: find every field carrying the PII tag for a given person or record, and remove it, wherever it appears. For the moment PII is first encountered, Prefactor can also act immediately: redact it, block the action outright, or escalate it to a human reviewer, depending on the sensitivity level configured for that data type. A name flowing through a support agent might simply pass through logged and redacted; a health record surfacing in an unrelated workflow might block the action and page the security team.
Compliance evidence
Every tagging event, deletion, redaction, and escalation is logged and exportable, satisfying GDPR, HIPAA, and PCI DSS requirements for evidence of how personal data is handled and removed. Combined with Prefactor's immutable audit trail, PII events become part of the same record used to answer an auditor's questions about how agents handle sensitive data: see the compliance guides at /compliance for the specific frameworks Prefactor maps to, including EU AI Act, SOC 2, ISO 27001, ISO 42001, NIST AI RMF, and OWASP LLM Top 10.
Frequently asked questions
How does Prefactor detect PII?
How is PII actually deleted?
What happens the moment PII is first encountered?
Related glossary terms
Drop this into what you already run
TypeScript and Python SDKs, plus OpenTelemetry ingest — native for LangChain, Claude, Vercel AI, OpenClaw and LiveKit, with 15 framework integrations covered out of the box.
$ prefactor init
See it on your own agents
Book a demo and we'll walk through pii deletion on a fleet like yours — real frameworks, real traces.
Unified performance platform for agents, authentication, and risk management