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 External DPO
The module set covers a consultancy practice — records of processing with a guided form and automatic risk assessment, a DPIA assistant, processors, TOMs, a document generator, plus client management with per-client dashboards; unlimited controller entities are claimed on the homepage and listed under the Enterprise plan, so the captured pages give different scopes for it. We found no public information on processors' DPAs, legal bases, or TOMs linked to processing activities as one connected data model, nor on DPIA need derived from the record, so this sits above module depth but short of the connected system of record. 1 2 3 6 11