Auditing the data an existing system collects
A list of every item of data a system collects, both typed in by the user and gathered passively (permissions, cookies, location), with the reason for collecting each item.
Understanding Auditing the data an existing system collects in Years 9–10 Data & Information
What it does: The entry splits the audit into data entered by the user and data gathered in the background. Each audit row pairs one data item with its purpose, which is the core of a data audit. Every permission is a possible source of data. An audit lists them all, and a missing reason is a warning sign. Cookies and trackers can quietly record what users do, so they belong in the audit as passive data.
Common mistakes: GPS location is not typed in by the user. The app gets it passively through a permission, so the source should be 'permission'. A data audit must record a reason for every item. The cookie row has no reason, so it needs one, such as 'save login'.
Free printable worksheet with full answer key — or add this module to a class and your students practise it interactively.
This module's key terms are also in a printable crossword (Modules 83–132) and word search (Modules 6–132).
Take this worksheet further — free with Cloodit
Each concept is reinforced from every angle — learned, then applied, then tested.
Cloodit turns curriculum-aligned coding content into journeys students work through one biome at a time.
Over 100 of them, across seven natural biomes.
Turns their work into revision material ready for Flash Cards and Exam study.
Live, competitive practice for the start of the lesson or a teacher-led lesson finisher.
Honour your top performers, or encourage a student who's trying hard — ready to print in seconds.
Quick Questions
Match the Pairs
Key Term
data auditFill in the Blanks
Spot the Error
Student with a class code? Join your class →