Computer Science and Digital Literacy · 40 minutes
Suggested grades 9–12 · Unit 3: Digital evidence and privacy decisions · Lesson 2 of 2
Privacy by Minimizing a Fictional Data Form
Compare stakeholder needs and reduce unnecessary collection before designing a form.
Mr. S Teaches · Original starter lesson · HS-CS-06 · Grade range is planning guidance.Watch, notice, discuss
Video choices for this lesson
Preview a video, then choose what fits your learners. “Show to class” opens a larger view; use the player’s play and full-screen controls when you’re ready.
Teacher preview needed. Check the language, level and length before showing. YouTube may show ads or related videos.
Big Data Problems: Crash Course Statistics #39
By CrashCourse
Use privacy and transparency concerns as context for deciding which fictional data is necessary.
Open on YouTube: Big Data Problems: Crash Course Statistics #39 (opens a new tab) ↗Cybersecurity: Crash Course Computer Science #31
By CrashCourse
Distinguish protecting collected information from reducing collection; the lesson develops the minimization design.
Open on YouTube: Cybersecurity: Crash Course Computer Science #31 (opens a new tab) ↗Which form field can be removed without preventing the stated task?
An external player loads only after you choose Preview or Show to class. Playback connects to YouTube. Videos belong to their creators; availability and embedding can change.
Learning objective
Produce a minimal-data design and synthesize a discussion’s conflicting claims and unresolved questions.
Before you begin
- Data fields
- Purpose and evidence
- Discussion norms
Gather your materials
- Paper and pencil
- Fictional field and stakeholder cards only
Language to know
- data minimization
- Collecting only information needed for a defined purpose.
- retention
- How long data is kept.
- threat model
- A description of what must be protected,from which failures or misuse,and why.
Understand the concept
Fictional scenario: A club needs to count workshop sign-ups and tell participants if a session changes. Draft fields include name,preferred contact,home address,birth date,health history and workshop choice. Organizer note:“We only need a count and a way to send schedule updates.” Accessibility advocate note:“Some participants may need an alternative way to receive updates.” No real forms or personal data are used. A privacy design starts with purposes,not with collecting everything that might become useful.
Teach it step by step
- Match each draft field to the two stated purposes and mark unnecessary or unresolved fields.
- Propose an alternative using a participant-chosen identifier,workshop choice and optional approved contact route,with a non-digital update option.
- Assign organizer,participant and reviewer roles;set a five-minute discussion deadline and compare usefulness,access and retention concerns.
- Synthesize all positions,resolve one contradiction and list specific information still needed before selecting an actual communication process.
Make the thinking visible
Worked example or model response
A possible paper design uses a chosen sign-up code and workshop choice for counting,plus a separate optional contact preference for updates. Delete unneeded address,birth date and health-history fields. A retention proposal removes the contact list after the workshop’s update needs end;an actual policy would require the responsible organization’s decision.
Guided practice
Discuss whether a public attendance list is necessary to send private schedule updates. Record one viewpoint and an evidence-based response.
Independent practice
Write a minimal-field proposal with each field’s purpose,a retention decision to confirm,and an accessible update alternative. Add a discussion synthesis naming a disagreement,its resolution if possible,and two unanswered implementation questions.
Quick assessment
Why is“we might use it someday”not a sufficient purpose for every sensitive field?
Answer key & assessment criteria
Answers and teaching guidance
- Guided: Public attendance disclosure is not necessary for the stated update purpose;a separate private route or non-digital notice can serve it.
- Independent criteria: Fields tied to stated needs,unneeded sensitive fields omitted,access option preserved,retention explicitly considered,and a fair synthesis with questions such as who controls access and when updates end.
- Quick check: An undefined future use cannot establish necessity and creates avoidable collection and retention burdens.
Look for: Require the learner to explain the interpretation and check, not only state a result. Assess the written trace or evidence record; do not request real passwords, accounts or personal data.
Make it work for your learner
More support
Use purpose→field cards and provide stakeholder sentence frames.
Extension challenge
Compare a fully anonymous count with an optional contact list and explain which stated purpose each can or cannot meet.
Verified references · Selected contributions
Standards connections
Subject-content alignment not yet verified
Supporting literacy connections
These records apply to the specified reading, writing or communication task. They do not establish subject-content alignment.
Supporting Common Core connection
SL.11-12.1.d
Common Core · Grades 11–12
Synthesize conflicting discussion claims and identify additional information needed.
Read the official standard ↗Supporting grades 11–12 speaking/listening practice in the explicit design discussion; this is not a verified computer-science or privacy-law content alignment.
Verified 2026-11-04. Selected contribution, not full attainment.