Collect Less, Expose Less

The concept

Information collected for a task creates obligations and opportunities for misuse. Data minimization means reducing collection, access, and retention to what a defined purpose needs. Removing names is useful but may not make records anonymous: combinations of attributes can still distinguish people, particularly in small communities or unusual circumstances.

Worked example

A fictional community center analyzes workshop attendance. It needs session counts and broad time preferences, not participants' personal stories or full addresses. Staff separate operational registration from the aggregate planning report, restrict access to the registration file, and delete working extracts after the approved review period. A table with a single person in a rare category is combined with a larger group before public sharing.

Limits and judgment

Less data can reduce analytical detail and make some fairness questions harder to investigate. The answer is an explicit purpose and access decision, not indiscriminate deletion or collection. Consider what evidence is necessary to evaluate outcomes, document the tradeoff, and use appropriate controls. Privacy is a continuing design concern across the data lifecycle, not merely a notice at signup.

RETRIEVE. REASON. REMEMBER.

Knowledge check.

Choose one answer for each question, then check your reasoning.