liveBook · Manning

Sensitive information

As explained in Effective Data Analysis

Protected information is data subject to legal, regulatory, or organizational restrictions governing its collection, use, disclosure, or retention.

Sensitive information is data about people or organizations that could cause harm if disclosed without consent or authorization. Some of it is also protected by laws governing how it is collected, used, stored, and deleted. In analytics, the first question is not how to secure every available field, but whether the analysis needs that field at all. section 8.3 section 8.3.1

Common categories call for different kinds of care:

  • Personally identifiable information (PII), such as names, phone numbers, email addresses, and other identifying characteristics, can link records to an individual. section 8.3
  • Protected health information (PHI) includes diagnoses, medical history, and payment information that can be tied to a person. section 8.3
  • Financial information includes accounts, credit card numbers, and transactions; authentication data includes login credentials, whose exposure can put other data at risk. section 8.3

Data protection regulations may require limited collection and retention, restricted access, and ways for people to learn how their data is used, deny consent, or request deletion. Work with security, IT, and legal teams where available. Collect only what serves a defined purpose, set a retention period, and avoid sending raw records to unauthorized stakeholders or through insecure channels. section 8.2.1 section 8.3.1

A wearable-device health study

A study combining activity data with participants’ heart-disease or hypertension diagnoses needs more than a useful research question. Its consent protocol should explain possible harms and benefits, its handling practices should address the risk of disclosure, and its team should be ready to honor a participant’s request to withdraw consent. section 8.1.3

Removing direct identifiers can reduce exposure, but do not assume a dataset is safe simply because it is labeled anonymized. Pseudonymization replaces identifying information with a key while retaining a way to reconnect records; even anonymized data can be re-associated with individuals. Establish guardrails against re-identification, and consider downstream harms as well as breaches: an automated hiring model trained on biased resumes, for example, penalized women applicants. section 8.4 section 8.0

How Effective Data Analysis covers it

How deep it goes
Defines major data categories and gives handling practices, consent questions, and re-identification cautions without a technical security implementation.
Examples
Uses a wearable-device health study, identifying and financial data categories, and a biased résumé-ranking model.
What it assumes
Assumes an analytics context but defines sensitive-data categories and introduces practical handling decisions without requiring security expertise.
What you can do after
Practice/perform a necessity check, limit collection and access, plan retention, and raise consent and disclosure risks before analysis.
How it connects
Connects sensitive information to data protection regulations, informed consent, data minimization, anonymization, pseudonymization, and bias.

Also explained in

Compare how 8 books explain sensitive information →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Effective Data Analysis. The section links point to the parts of the book it draws on.