Records & DPIA depth
How this is scored
The DSMS core: records of processing activities (RoPA/VVT, Art. 30 DSGVO), data protection impact assessments (DSFA, Art. 35), processor and DPA management (AVV), and technical and organisational measures (TOMs) — how deeply the legal artefacts are modelled and connected.
0 — Not a privacy management tool; at most a set of document templates with no structured records.
3 — A structured record of processing activities with templates, and a DPIA questionnaire or checklist.
5 — Records of processing and DPIAs as modules with templates, processors and their DPAs recorded, and TOMs documented and assigned to processing activities.
8 — A connected data model — processing activities linked to systems, processors, TOMs and legal bases — with DPIA need derived from the record, reusable templates across companies, and outputs (Art. 30 register, DPIA report) ready for a supervisory authority.
10 — Privacy records as a system of record: the RoPA drives DPIAs, processor management and TOM coverage from one data model, multi-client capability for external data protection officers, and the documentation is audit-ready without manual assembly.
The Skeptic
The record of processing activities demonstrably drives the rest: DPIA need is derived automatically and tied to risky processing activities, vendor management links into the record, the deletion concept is generated from it, and records synchronise with DPIAs, TOMs and vendors. Records are captured per company with a configurable one- or multi-stage approval, processor records under Art. 30(2) are supported with over 200 legally reviewed templates, and everything from the processor agreements to the register goes to the authority at a button press. I found no public information on a multi-client mode for external data protection officers, which is the one gap here. 8 7 9