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 dedicated pages do show the four core artefacts: a central VVT covering data subject categories, assets, business processes and involved systems, guided DPIAs with a growing template set including AI-system evaluation, AVV management with vendors, and documented TOMs under review. Updates are said to propagate system-wide and requests link back to the inventory, which reaches toward a connected model. I found no public information on legal bases recorded per activity, DPIA need derived from the record, or multi-client use for external data protection officers, and I count the 'everything in one place' prose as claims rather than architecture. 14 10 9