Every part of this product started as a job somebody was doing by hand.

The eight moments that changed what the software could do.

1. 2014–15Make GDPR actionable

   Teams could begin without turning every task into a legal consultation.

   During a GDPR implementation for a CAC 40 company, Angular prototypes turned legal requirements into guided assessments. Project leaders could collect the right facts, see what needed attention and move work forward without first becoming privacy specialists.

2. 2016Start again, properly

   The first platform was deleted rather than shipped.

   The team building it had not implemented proper IT security controls. The team was let go, the entire codebase was deleted, and Legiscope started again from nothing rather than sell a privacy product that could not meet its own standard.

3. 2017Run compliance in one place

   Five weeks of register work became two days. Article 28 assessments were in the product from the same release, read clause by clause at about five hours per processor.

   Legiscope began selling its rebuilt Angular-based cloud service. Fifty fully documented standard activities meant a register was assembled by selecting what an organisation actually did, instead of writing every entry from a blank page — five weeks of work became two days.

4. 2022Connect the core programme

   Records, vendor relationships and access controls became one workspace.

   The current repository opens during the move from Angular to React 17 and React 18. Processing records, audits, reusable templates, processor and subprocessor records, accounts and groups reduced duplicate work and kept access beside the records it governed.

5. 2023Explain the assessment

   Customers received an evaluation they could understand and challenge.

   The React interface moved into Next.js as Legiscope added AI-supported evaluations. Recorded justifications and validation steps helped teams identify possible gaps earlier, inspect the reasoning and decide what should be accepted. A processor DPA pasted into the assessment came back in three minutes instead of five hours.

6. 2024Bring context to the work

   Documents, tasks and controller boundaries stopped living outside the record.

   Automated processing creation and field-level audits reduced blank-form work. Document processing and assisted updates reduced re-entry, while tasks and multi-controller permissions put follow-up with the right people without losing organisational boundaries.

7. 2025Turn evidence into structured work

   The register that took two days took five minutes.

   Legiscope built the first automated register: the system drafts the processing activities and the reviewer corrects them, taking the same register from two days to five minutes. Background jobs, document ingestion, application enrichment, product-security analysis, DPA discovery and modular audits prepared the rest of the context so reviewers could focus on exceptions.

8. 2026Reach review-ready decisions

   Customers can move from evidence to accountable decisions without losing the links between them.

   Article 28 assessment stopped needing the document: name twenty processors and the system finds each DPA online and assesses them in minutes. Structured DPIAs, transfers, incidents and rights requests reuse existing programme context. Source evidence, reassessment, acceptance, dismissal and versioned decisions keep automation useful while the customer retains accountable judgment.

The chronology comes from the earlier Legiscope site and the current code history. The first product generation used Angular; React 17 and 18 appear in the 2022 repository transfer, followed by the Next.js interface in 2023.