Security & procurement
What is subprocessor?
A third party that a vendor uses to process customer personal data, such as a cloud host, email provider or AI service.
Also called: sub-processor, subprocessor list
A subprocessor is any outside company a software vendor engages to process personal data on its customers' behalf. For an event platform, that might include cloud hosting, email delivery, SMS, payment processing, analytics, support tools, video streaming and AI model providers.
Under GDPR, processors need the customer's authorization to use subprocessors and must pass on equivalent data protection obligations. Vendors typically publish a subprocessor list and notify customers before adding new ones.
When reviewing, check where each subprocessor is located, what data it receives, how you'll be notified of changes and whether you can object. AI features often add new subprocessors, so ask about them specifically.
Why it matters for event marketers: Your attendee data travels to every subprocessor, so the list is part of the risk you're accepting.
How it works
Under GDPR Article 28, a vendor acting as a processor can only engage another processor with the customer's prior specific or general written authorization. Most SaaS vendors use general authorization: the data processing agreement (DPA) approves the current published list of subprocessors, and the vendor commits to notify customers before adding or replacing one, giving them a chance to object.
The vendor must also flow down equivalent data protection obligations by contract and remains liable for each subprocessor's performance. A typical event platform's list includes a cloud host, email and SMS delivery, payment processors, video streaming, customer support tools, analytics and, increasingly, AI model providers.
What to look for in software
Find the vendor's public subprocessor list and check each entry's purpose, the data it receives and its location. Data transferred outside the EEA or UK needs a transfer mechanism, such as standard contractual clauses or the EU-US Data Privacy Framework.
Check how you'll be notified of changes (email subscription, RSS or in-app), the notice period and your right to object. For AI features, ask which model providers receive attendee data, whether it's used for training and whether AI features can be switched off per account.
Examples
Cvent publishes a list of affiliates and subprocessors with locations and transfer mechanisms. Bizzabo's sub-processor list shows processing countries and update notices, Sessionize has a public subprocessor page, and Livestorm lists subprocessors in its trust center.
The European Data Protection Board's guidelines on controllers and processors explain the authorization and flow-down requirements in detail.