Legal full name

Identifies documents containing references to legal full name 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

Topic false positive

Jurisdictions

global

Regulations

GDPR

Data categories

government-id, pii

Scope

wide

Risk rating

3

Platform compatibility

Purview: Compatible, GCP DLP: Compatible, Macie: Compatible, Zscaler: Compatible, Palo Alto: Degraded, Netskope: Unsupported

Pattern

(?is)\b(?:legal\s+full\s+name|legal\s+name|full\s+name|given\s+name|family\s+name|first\s+name|last\s+name|middle\s+name|personal\s+details|identity\s+document|name\s+change)\b

Corroborative evidence keywords

legal full name, legal, full, name, personal, identity, demographics, address, age, birthday, citizenship, city, date of birth, [object Object], email, ethnicity, fax, first name, full name, gender (+65 more)

Proximity: 300 characters

Should match

• legal full name — Exact 75 probe - canonical label without two additional name-field terms
• legal name — Case-insensitive topic phrase match
• full name — Alternative topic phrase match
• given name — Exact 65 discovery probe - alternative name-field phrase without the canonical legal-full-name label
• Identity verification form. Legal full name of the applicant, including given name and family name, exactly as shown on the identity document. — Exact 85 probe - canonical label with two additional non-overlapping name-field terms

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
• name disability — Generic word pair from old broad template should not match
• Sample: Applicant legal full name, given name and family name — High-like template fixture must be rejected by the shared exclusion dictionary

Known false positives

• Common words and phrases related to legal full name 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.

References

• https://eur-lex.europa.eu/eli/reg/2016/679/oj
• https://www.oaic.gov.au/privacy/your-privacy-rights/your-personal-information/what-is-personal-information