Deceased-person records with cultural sensitivity

Identifies records about a deceased person that carry cultural-sensitivity handling requirements (for example Aboriginal and Torres Strait Islander name and image restrictions): a deceased-person record with populated person fields and explicit cultural-protocol evidence.

Type: regex
Engine: boost_regex
Confidence: medium
Confidence justification: Medium: death-record vocabulary is common in probate, guidance and news; enforcement needs a populated deceased-person record and cultural-protocol evidence that the primary does not itself match.
Detection quality: Topic false positive
Jurisdictions: global
Regulations: Privacy Act 1988 (Cth), Information Privacy Act 2009 (Qld)
Frameworks: ISO 27001, ISO 27701
Data categories: pii, government
Scope: wide
Risk rating: 3
Platform compatibility: Purview: Compatible, GCP DLP: Compatible, Macie: Compatible, Zscaler: Compatible, Palo Alto: Degraded, Netskope: Unsupported

Pattern

(?is)\b(?:deceased\s+person|deceased\s+estate|death\s+record|cultural\s+sensitivity|Aboriginal\s+deceased|Torres\s+Strait\s+Islander|sorry\s+business|death\s+notification|next\s+of\s+kin)\b

Corroborative evidence keywords

deceased-person records with cultural sensitivity, deceased, person, records, cultural, sensitivity, personal, identity, demographics, address, age, birthday, citizenship, city, date of birth, [object Object], email, ethnicity, fax, first name (+42 more)

Proximity: 300 characters

Should match

Death notification - Aboriginal deceased Name of deceased: Jamie Teston Date of death: 02/08/2026 Community: Palm Island Senior next of kin: Morgan Teston Cultural protocol: the family requests that the name and images are not used; use the replacement name advised by community authority. — 85 - populated deceased-person record with cultural-protocol evidence
Deceased estate file Name of deceased: Riley Teston The family asked that images of the deceased are not reproduced, in line with cultural protocol. — 75 - one populated record field plus cultural-protocol evidence
Aboriginal deceased record: restricted image under community cultural protocol. — 65 discovery - cultural restriction without populated record fields
Death record received from the registry for the estate file. — 65 discovery - death-record mention without fields or cultural evidence

Should not match

unrelated generic text without domain phrases — No relevant topic phrases present
Deceased estate notice sent to next of kin. — Generic probate wording without cultural-protocol evidence stays discovery-only
Cultural sensitivity training for customer service. — Culture wording without a deceased-person record must not enforce
Cultural protocol guidance: when a deceased person is Aboriginal or Torres Strait Islander, ask the family before using their name or image. — Guidance naming the protocol - no populated record (65 at most)
Death notification form Name of deceased: ________ Date of death: __/__/____ Community: [if known] Cultural protocol: [family advice] — Blank form - placeholder fields are rejected
Warning: this story contains images of a deceased person. The community asked media to respect cultural protocol. — News warning - no populated record fields

Known false positives

Common words and phrases related to deceased-person records with cultural sensitivity 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 Australian English, 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.