← Back to course
AI and You 9-12 / Week 07 / Thursday
4/6
Week 07 · Privacy in the Machine

Thursday

Fewer details, still useful?
// What a question log reveals
⏱ about 20 min

Thursday: Fewer Details, Still Useful?

Comet spreads six sticky notes across the table. Each one names a privacy fix for the log.

"No names. Changing IDs. Totals only. Delete after 14 days. No training on questions. Tell students everything," she reads. "Let's add them all!"

Teacher Dev looks worried. "If I only see totals, how do I know which student is stuck on slope?"

Wren nods slowly. "Every fix protects something. What does each one give up?"

Comet pulls the pencil from behind her ear. "So it is a trade, not a free win."

Nova projects a table with three columns. "Would you like a hint?" she asks. "For each fix, write what it protects and what it gives up."

Wren hands you the first sticky note. "Our reviewer gets the last word on each one."

Two kinds of privacy fix

NIST names two ways to keep fewer details: de-identification and aggregation.

De-identification takes out or replaces the details that say who a record is about, such as names.

Aggregation combines records into totals. NIST says these methods can support privacy-enhanced AI systems.

But NIST also warns that, in some cases, privacy methods can lower accuracy.

NAME THE METHOD
  • Read the question.
  • Tap your answer.
Replace every name in the log with an ID.
Keep only the number of questions on each topic.
Give every student a new ID each week.

The crew's six fixes

These are the crew's own proposals in the story, with their trade-offs.

FixWhat it protectsWhat it gives up
No names in the logAnonymity: a row does not say who askedTeachers cannot see which student needs help
IDs that change each weekA pattern cannot be followed for weeksNobody can see if one student is stuck for a month
Keep topic totals, not timesLate-night habits stay privateThe builder cannot see when students study
Delete the raw log after 14 daysOld rows cannot leak laterNo long history to look back on
Never train SH-1 on student questionsQuestions cannot be memorized and repeatedSH-1 does not learn from how students ask
Tell students exactly what is keptControl: students know and can choose what to askSome students may ask fewer questions
WEIGH THE TRADE-OFF
  • Read the question.
  • Tap your answer.
Teacher Dev cannot tell which student is stuck on slope. Which fix caused that?
Which fix stops SH-1 from repeating another student's question?
Which fix would have hidden S07's late-night pattern?
StatementTrue or false?
De-identification and aggregation can support privacy.?
Privacy methods never change how accurate or useful data is.?
Every privacy fix gives up something.?
Removing names alone always stops anyone from working out who asked.?
WHY THIS EXERCISEPrivacy design means choosing which trade-offs are worth it.
FOLLOW ONE QUESTION UNDER THE CREW'S FIXES
  • Tap a card.
  • Then tap its spot.
1First
2Next
3Then
4Last
Combining records into totals is called ____.
Taking out or replacing names is called de-____.

Thoughtful trade-offs, reviewer. Tomorrow is Impact Friday, and the panel has a hard question for you.

← Wednesday