Who is affected?
When data leaks, it is useful to ask who is affected and how badly. A leaked cake recipe affects only the baker. A leaked list with names, addresses and times that children arrive at school could put many people at risk. To rank harm, think about how many people are affected, how private the details are and how hard the harm is to undo. A changed password can be fixed in a minute, but a leaked address cannot be changed so easily. People who hold data have a duty to keep it safe: the organisation, its staff, and, for their own files, every one of us. Everyone can help by sending files only to the right person, checking addresses twice and asking an adult when unsure.
| Leaked item (invented) | People affected | Easy to fix? |
|---|---|---|
| club cake recipe | 1 | yes |
| pupil addresses | 200 | no |
| canteen menu | 0 (public) | not needed |
| Role | Duty |
|---|---|
| Office | send files only to the right people |
| Teacher | lock the screen when away |
| Pupil | close and report a file they should not see |
Is this the right person?
Let me check the address again.
Rank the harm (on paper). Write six invented leaks on slips: ‘sports day times’, ‘pupil medical list’, ‘teacher’s lunch order’, ‘home addresses of the choir’, ‘new club logo’, ‘list of pupils who need help with reading’. Rank them from most to least harm. Next to each, write how many people are affected, how private it is and how hard it is to fix. Compare your ranking with a partner’s and discuss one difference. Write who has the duty to keep each safe. If you have a computer or tablet, type your ranking. These are invented.
| Item | Rank |
|---|---|
| sports day times | ? |
| pupil medical list | ? |
| club logo | ? |