01 90-day implementation route
Discover → Decide → Design → Deploy → Demonstrate. The days are an editorial planning frame, not a legal deadline, guarantee or universal project estimate.
Trace reality
Create an owned picture of collection points, purposes, systems, exports, processors and high-impact journeys.
Make choices explicit
Resolve purposes, notice scope, choice reliance, retention events, role assessments and conditional child/SDF questions.
Build the operating path
Turn decisions into rights, correction, erasure, safeguard, vendor-exit and breach workflows with clear hand-offs.
Put the design into systems
Ship the smallest coherent configuration, content and ownership changes, then record what actually changed.
Exercise and retrieve
Run synthetic requests and an incident tabletop, retrieve the evidence pack and convert failures into owned remediation.
Use the JSON export as a planning snapshot. Keep actual evidence in the organisation's controlled systems.
This site has no upload, submission or account capability and should not be used to store personal data.
Use qualified counsel for applicability, interpretation and release review. The route cannot make those conclusions.
02 Your first fifteen days
A representative lead, customer and staff journey usually expose enough hand-offs to establish the register structure and ownership questions.