Subprocessor change notice template for SaaS teams
Use this operational template when your SaaS company adds, replaces, or materially changes a vendor and needs to notify customers before the change takes effect.
This guide helps organize facts for customer communication and attorney review. It does not decide whether a notice is legally required or whether a specific notice satisfies your agreements.
When to use this notice
A subprocessor change notice is usually relevant when a B2B SaaS team adds a vendor that may process customer personal data, changes the purpose of an existing vendor, changes a processing region, or replaces one vendor with another.
Before sending anything, check the DPA or customer agreement for the required notice period, delivery method, objection process, and any customer-specific recipient rules.
Facts to collect first
- Vendor legal name and public website.
- Service purpose, written in plain customer-facing language.
- Data categories that may be processed.
- Processing region or transfer context.
- Notice date and planned effective date.
- Objection deadline based on the relevant customer agreement.
- Internal owner, reviewer, and evidence folder location.
Customer notice template
Subject: Upcoming subprocessor update
Hello {{customer_name}},
We are updating our subprocessor list to add {{vendor_name}} for {{service_purpose}}. This vendor may process {{data_categories}} for {{affected_customer_segment}}. Processing may occur in {{processing_region}}.
Notice date: {{notice_date}}
Planned effective date: {{effective_date}}
Objection deadline: {{objection_deadline}}
If your agreement includes a right to object, please send any objection through {{objection_method}} by the deadline above so we can review it before the change takes effect.
We have updated our subprocessor page here: {{subprocessor_page_url}}.
Regards,
{{sender_name}}
Short version
Subject: Subprocessor list update
We plan to add {{vendor_name}} as a subprocessor for {{service_purpose}} on {{effective_date}}. The vendor may process {{data_categories}} in {{processing_region}}. If your agreement includes objection rights, please send any objection by {{objection_deadline}} through {{objection_method}}. The updated subprocessor page is available at {{subprocessor_page_url}}.
Evidence to keep
The notice itself is only part of the workflow. Keep a simple evidence record so your team can answer procurement, counsel, or customer success questions later.
- Final notice copy that was sent.
- Recipient list or customer segment definition.
- Timestamp, channel, and sender.
- Screenshot or archived copy of the updated subprocessor page.
- Objections received, owner assigned, and resolution status.
- Internal approval notes from privacy, security, legal, or leadership reviewers.
Common mistakes
Sending the notice without a deadline
A customer cannot easily act if the notice does not say when the change becomes effective or when objections close.
Listing only the vendor name
Customers usually need to know what the vendor does, what data may be involved, and whether the change affects them.
Losing proof after sending
Email copy, page proof, and reviewer notes should live in one evidence folder before the objection window closes.
Using one notice for every customer
Enterprise customers can have different notice periods, recipients, and escalation paths. Segment before sending.
Want the working files?
NoticeKit Starter includes the notice variants, objection-window tracker, subprocessor list template, and evidence log for one vendor change.