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 is a real module — Article 30, guided fields, templates, versioning, exportable documentation and an authority export — and it is linked to asset and vendor data, alongside DPIAs under Article 35 with a risk matrix, centrally documented TOMs, and Article 28 processor management over a database of 4,000-plus vendors. We found no public information on legal bases modelled inside the record, DPIA need derived from it, or template reuse across client companies, which keeps this below the fully connected data-model level. 13 9 3 12 4