DPDP Rules 2025 notified — enforceable 13 May 2027.|Time left: –d –h –m –s
What it covers

Every processing activity gets checked — not just the obvious ones

The assessment starts from the asset, works through every processing activity tied to it, and confirms applicability before any deep-dive risk work begins.

Asset / application intake

The assessment starts from the specific asset or application, scoped and introduced before any processing activity within it gets touched.

Processing activity inventory

Every processing activity tied to that asset, listed in full, not just the ones assumed upfront to be risky.

Data Processor involvement check

For each activity, whether a third-party processor is involved, and to what extent.

Documentation adequacy check

Whether existing documentation for each activity is actually sufficient, or has real gaps once someone looks closely.

Applicability confirmation

Every processing activity is tested against DPIA triggers, including validating any activity already flagged as "DPIA not needed" rather than accepting that call at face value.

Deep-dive risk work, where confirmed

Necessity & proportionality, risk-to-rights, and mitigation design — run only on the activities confirmed to actually need it.

What you get

A finding for every activity, not one verdict for the whole asset

Every finding traces back to a specific processing activity — nothing is bundled into a single pass/fail for the entire asset.

  • A completed DPIA intake per asset, covering every processing activity, its processor involvement, and its existing documentation
  • An applicability finding for every processing activity — confirmed in scope, confirmed out of scope, or flagged for more input — not one blanket verdict
  • Full DPIA findings — necessity/proportionality, risk-to-rights scoring — for every activity confirmed in scope
  • A mitigation plan mapped to specific design or process changes, each with an owner
  • A reusable intake template calibrated to your own systems, for assessments your team runs in-house afterward
Process

Five stages, click any to see more

Data flow mapping and risk mapping run as two distinct steps — a scored risk register depends on the flow map being done first.

01

Template & scoping

Share the DPIA intake template for your team to complete and return.

Covers asset, every processing activity tied to it, processor involvement, and existing documentation — one template, filled once, per asset.

02

Applicability confirmation

Confirm which submitted activities genuinely warrant a full DPIA.

Any activity already marked exempt by your team is tested here too, rather than accepted at face value.

03

Data flow mapping

Map how data actually moves for every activity confirmed in scope.

Systems, storage points, and transfers — the concrete map that risk scoring depends on.

04

Risk mapping & scoring

Identify and score the risk to Data Principals for each in-scope activity.

Scored as risk to the individual, not organisational or reputational risk — kept as its own step from flow mapping.

05

Mitigation & recommendations

Deliver mitigation recommendations mapped to each identified risk.

Each recommendation gets an owner, so the finding doesn't stall as an unassigned line item.

Have an asset that needs a real DPIA?

Start with the intake template — 30 minutes to scope it, no obligation.

Book a Consultation