Racial or Ethnic Origin
Detects racial or ethnic origin information in person-linked demographic, workforce, intake, census, application, and case records. The detector recognises explicit racial/ethnic-origin phrases and structured race or ethnicity fields, then raises confidence only when the same span contains a data-subject record and a populated attribution. Racial or ethnic origin is protected under GDPR Article 9 and Australian anti-discrimination and privacy law. Topic-grade detector, low confidence by design.
- Type
- keyword_list
- Engine
- universal
- Confidence
- low
- Confidence justification
- Low by design. Racial or ethnic origin is a GDPR Article 9 special category with no fixed format, so it is detected purely by topic vocabulary. The bare word "origin" appears constantly in unrelated contexts (country of origin on customs/shipping forms, "original" documents); the regex is scoped to full disclosure phrases only, and hits should be paired with corroborative keywords (race, ethnicity, ancestry) to raise precision.
- Jurisdictions
- global, au, eu
- Regulations
- GDPR, Privacy Act 1988 (Cth), Racial Discrimination Act 1975 (Cth)
- Frameworks
- ISO 27001, NIST CSF, SOC 2
- Data categories
- pii
- Scope
- broad
- Risk rating
- 7
Pattern
(?i)\b(?:racial\s+(?:or\s+ethnic\s+)?origin|ethnic\s+origin|race\s+(?:and|or)\s+ethnicity|racial\/ethnic\s+(?:origin|background|group|category)|ethnic\s+background|(?:race|ethnicity)\s*(?::|(?:demographic\s+)?(?:field|category|code|response))|racial\s+identity|ethnic\s+identity)\b
Corroborative evidence keywords
race, ethnicity, ethnic, ancestry, heritage, diversity survey
Proximity: 300 characters
Should match
Ethnic origin disclosure topic pending review.— Exact 65 discovery probe - protected-attribute topic without a data-subject recordEmployee diversity survey includes an ethnic origin field.— Exact 75 probe - workforce record context without a populated valueEmployee record: ethnic origin recorded as Torres Strait Islander; selected category confirmed.— Exact 85 probe - person record plus populated origin attributionThe diversity survey asks employees to record ethnic origin voluntarily.— Ethnic origin phrase presentProfile field captures racial identity alongside other equity data.— Racial identity phrase presentThe intake form lists ethnic background under demographic information.— Ethnic background phrase presentPatient intake record records ethnicity: Maori.— Structured ethnicity label in a person record
Should not match
Country of origin: Australia, per the customs declaration.— Near-miss ("origin" alone, "country of origin"), no racial/ethnic origin disclosureThe original document was notarized by a public official.— Unrelated root-word near-miss ("original" vs "origin")The restaurant offers a variety of ethnic cuisines.— Topical mention ("ethnic" alone), no personal disclosure phrasePublic aggregate report on population ancestry statistics by region.— Public aggregate material is not a person-linked racial/ethnic disclosureSample template: employee diversity response, ancestry category recorded as Example Category.— Adjacent template language is not a populated protected-attribute recordData subject profile records nationality as Canadian.— Sibling nationality attribute does not satisfy the racial/ethnic-origin primary
Known false positives
- The bare word "origin" appears in unrelated contexts (country of origin on customs/shipping documents, "original" documents) that have nothing to do with racial or ethnic origin. Mitigation: The regex targets full disclosure phrases and structured race/ethnicity labels rather than the bare word "origin"; enforcement requires a person-record context, and the high tier also requires an attribution signal.