Counseling hotline notes are person-to-person records with highly sensitive personal details. What should constrain the analytics scope for this source?
Select an answer to reveal the explanation.
Short Explanation
Hotline notes are not traffic beepers — they carry someone’s hardest day. Narrow the purpose, strip what you can, and lock the door. Open-data dump thinking does not belong here.
Full Explanation
Certain person-to-person sources carry elevated privacy risk. Counseling hotline notes demand purpose limitation, minimization, and strict access before any Big Data analysis proceeds. Civic analytics may still use carefully scoped aggregates, but only inside privacy boundaries that protect vulnerable residents who sought help.
Publishing every note on the open data portal first fails by concept: transparency absolutism violates sensitivity. Treating notes like anonymous traffic-counter beeps with no access controls fails by concept: counseling content is highly sensitive P2P. Requiring full names in every dashboard filter by default fails by concept: that maximizes identifiers instead of minimizing them.
Exam caveat: Privacy and sensitivity constrain counseling-note analytics—narrow purpose, minimize identifiers, restrict access; do not open-publish or treat as anonymous sensors.
Operational check: Complete a DPIA or privacy review, restrict analyst roles, strip or tokenize identifiers, and ban open-portal publication of hotline narratives. Document residual risk for civic operators and revisit after the next production change window. Confirm owners, SLAs, and rollback criteria in the runbook before go-live.