F1 on this PII detection benchmark.
OpenAI reports this corrected PII-Masking-300k F1 score on its Privacy Filter release page. This test came in 23.2 points lower.
On this English PII detection benchmark, Agent Mask reached 96.9% F1 versus 74.2% for OpenAI Privacy Filter. Privacy Filter is an open-weight model for context-aware PII detection in unstructured text; Agent Mask detects PII and returns redacted output, stable replacements, and review metadata in one private de-identification workflow.
Start a trial on Snowflake Marketplace, or get a self-hosted trial key for Docker.
1SELECT agent_mask_en.app_public.mask(
2 [ticket_note, chat_log]
3) AS redacted
4FROM support_tickets;
OpenAI reports a strong Privacy Filter score in its release. This local benchmark tested how OpenAI Privacy Filter and Agent Mask handled 50,000 English PII examples under the same setup. press release
F1 on this PII detection benchmark.
OpenAI reports this corrected PII-Masking-300k F1 score on its Privacy Filter release page. This test came in 23.2 points lower.
F1 on this benchmark, with de-identified output and review details from one private workflow.
faster in this run, measured on a consumer RTX 3080. Production speed depends on deployment and batching.
50,000 English PII examples across names, locations, dates, emails, phone numbers, and URLs. Same test setup for both systems.
The accuracy gap is not subtle. On this PII detection benchmark, Agent Mask outperforms OpenAI Privacy Filter on overall F1, PII found, and match quality. The aggregate numbers are the stronger signal: more PII found, fewer cleanup paths, and a response your team can use.
The scores point to the same operational outcome: Agent Mask misses fewer PII detections than OpenAI's Privacy Filter.
Privacy Filter gives you detections to wrap. Agent Mask returns de-identified text plus entity positions, a ledger, and request-time controls for custom entities and replacement behavior.
A grouped detection result still needs application code for redaction, replacement consistency, review evidence, and writeback.
[
{
"entity_group": "private_person",
"score": 0.99,
"word": "Maya Torres",
"start": 0,
"end": 11
},
{
"entity_group": "account_number",
"score": 0.86,
"word": "CLM-1042",
"start": 24,
"end": 32
}
]
{
"columns": [
{
"deidentified_text": "[PERSON_1] filed claim 8f3a2c91 at ******************.",
"analyzer_results": [
{
"entity_type": "PERSON",
"start": 0,
"end": 11
},
{
"entity_type": "CLAIM_ID",
"start": 24,
"end": 32
},
{
"entity_type": "LOCATION",
"start": 36,
"end": 54
}
]
}
],
"entity_ledger": [
{
"entity_type": "PERSON",
"original": "Maya Torres",
"replacement": "[PERSON_1]"
},
{
"entity_type": "CLAIM_ID",
"original": "CLM-1042",
"replacement": "8f3a2c91"
},
{
"entity_type": "LOCATION",
"original": "Northbridge Clinic",
"replacement": "******************"
}
]
}
A private de-identification response includes the output text, the evidence, and the controls needed for production workflows.
Representative response shapes are shortened for readability. The OpenAI example reflects grouped model output; Agent Mask field names come from the public response format.
OpenAI Privacy Filter is a useful open-weight model for PII detection. In this benchmark, Agent Mask found more PII and already includes the de-identification workflow that your team needs.
OpenAI Privacy Filter can make sense if your team wants an Apache-2.0 model and has the engineering time to host it, tune it, monitor it, and connect it to a redaction workflow.
The benchmark shows Agent Mask found more PII. It also gives you what a redaction workflow needs: de-identified output, review evidence, consistent replacements, custom PII/PHI rules, and private deployment as a Snowflake Native App or self-hosted container.
OpenAI Privacy Filter focuses on context-aware PII detection in unstructured text. Agent Mask detects PII, replaces it, keeps replacements consistent, returns review metadata, and runs in Snowflake or a self-hosted container.
OpenAI Privacy Filter returns detections. Your team still has to turn them into masked text, writeback, and review evidence. Agent Mask returns de-identified text, replacement details, and review details in one workflow.
Define custom PII, PHI, IDs, or policy-specific terms with plain-English descriptions or regular expressions. Privacy Filter uses a fixed taxonomy; custom entities require another detector or application rules.
Use Agent Mask in Snowflake or a self-hosted container so PII does not have to move into a separate model service.
Compare an open-weight PII detection model with a private de-identification workflow that includes redacted output, review metadata, replacement controls, custom entities, document/file support, and deployment choices.
This page uses OpenAI Privacy Filter release materials, local Agent Mask benchmark output, and Agent Mask docs as references.
Hugging Face model card for OpenAI Privacy Filter, including intended use, Apache-2.0 license, English-focused details, and deployment cautions.
OpenAI release page where the 97.43% corrected PII-Masking-300k F1 score for Privacy Filter is reported.
OpenAI PDF model card with benchmark tables, intended-use framing, output shape, and limitations.
Agent Mask docs for redacted text, review details, document details, and redaction details.
Agent Mask docs for choosing what to find, adding custom PII, returning review details, and controlling replacements.
Agent Mask documentation explaining how Snowflake Native App and self-hosted Docker processing stay inside your chosen runtime without sending payloads to Agent Mask.
Agent Mask documentation for self-hosted data flow, network requirements, offline license verification, retention, and hardening.
Keep evaluating redaction options across the same private-runtime, data movement, pricing, and implementation questions.
Compare Snowflake AI_REDACT with Agent Mask for PII redaction in Snowflake: long text, documents, custom entities, consistent replacements, and review metadata.
Compare John Snow Labs with Agent Mask for Snowflake PHI de-identification, clinical notes, audit mapping, custom entities, and private deployment.
Compare Agent Mask with Amazon Comprehend PII for teams that need private de-identification, custom entities, consistent replacements, and deployment in Snowflake or self-hosted infrastructure.
Answers for teams comparing an open PII detection model with a private redaction workflow.
Privacy Filter can fit if you want an open model for English PII detection and your team is ready to host it, test it, and build the redaction workflow around it.
Privacy Filter returns detections, not redacted output. To use it in production, your team still has to host and monitor the model, validate the results, write them back, and turn findings into masked text, stable replacements, and review evidence.
Not as part of the model. It returns the categories the model knows; custom PII/PHI terms, internal IDs, and policy-specific strings require another detector or application rules.
No. Privacy Filter identifies PII; it does not decide how each value should be replaced or keep aliases mapped across related text. Agent Mask can do that in the redaction request.
On the 50,000-example English PII benchmark, Agent Mask reached 96.9% F1 versus 74.2% for OpenAI Privacy Filter, found 99.9% of PII versus 71.2%, and reached 98.1% match quality versus 76.1%. The biggest category gap was location, but the headline result is the aggregate accuracy gap plus the production response shape.
Use Agent Mask when you need production redaction, not just model detections. Agent Mask finds more PII in less time, while also returning de-identified output, replacements, and review details.
If your goal is a production de-identification workflow, you need private deployment, replacement controls, custom entities, redacted output, and review metadata, not just a standalone detection model.