Subprocessor notice example for SaaS teams
This worked example shows how a small SaaS team can turn one vendor change into a clean customer notice with dates, a deadline, and a proof trail.
Your DPA, privacy policy, customer contracts, and counsel should decide the actual notice language and timing. This page is meant to make the workflow concrete.
The example change
Imagine a SaaS team is adding Acme Email Cloud as a transactional email subprocessor. The vendor will process customer names, email addresses, and message metadata for EU customers on a signed DPA. The team wants a simple notice they can send before the change goes live.
Filled-out notice
Subject: Upcoming subprocessor update
Hello {{customer_name}},
We are updating our subprocessor list to add Acme Email Cloud for transactional email delivery. This vendor may process customer names, email addresses, and message metadata for EU customers on a signed DPA. Processing may occur in the United States and the EU.
Notice date: April 23, 2026
Planned effective date: May 30, 2026
Objection deadline: May 23, 2026
If your agreement includes a right to object, please send any objection by the deadline above so we can review it before the change takes effect. The current subprocessor page is available at {{subprocessor_page_url}}.
Regards,
{{sender_name}}
Why this example works
It names the change
The notice says which vendor is being added and what service it supports, instead of hiding behind a vague "vendor update" label.
It sets a deadline
Customers can see the notice date, the effective date, and the objection deadline in one place, which makes the timeline easier to review.
It scopes the impact
The example calls out the affected customer segment and data categories so the message is not broader than the change itself.
It preserves proof
The team can save the final text, the send timestamp, the updated public page, and any objections in one evidence folder.
What to customize before sending
- Replace the vendor name, service description, and public URL.
- Use the exact customer segment defined in your DPA or contract set.
- Adjust the effective date and deadline to match the notice period that controls the change.
- Add the internal owner, reviewer, and escalation path if objections need a response.
- Save the final draft in the same folder as the page proof and recipient list.
Fast send checklist
Check the DPA or customer contract for the notice window and any special recipient rules.
Do not send one blanket notice if only one customer group is affected by the vendor change.
Make sure the notice date, objection deadline, and effective date are consistent before the email goes out.
Keep the sent copy, customer list, updated public page, and objection responses in one evidence trail.
Want the generator instead of the example?
Run the readiness self-audit to see whether your workflow is ready, then use the homepage generator to draft the next notice.