Sub-processors
Who processes data when you use Nodest, where they are, and how changes are announced.
A sub-processor is a company Nodest uses to operate the platform that may process personal data in doing so. There are three, and the list is public.
| Sub-processor | Purpose | Data processed | Location | Safeguard |
|---|---|---|---|---|
| Hetzner Online GmbH | Cloud hosting and infrastructure | All customer and automation data stored on the platform | Germany (EU) | Art. 28 GDPR DPA |
| Brevo (Sendinblue SAS) | CRM, transactional email and newsletter | Name, email address | France (EU) | Art. 28 GDPR DPA |
| Stripe, Inc. | Payment processing | Billing contact details, payment transaction data | USA | Standard Contractual Clauses (EU 2021/914) |
The sub-processors page is the authoritative version, kept current with a visible last-updated date.
Your connected tools are not sub-processors
When your automation sends data to external tools or any other service you've configured, that service isn't a Nodest sub-processor. You chose it, you instructed the transfer, and the data processing relationship is between you and them.
How changes are announced
Planned changes are posted on the sub-processors page at least 10 days before they take effect. Emergency changes — where waiting isn't possible — are posted within 5 days of happening.
There's no email notification, so if sub-processor changes need reviewing on your side, check the page periodically or have someone watch it.
Objecting to a change
You can object to a new or replacement sub-processor within 10 days of the page being updated. Write to privacy@nodest.com stating the specific data protection grounds for the objection.
If we can't reasonably accommodate it, either party may terminate the agreement. It's a real right, not a formality — but it needs specific grounds, not a general preference.
