Circuit schematics

Identifies documents containing references to circuit schematics 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(?:circuit\s+schematics|schematic\s+diagram|circuit\s+design|intellectual\s+property|trade\s+secrets|proprietary\s+design|PCB\s+layout|hardware\s+design|electronic\s+design|circuit\s+board)\b

Corroborative evidence keywords

circuit schematics, circuit, schematics, intellectual, property, trade, secrets

Proximity: 300 characters

Should match

• circuit schematics — Primary topic phrase match
• schematic diagram — Case-insensitive topic phrase match
• circuit design — Alternative topic phrase match
• intellectual property — 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
• algorithm schematic — Generic word pair from old broad template should not match

Known false positives

• Common words and phrases related to circuit schematics 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://www.ipaustralia.gov.au/patents/what-are-patents
• https://www.ipaustralia.gov.au/designs
• https://www.ipaustralia.gov.au/tools-and-research/business-resources/non-disclosure-agreements