Software inspection
The technical inspection layer.
Finding the decisions is one job. Establishing what the software actually does is another, and it needs people who can read the code, the configuration and the data model.
What this covers
- Source code, where you have it and we have access.
- Configuration and rules inside vendor platforms.
- Workflow automation - the rules living in tools like Power Automate and Zapier that nobody thinks of as software.
- Spreadsheets carrying scoring or ranking formulas.
- Legacy business rules written years ago that nobody has reviewed since.
Why it matters for this obligation
A privacy policy has to describe what a system does. If nobody has read the rule since it was written, the description is a guess.
In older systems, it is common for decisions to sit in code that no current staff member knows are being made.
Quoted as an add-on to any tier, after a scoping call.
Find out what you are dealing with
Six questions, about a minute. An indicative tier and price on screen.