SENSITIVE DATA REVIEW · Workflow idea
For an organization-approved processing purpose, assess submitted text for possible personal or sensitive information, prepare a risk category, and apply documented redaction or routing rules. Pattern matching and context checks can miss sensitive content or over-classify ordinary text; never treat a clean result as proof of safety or legal compliance. Minimize what is recorded, keep audit logs access-controlled, and require a privacy or security owner to review uncertain cases and approve any external processing path.
01 / The starting point
An authorized request and documented sensitivity categories and handling rules
“Identify possible sensitive content and apply approved safeguards before further processing.”
02 / The work
Helps a team assess potentially sensitive text and prepare privacy-conscious handling decisions.
Check that the request is permitted and uses only necessary information.
Look for direct identifiers and sensitive context, noting uncertainty.
Keep protected details from reaching destinations not approved for them.
Check access, retention, location, and the purpose of any destination.
Require a privacy or security reviewer before processing continues.
03 / The result
A reviewable sensitivity assessment with handling decision and limited audit record.
Reviews & approvals · Example outcome
A reviewable sensitivity assessment with handling decision and limited audit record.
Detection is fallible and does not establish compliance. Keep unreviewed requests from reaching unapproved services, document why a route was chosen, minimize retained content, and make qualified people responsible for exceptions.
04 / Make it yours
A few choices shape the work around your team.
Set organization-specific handling rules with privacy and security owners.
Do not silently pass ambiguous or high-risk content onward.
Record only what supports review while protecting underlying content.
Review safeguards and data terms before allowing external processing.