A well-maintained SaaS subprocessor list helps customers understand where their data goes, gives internal teams a reliable vendor data-flow inventory, and creates evidence for privacy and security reviews. This guide provides a reusable subprocessor register template, change-review checklist, approval workflow, and customer-notice examples for reviewing providers before onboarding, replacement, expansion, or audit preparation.
Overview
A subprocessor is generally a third party engaged by a processor to handle personal data on the processor’s behalf. In a SaaS environment, subprocessors may include cloud hosting providers, managed databases, observability platforms, customer-support tools, email delivery services, identity providers, payment services, or security vendors. The exact role depends on the service and the data flow, so the register should describe what each provider actually does rather than relying on broad labels such as “infrastructure.”
Subprocessor management is more than publishing a list on a legal page. A useful process connects four records:
- The subprocessor register: the customer-facing and internal record of approved providers.
- The data-flow inventory: the systems, data categories, locations, and transfer paths involved.
- The vendor risk assessment: the security, privacy, contractual, and operational review of each provider.
- The DPA workflow: the rules for authorization, advance notice, objections, and customer communication.
These records should agree. If a provider appears in a production architecture diagram but not in the register, or if the register says one region while the vendor operates in another, the gap can affect customer trust and data protection compliance. For broader review controls, see the Cloud Vendor Risk Assessment Playbook and the Cross-Border Data Transfer Compliance checklist.
Checklist by scenario
1. Build or refresh the subprocessor register
Start with an inventory of production and customer-facing systems. Ask engineering, infrastructure, support, sales operations, finance, and security teams which external services can access, store, transmit, or generate customer data. Include indirect providers when they are part of the processing chain, not only vendors that receive a direct API payload.
Use the following fields in a subprocessor register template:
- Legal entity name and product or service name
- Processing role and a plain-language service description
- Categories of personal data handled
- Types of data subjects affected, where relevant
- Processing purpose and connected product feature
- Hosting, support, and processing locations
- International transfer mechanism or transfer assessment reference, when applicable
- Security documentation, such as a trust page, audit report, or questionnaire
- Contract status, including DPA owner and renewal or review date
- Date added, last reviewed, and next review date
- Customer notice method and applicable notice period under the governing DPA
- Internal owner responsible for maintaining the entry
Keep customer-facing descriptions specific but restrained. “Cloud hosting and encrypted storage” is more useful than “technology services,” while a description should not expose sensitive architecture details unnecessarily.
2. Onboard a new provider
- Define the proposed data flow. Identify what data leaves your environment, when it is sent, whether it is stored, and which locations or support teams can access it.
- Classify the provider. Confirm whether it is a subprocessor, an independent controller, a service provider under another legal framework, or a tool that does not receive personal data.
- Complete due diligence. Review access controls, encryption, retention, deletion, incident response, subprocessors, regional hosting, audit evidence, and business continuity. A SaaS vendor risk assessment checklist can provide a repeatable baseline.
- Review contractual terms. Check the DPA, security addendum, confidentiality terms, breach cooperation obligations, deletion or return commitments, audit rights, and restrictions on onward processing.
- Obtain approval. Route the review to the data protection, security, legal, and system-owner functions required by your internal policy. Record exceptions rather than resolving them informally in chat.
- Update records before production use. Add the provider to the register, data-flow inventory, risk log, and relevant customer documentation before enabling customer data.
3. Review a proposed subprocessor change
When a provider changes its legal entity, service, processing location, hosting model, or onward subprocessors, compare the proposed state with the approved state. The review should answer:
- Is the provider new, or is an existing provider changing its role?
- Will the categories or volume of personal data change?
- Will data be stored or accessed from a new country or region?
- Are new support personnel, affiliates, or onward subprocessors involved?
- Does the change alter retention, deletion, model-training, logging, or telemetry practices?
- Does the customer DPA require advance notice, an objection period, or a right to terminate?
Document the decision, reviewer, evidence, effective date, and customer-notice date. If customers may object, give the privacy and account teams a consistent process for logging objections, assessing alternatives, and communicating the outcome.
4. Prepare a customer notice
Before sending a notice, verify the governing contract and DPA. Notice periods and objection rights vary by agreement, so do not assume that a standard number of days applies to every customer. A practical notice should include:
- The provider’s legal name and service description
- The expected effective date
- The relevant processing purpose and data categories
- Processing or hosting locations, where material
- A link to the current subprocessor list or security documentation
- How customers can raise a documented objection
- The deadline and required information for an objection, if specified by contract
- A privacy or support contact for questions
Example wording: “We plan to add [provider] to support [service function] on [effective date]. The provider may process [data categories] in [locations] under the applicable data processing terms. Customers may review the updated subprocessor list at [link] and submit questions or objections through [contact] by [date], subject to the notice and objection process in their agreement.”
What to double-check
Before closing a review, reconcile the register against technical and contractual evidence. These checks catch many avoidable gaps:
- Architecture versus register: compare cloud account inventories, deployment manifests, API integrations, logging tools, and production environment diagrams with the published list.
- Data category accuracy: distinguish account details, authentication data, support content, payment information, usage logs, and special-category data where relevant.
- Location accuracy: separate primary storage, backup storage, disaster recovery, support access, and subprocessors’ own onward locations.
- Retention and deletion: confirm that the provider’s documented retention matches your data retention policy and customer commitments. See the SaaS data retention policy guide.
- Access boundaries: identify whether the vendor receives a complete record, selected fields, pseudonymized data, metadata, or temporary support access.
- Evidence currency: record the date of the latest security report, questionnaire, penetration-test summary, or other evidence used in the decision.
- Customer documents: confirm that the DPA, privacy notice, security page, and subprocessor page use consistent names, dates, regions, and descriptions.
Store review evidence in a location with controlled access and a clear owner. The evidence should allow a reviewer to reconstruct what was known, approved, and communicated at the time of the decision.
Common mistakes
- Treating the list as a one-time legal document. A register becomes unreliable when engineering changes do not trigger a privacy review.
- Listing vendors without explaining the data flow. A customer needs to understand the provider’s role, not merely its brand name.
- Ignoring internal tools. Support, analytics, ticketing, monitoring, and error-reporting tools can process customer information even when they are not part of the core application.
- Copying a vendor’s region statement without validation. Verify whether it describes storage only or also support access, backups, and onward providers.
- Sending notice after the change is live. Build notice timing into procurement and release planning rather than treating it as an administrative follow-up.
- Failing to track objections. Keep a decision record for each objection, including risk analysis, mitigation, alternative provider review, and final communication.
- Overpromising in customer communications. Use precise language and avoid claiming that data never leaves a region unless the architecture and contracts support that statement.
When to revisit
Set a recurring quarterly register review, but do not rely on the calendar alone. Reopen the review when a workflow or tool changes, before seasonal planning cycles, and whenever customer data may move through a new system or location.
Use these triggers:
- A new production integration, cloud region, analytics tool, or support platform
- A vendor acquisition, legal-entity change, security incident, or material contract update
- A change to data retention, encryption, access, telemetry, or artificial-intelligence features
- A customer request for a current subprocessor list or due-diligence evidence
- A new product launch, market expansion, or cross-border data-flow change
- An annual DPA, privacy notice, security policy, or records-of-processing review
- A failed reconciliation between architecture, procurement records, and the published register
For the next review, assign one owner and schedule a short working session with engineering, security, procurement, and privacy stakeholders. Export the current register, compare it with production integrations and vendor contracts, resolve discrepancies, approve changes, and archive the evidence. Then update the customer-facing page and notice workflow before the next provider change reaches production. This turns subprocessor management into a repeatable vendor-risk control rather than a last-minute compliance exercise.