DPO Radio

Sub-Processor Change Impact Assessment

Overview Image

Why Sub-Processor Change Impact Matters

A vendor announces a sub-processor change. Under GDPR Article 28(2), a processor that changes its sub-processors informs the controller of the intended change and gives the controller the opportunity to object; Article 28(4) separately requires the same data protection obligations to flow down to the sub-processor. The window to notify and to object is short — typically governed by the DPA's SLA — and missing it is the kind of finding that surfaces in vendor renegotiation or customer audit.

The workflow reads the notification record and prepares a notice and proposed tasks. Confirm the notice period against the agreement and adjust the task due date before using it.

How It Works

Trigger From a Sub-Processor Change Notification

The workflow runs against the notification record. The affected vendor, the new sub-processor, the data category and the change shape feed the workflow context.

Article 28(2) Notification Template

The draft template is the notice a processor gives its controller of an intended change under Article 28(2), with the fields the product uses — sub-processor identity, processing activity, data category, transfer destination if applicable, and the objection mechanism.

Review the Follow-Up Task Date

The proposed follow-up task defaults to 30 days after the assessment runs. The reviewer checks the agreement and recorded obligations to determine the notice period and adjusts the task date as needed.

Follow-Up Task Chain

The workflow creates the follow-up task chain — internal review, customer notification, objection-tracking. Tasks carry suggested owner roles; the operator picks the human assignees.

Per-Field Accept or Reject

The vendor risk lead and the legal counsel review the draft. The accepted template commits to the notification record; rejections persist in the audit trail.

Trace the Review

Open the draft and review decision from audit lineage to see which proposals were applied.

The Difference

Graphic Image

Without Sub-Processor Change Impact Workflow

Graphic Image

With Forseti Sub-Processor Change Impact

IconArticle 28(2) notifications are drafted by hand for each sub-processor change.
IconThe draft notice cites the relevant requirement.
IconNotification deadlines are worked out by hand with risk of clock errors.
IconThe task date is visible for the reviewer to check.
IconFollow-up tasks are assembled for each notification.
IconSuggested roles help a reviewer route the tasks.
IconReviewers need to locate the draft and the decision separately.
IconThe responsible person confirms the follow-up.
IconTask ownership is tracked separately from the proposed change.
IconThe audit trail walks the notification end to end.

Built for Auditable AI

Build For Image

The notice cites GDPR Article 28(2). The reviewer checks the proposed task date against the applicable contract and recorded obligations.

Build For Image

The workflow creates tasks with suggested owner roles; the operator picks human assignees. No external integration assigns tasks autonomously.

Build For Image

The audit trail walks the notification from sub-processor change through customer outreach and objection tracking.

Regulatory Framework Support

FrameworkHow Sub-Processor Change Impact Supports It
EU GDPRDrafts the Article 28(2) customer notification for the responsible person to review.
Overview Image

Related Forseti Work

Use this workflow for an intended subprocessor change. Use the wider vendor reviews to examine risk and supporting records. See Third-Party Workflows.

Background Image

See Sub-Processor Change Impact in Action

See the proposed notice, the task due date and the evidence to review before notifying a customer.

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 sub-processor change impact against your active vendor pipeline for one quarter.

Icon Image

Discuss Your Compliance Needs

Talk to our team about how the workflow fits your DPA management cadence.

Frequently Asked Questions About Sub-Processor Change Impact

Sub-processor identity, processing activity, data category, transfer destination if applicable, and the objection mechanism. The template is written for the Article 28(2) notice-and-objection step and carries the citation; Article 28(4), which requires the same data protection obligations to flow down to the sub-processor, is a separate duty the template does not discharge.

The workflow displays a default task due date alongside the notice draft. Check the agreement and applicable recorded notice period before setting the final deadline.

No. The draft template is reviewed by the vendor risk lead and the legal counsel. Sending the notification is an operator action through the standard outreach surface.

Tasks are created in the standard task surface with suggested owner roles. The operator picks the human assignees per task.

Yes. Each run sends requests to the AI provider your organisation has configured, and your provider bills your organisation for them directly. A run is never refused because a Forseti allowance ran out, and the Usage page reports what each feature consumed.