Protective order application records

Name: Protective order application records
Creator: TestPattern Community
License: https://opensource.org/licenses/MIT

Identifies documents containing references to protective order application records in international contexts. This information type is classified as personally identifiable information under applicable data protection regulations.

Type: regex
Engine: boost_regex
Confidence: medium
Confidence justification: category-aware structural regex with anchor and context constraints replaces phrase-only detection. Added context gating and exclusion rules improve precision and reduce incidental matches.
Detection quality: Mixed
Jurisdictions: global
Regulations: GDPR
Data categories: pii
Scope: wide
Platform compatibility: Purview: Compatible, GCP DLP: Compatible, Macie: Compatible, Zscaler: Compatible, Palo Alto: Degraded, Netskope: Unsupported

Pattern

(?is)\b(?:protective\s+order|restraining\s+order|protection\s+order|no[\s-]+contact\s+order|domestic\s+violence\s+order|order\s+of\s+protection|temporary\s+protective\s+order|emergency\s+protective\s+order|protection\s+application|stay[\s-]+away\s+order|harassment\s+order|protective\s+injunction)\b

Corroborative evidence keywords

protective order application records

Proximity: 240 characters

Should match

protective order — Primary topic phrase match
restraining order — Case-insensitive topic phrase match
protection order — Alternative topic phrase match
no-contact order — Additional topic phrase match

Should not match

unrelated generic text without domain phrases — No relevant topic phrases present
placeholder value 12345 — Random text should not match topic-specific regex
mugshot victim — Generic word pair from old broad template should not match

Known false positives

Common words and phrases related to protective order application records appearing in policy documents, training materials, HR templates, or compliance guidelines without actual personal data. Mitigation: Require corroborative evidence keywords within the proximity window to confirm sensitive data context rather than general discussion.
In English (as the primary international business language), similar terminology used in formal or administrative contexts (education, professional documentation) that does not constitute sensitive data collection. Mitigation: Layer with additional contextual signals such as structured identifiers, form fields, or database column headers to distinguish sensitive records from general references.
High-frequency pattern matches in large document corpora due to broad regex anchors. Expected match rate is significantly higher than specific identifier patterns. Mitigation: Tune confidence thresholds for bulk scanning. Consider using this pattern primarily as a pre-filter with secondary validation.