Privacy and compliance
Sub-processor
A sub-processor is a third party that a data processor engages to process personal data for the controller, for example a hosting or email provider.
Also called: subprocessor, sub processor, sub-processor list
Few services run everything themselves. A form backend rents servers from a hosting company, sends email through a mail provider and stores backups with a storage provider. Each of those that handles personal data on the service’s behalf is a sub-processor.
What the GDPR requires
The processor may not hire a sub-processor without the controller’s authorisation, which can be specific (each one approved) or general (a list that can change, with notice). It must bind the sub-processor to the same data protection obligations as in the data processing agreement, and it stays fully responsible to the controller for what the sub-processor does.
What a good sub-processor list shows
- The name and country of each provider.
- What each one does and which data it touches.
- Where the data is processed (see data residency).
- How and when you are told about changes, and what you can do if you object.
Providers you choose are not sub-processors
If you connect your own Google Sheet, Slack workspace or SMTP server, the provider receives data because you chose to send it there. That provider works for you, and you need your own agreement with it. The service you used to connect it is not hiring it.
In StaticForm
Annex II of the StaticForm data processing agreement lists the sub-processors, their purpose, location and the data they handle. StaticForm gives general authorisation, and notifies customers by email at least 30 days before adding or replacing a sub-processor, during which a customer can object on reasonable data protection grounds. Integrations a customer enables itself, such as Google Sheets, Notion, Slack, Discord, webhooks, its own SMTP server, its own CAPTCHA keys or its own Stripe account, are destinations the customer chose and not sub-processors.
Learn more
Related terms
- Data processing agreementA data processing agreement (DPA) is the contract the GDPR requires between a data controller and a processor that handles personal data on the controller's behalf.
- Data residencyData residency is the country or region where data is physically stored. For website forms it decides which legal rules apply to the submissions you collect.
- Form backendA form backend is a service that receives what a website form submits, then validates it, stores it, filters spam and sends it on to email, a spreadsheet or another tool.