Privacy Impact Assessment demo
Pre-answers each DPIA from the project's own documents and scores every risk before and after its controls 1:32
What the demo shows
Drafts and scores PIAs and DPIAs for new projects and vendors for privacy teams
A project's DPIA is shown as a likelihood-by-severity map on which each privacy risk is drawn twice, before and after its mitigations, joined by an arrow; beside it sits the processing description the agents extracted from the project's own documents, each operation linked to the risks it creates, and a conversation with the agents. A screening agent runs the threshold test; an intake agent reads the brief, diagram and vendor contract and pre-answers the questionnaire with the passage behind every answer, asking the owner only what the documents do not say; a necessity agent challenges every data field; a risk agent scores each risk and proposes controls from the company's library; a control checker re-checks every control against the contract and the vendor's security report on its own and disagrees out loud; a consultation agent drafts the works-council summary and the prior-consultation pack; a change watcher reopens the assessment when the vendor, design or scope changes. The project owner confirms, the privacy officer accepts each control and the residual risk with a reason code, and the DPO advises and decides any prior consultation.
Transcript
- Privacy Impact Assessment Drafts and scores DPIAs for new projects and vendors for privacy teams.
- Skip one on high-risk processing and a fine can reach 2% of turnover.
- Kestrel and Vane wants fatigue cameras in its trucks, a full DPIA Agents read the brief, diagram and contract and pre-answered
- 41 of 48 questions, each with its source.
- Each risk is drawn twice, before and after.
- Face login stores driver faces in the vendor cloud.
- Hi. A necessity agent asks why.
- Drivers already badge in.
- With on-device processing and 72-hour deletion, the arrow moves to medium.
- A second agent checks every control and disagrees out loud.
- Sophia Brandt accepts the residual risk with a reason code.
- Every answer cited, every decision signed, every step logged.
- Three high risks became none, and it was signed in eight days, not 34.
- Built on Botminds: agents, data, screens, and governance on one platform.
Transcribed from the film’s narration. Captions are on the player.