How Simpriva Works | DPIA and RoPA Workflow
How Simpriva works

Built for how DPIAs and RoPA actually work

Simpriva is being designed around a connected privacy journey: starting with an Initial Privacy Check, identifying the appropriate route and reusing approved information across the work that follows.

Take part in the discovery

A clearer route through privacy governance

1

Initial Privacy Check

A user begins with clear questions about the proposed activity, the information involved and the surrounding context.

2

Appropriate route

Based on the information provided, the activity can be guided towards the most suitable next step.

3

Guided information gathering

The user is asked for information relevant to the route they are following, avoiding unnecessary questions wherever possible.

4

Risk and safeguard support

Relevant risks, controls, safeguards and review points can be brought into the assessment for consideration.

5

Connected records

Approved information can be reused across related DPIA, RoPA and privacy governance records.

6

Human review and approval

The appropriate privacy professional or decision-maker reviews the information, challenges it where necessary and retains responsibility for the final decision.

Routes being designed
Update existing record
Light privacy review
Privacy by Design check
Refresh existing DPIA
Full DPIA required
Core design principles

The principles behind Simpriva

Input once

Information should not have to be repeatedly recreated when it is already available and appropriate to reuse.

Follow the golden thread

The route from the original question through risks, safeguards, decisions and final outputs should remain clear.

Reflect the real context

Privacy questions and risks should reflect the activity, organisation and sector rather than relying entirely on generic forms.

Keep people accountable

Guidance and technology should support human decisions rather than obscure or replace responsibility.

More than another DPIA form

Simpriva is not being designed as a standalone questionnaire or a document generator. The intention is to connect the privacy journey so that the original activity, answers, risks, actions, decisions and related records can be understood together.

Connected rather than fragmented

DPIA, RoPA and related privacy information should be able to work together.

Guided rather than generic

Users should receive questions and support relevant to the journey they are following.

Controlled rather than automatic

Suggestions and routes should be explainable, reviewable and subject to human approval.

Does this reflect the challenges your organisation experiences?

We are testing these assumptions with privacy practitioners and organisations before finalising the product.

Share your experience