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 Drafted Generalist
The record of processing is built around Article 30 and can be filled via templates, questionnaires or an AI wizard, with asset, stakeholder and data-mapping records already on the lowest tier; DPIAs, transfer impact assessments and retention analyses run as questionnaire modules, contracts including DPAs get AI analysis on the Pro tier, and there is a role for external data protection officers managing all their clients as if they were one. I found no public information on the record itself flagging when a DPIA becomes mandatory, so I stayed just under the top band. 6 10 2 1