DPO Radio

Consent Gap Analysis

Overview Image

Why Consent Gap Analysis Matters

Consent is where several regimes overlap without agreeing. GDPR expects a lawful basis on every purpose, a withdrawal path as easy as the original consent and purpose-level granularity, and for special-category data it sets a condition that applies in addition to the lawful basis. The Vietnamese law brings its own expectations on consent for children and on cross-border transfers. SOC 2 asks a narrower question about disposal. An organisation operating across these markets has to answer all of them from one consent record set.

Tracked by hand, this becomes a spreadsheet nobody trusts. The gaps that matter are rarely the obvious ones — they are the purpose that was set up before anyone recorded its ground, or the market entered after the consent flow was designed.

The consent gap analysis walks every active consent purpose against the rules of each installed family in a single pass. It returns the gaps sorted by severity, each critical or high gap with a suggested remediation for a person to review. The privacy team then works a list of specific findings instead of re-reading several regimes against a register.

Three organisation-level facts change the result and are set on the page before the run: whether a global withdrawal mechanism is documented, whether a parental-consent flow exists for under-16 subjects, and whether a cross-border filing is on record. These are conditions the platform cannot infer from the purpose records alone, and stating them is what keeps the output specific to the organisation rather than generic.

How It Works

Only the Families You Installed

The page offers only the consent families of frameworks the organisation has installed and in operation, and selects all of them. A Vietnamese tenant that has not installed GDPR is never offered it, so it is never handed findings under a regime it does not answer to. If a selected family is not installed, the result names it as not analysed rather than reporting it clean, and No gaps is shown only for families the analysis actually ran.

State the Organisation Context

Three checkboxes carry the facts the purpose records cannot: a documented global withdrawal mechanism, a parental-consent flow for under-16 subjects, and a cross-border filing on record. Each one switches off a class of finding that would otherwise be raised organisation-wide.

Per-Purpose, Per-Attribute Evaluation

Every active consent purpose is checked against the attributes each installed family's rules cover — lawful basis recorded, withdrawal mechanism, consent separable per purpose, the sensitive-data ground review, consent for children, a cross-border transfer record, and a stated retention period. A family the organisation has not installed raises nothing.

A purpose counts as having a lawful basis when it carries one the installed frameworks declare, or a ground recorded in a person's own words together with the article it rests on.

The Sensitive-Data Ground Review

For every active purpose that handles sensitive personal data, the GDPR family raises a sensitive-data ground review. It asks a person to record the condition the installed frameworks require for that data, in addition to the lawful basis, with its article. It does not presume what that condition is, and it does not say that consent is required. The Vietnamese and SOC 2 families raise no such review.

A person can acknowledge a purpose's review with a required note. Later runs show the finding as acknowledged, not as a new open gap, until the purpose's sensitivity or its recorded ground changes. When either changes, the review reopens and names which one. Only a person can acknowledge: an API key or an AI workflow cannot. Each acknowledgement is recorded on the consent audit trail.

Deterministic Severity

Severity is assigned by the rule, not by the model — critical, high, medium or low. A missing lawful basis is critical. A sensitive-data ground review is high, because it marks a determination a person owes rather than a defect the platform has found. A missing retention period is medium. The same gap on the same record returns the same severity on every run.

Suggested Remediation Per Gap

Each critical or high gap carries a suggested remediation. Forseti drafts it from requirement excerpts read from the organisation's installed frameworks; where the assistant is unavailable, a fixed text takes its place. A missing-basis remediation never names a basis: it points the operator to the bases the installed frameworks declare, or to recording the ground in their own words with its article. The operator reads it as a starting point, not an instruction.

Resolve or Dismiss Per Gap

Each gap is worked individually — resolved once addressed, or dismissed as not applicable with a note. Both decisions are recorded against the run. A dismissal does not suppress the finding on the next run; it is kept as the organisation's interpretation, which Forseti can draw on later.

The Difference

Graphic Image

Without Consent Gap Analysis

Graphic Image

With Forseti Consent Gap Analysis

IconMulti-regime consent compliance is tracked by hand or in a spreadsheet.
IconEvery active purpose is walked against the rules of each installed family in one pass.
IconGaps surface during an audit or an inspection rather than before one.
IconFamilies the organisation has not installed are never analysed and never reported clean.
IconEvery regime is checked whether or not the organisation operates under it.
IconOrganisation-level context is stated once and applied consistently.
IconPurposes created before anyone recorded their ground are the ones that get missed.
IconSeverity is deterministic — the same gap scores the same way every time.
IconSeverity is a matter of opinion and varies by reviewer.
IconA person's acknowledgement of a sensitive-data ground review carries into later runs until the purpose or its ground changes.

Built for Auditable AI

Build For Image

The matrix itself is deterministic. Which gaps exist, and how severe each one is, is decided by explicit rules over the organisation's own consent records — not by a model's judgement. The assistant's contribution is the suggested remediation, which is the part where phrasing helps and the part where being wrong is recoverable.

Build For Image

The analysis never chooses, suggests or pre-selects a lawful basis, never decides that a basis is lawful, and never presumes that sensitive data needs consent. Those determinations stay with the organisation's people.

Build For Image

Nothing is remediated automatically. Findings are surfaced and worked by a person, with resolve, dismiss and acknowledge all recorded.

Build For Image

Every run writes the same three-event audit trail as the other Forseti workflows, so the sequence from finding to operator decision is reconstructable long after the fact.

Regulatory Framework Support

FrameworkHow Consent Gap Analysis Supports It
EU GDPRChecks that each purpose has a lawful basis recorded, a description that keeps its consent separable and a stated retention period, and that a withdrawal mechanism is documented; raises a sensitive-data ground review for each sensitive purpose.
Vietnam Personal Data Protection LawChecks that each purpose has a lawful basis recorded, and that a withdrawal mechanism, a consent flow for children and a cross-border transfer record are on file.
SOC 2Checks that each purpose carries a stated retention period.
Overview Image

Related Forseti Work

Use consent gap analysis for the recorded purposes. Continue with processing, notice and assessment reviews in the wider privacy work. See Privacy Workflows.

Background Image

See Consent Gap Analysis in Action

Ready to see your active consent purposes walked against the consent families you have installed, sorted by severity, with a suggested remediation on every critical and high gap? Request a personalised demo.

Demo Image
Ronni K. Gothard Christiansen

Ronni K. Gothard Christiansen - Technical Privacy Engineer & CEO

Technical Compliance Expert, 32+ Years Open Source Advocate, X-BoD Open Source Matters Inc.

Or contact via

ronni@aesirx.io+84 909 500 760

Next Steps

Icon Image

Start a Compliance Pilot

Run consent gap analysis against your live purpose catalogue and work the findings for 30 days. Measure how many gaps were genuinely unknown before the first run.

Icon Image

Discuss Your Compliance Needs

Talk to our team about which consent families apply to your markets and how the analysis fits alongside your consent management platform.

Frequently Asked Questions About Consent Gap Analysis

GDPR, the Vietnamese Personal Data Protection Law and SOC 2, whichever the organisation has installed. The page offers only those families, and analyses only those. China's PIPL is not one of them: the product ships no PIPL framework, and the analysis carries no PIPL rules.

Lawful basis recorded, withdrawal mechanism, consent separable per purpose, a sensitive-data ground review, consent for children, a cross-border transfer record, and retention period. Not every attribute is checked under every family; each family raises only its own rules.

No. A missing basis is reported as a gap, and the remediation points to the bases the installed frameworks declare, each with its article, or to recording the ground in your own words with the article it rests on. Choosing the basis, and judging that it is lawful, stays with your people.

No. For a sensitive purpose, the GDPR family raises a neutral review that asks a person to record the condition the installed frameworks require, beside the lawful basis, with its article. Consent may or may not be that condition, and the analysis does not presume either way.

Because three of the checks depend on facts that live outside the consent records — whether a global withdrawal mechanism is documented, whether a parental-consent flow exists for under-16 subjects, and whether a cross-border filing is on record. Without them the workflow would either raise organisation-wide findings that are already handled or stay silent about ones that are not.

No. Findings are surfaced with a suggested remediation attached; a person resolves, dismisses or acknowledges each one, and every decision is recorded.

Each run is started by a person on the page. A quarterly run, and a run after each batch of new or changed consent purposes, keeps the consent posture reviewed before each renewal cycle.