Skip to content

Risk and data flows

See the risks, and where the personal data goes

Both are built from what the workspace already knows: the intake answers, the findings, the vendor register and the connector checks.

Risk register

Every gap becomes a risk with a score, an owner and a due date, so the riskiest work is done first.

  • Scored by likelihood × impact, each from 1 to 5: 20 and above is critical.
  • Starting scores come from the finding's status and the obligation's severity.
  • Treatments: mitigate, accept (with a written reason), transfer or avoid.
  • A heat map of open risks; your edits survive a re-assessment.
  • Failed connector checks become risks too.

Data-flow map

From the people the data is about, through your systems and vendors, to where it ends up.

  • Built from the intake and the vendor register, with AWS regions from the connector.
  • Every flow that leaves India is flagged, for the Section 16 transfer check.
  • Each gap is pinned to the step of the flow it affects.
  • Systems the intake missed can be added by hand.
  • Export the action plan as CSV.