How it works
Innovations often collect, store, share, infer, or expose data about people.
Evaluate what data is collected, why it is needed, who can access it, how it is protected, and how it could be misused.
Common error
Opt-in language does not automatically mean users understand every future data use.
Worked example
Assess whether attendance tracking needs continuous location collection.
Data / pseudocode
Goal: record class attendance
Proposal: continuous precise location
Alternative: class-specific check-in
Retention: not yet specifiedContinuous location collects information beyond the stated attendance event. Evaluate whether a narrower check-in can meet the requirement, limit retention and access, and explain the remaining tradeoff. A consent screen alone does not resolve all future-use or disclosure risks.
Exercises
5.2.1
What is data minimization in this scenario?
Show solution
Collect and retain only the information needed to record attendance, rather than unrelated continuous location history.
5.2.2
Why should a privacy review consider sharing partners and retention as well as the initial collection?
Show solution
Later access, combination, reuse, or storage can create risks not apparent when the data was first collected. The full data lifecycle affects exposure.