Applying Privacy Principles
Applying Privacy Principles to Data Use
In the last unit you learned to size up how much harm a dataset could cause if it leaked. Now you'll add a second lens for the most common request that lands on your desk: someone wants to use information about actual people. Classification asks "how sensitive is this?" Privacy principles ask a different question, "is this use fair to the people the data is about?" Same triage habit you already know, just sharper questions.
Knowing What You're Holding: The Privacy Vocabulary
Before you can judge a request, you need a few plain-language terms. Personal data is any information that identifies a person or could be linked back to one: a name, an email, an address, a customer ID, even a purchase tied to an account. Sensitive personal data is a smaller, riskier subset, the kind of detail that could expose someone to discrimination or serious harm if mishandled: health information, race or ethnicity, religion, sexual orientation, political views, or biometric and financial identifiers. When sensitive data is in play, your antenna should go up immediately.
Around these sit a handful of ideas worth naming. Consent is the person's agreement to a specific use of their data, and purpose is the reason the data was collected in the first place. These two often travel together: data collected for one purpose shouldn't quietly drift into another without fresh agreement.
The other two are about openness and control. Transparency means people were actually told how their data would be used, in language they could understand. And subject rights are the things a person can ask of you: to see what you hold about them, to correct it, or to have it deleted.
These all roll up into the Core Privacy Principles, a short list governance leans on worldwide: use data lawfully, fairly, and transparently; limit it to the purpose you collected it for; collect the minimum you need; keep it accurate; don't keep it longer than necessary; protect it; stay accountable; and respect those individual rights. You don't have to memorize all eight. The four you'll reach for most are purpose, minimization, transparency, and retention, and that's exactly what the next section turns into questions.
Analyzing a Request: Purpose, Minimum Data, Notice, and Retention
When a request to use personal data arrives, run it through four quick questions. The first is purpose fit: does this use match the reason the data was collected? Data gathered to fulfill orders being repurposed for marketing is a purpose mismatch worth flagging.
The second is minimum necessary data, often called data minimization. Look at every field being requested and ask, "does the stated goal actually require this one?" The instinct to grab "everything, just in case" is the single most common privacy risk you'll meet, and it's usually easy to trim.
The third is notice expectations: were people told their data might be used this way? If a customer would be surprised to learn what's happening with their information, that's a transparency gap.
The fourth is retention limits: how long will this data live once the work is done? "Keep it forever" is rarely the right answer. A clear end date is part of using data responsibly.

