Skip to main content
Good Security

Service

Catch privacy risk before the project launches

Work out whether a project creates privacy risk before launch, with clear decisions, mitigations, and evidence you can stand behind.

Example deliverable
What you send when privacy gets challenged preview

What this gives the business

What you send when privacy gets challenged

A fictional privacy impact assessment covering project context, information flows, IPP analysis, and treatment actions.

The pressure

A new project or change to data handling is moving ahead and privacy risk is being discovered too late

You get a structured privacy impact assessment that surfaces the material risks, required controls, and decisions before the change hardens.

When a new project changes how personal information is collected, used, or shared, the risk is not just legal. It can slow delivery, create customer trust issues, and force rework after launch. A privacy impact assessment helps you surface those issues early enough to do something useful about them.

Good Security reviews the proposal, tests it against privacy obligations and real operating risk, and leaves you with a written assessment, practical mitigations, and a decision record the project team can work from.

Deliverables

The artefacts that land on your desk

A detailed PIA report, specific risk treatment recommendations per identified risk, privacy-by-design guidance, and a mapping to the relevant Information Privacy Principles

Privacy Impact Assessment Report

Detailed assessment documenting the project scope, personal information flows, identified privacy risks, impact ratings, and recommended controls.

Risk Treatment Recommendations

Specific, practical recommendations for each identified risk, including control options, implementation guidance, and residual risk assessment.

Privacy-by-Design Guidance

Proactive recommendations for embedding privacy controls into the project design rather than retrofitting them after implementation.

Compliance Mapping

Mapping of project activities to relevant Information Privacy Principles, identifying applicable obligations and demonstrating compliance approach.

What that looks like in practice

The PIA output sets out the project context, the personal information involved, the risk areas, the required mitigations, and the decisions leadership or the project team must make before proceeding.

Outcomes

What stops being a scramble

Project privacy risk shows up before go-live, mitigations land while they can still shape delivery, and you've a defensible decision record

  • Project privacy risk is visible before go-live instead of being discovered after complaints or change requests.
  • Mitigations are agreed with enough time to influence delivery, not just document concern.
  • You have a written record of the privacy decisions you made and why.
  • Teams know what must change before the project can safely move forward.

Process

From kick-off to handover, step by step

Four steps from defining project and data context, through impact assessment and mitigation agreement, to a pre-launch walkthrough of what must change

1

Define the project and data context

We confirm what is changing, which personal information is involved, and where the highest sensitivity sits.

2

Assess the privacy impact

Good Security reviews the design against privacy obligations, practical risk, and customer trust considerations.

3

Agree the mitigations

The assessment turns into concrete changes, decisions, and owners rather than a generic warning list.

4

Deliver the PIA record

You receive the written assessment and a walkthrough of what must happen before launch or approval.

Not sure if this is the right next step for the business?

Book a call and we'll talk through whether this is the right next step, what you'd walk away with, and how it sits alongside anything the business already has in place.

Questions buyers ask before committing

When is this the right fit?

A new project or change to data handling is moving ahead and privacy risk is being discovered too late Use this when a new data use, system, or process needs privacy review before go-live or procurement sign-off.

What changes once the work is delivered?

You get a structured privacy impact assessment that surfaces the material risks, required controls, and decisions before the change hardens.