Sub-processors
TrimCI processes customer CI data as a processor under our Data Processing Agreement. To provide the service we rely on the sub-processors below, engaged under the general authorisation in that agreement. We notify organization owners and admins by email at least 30 days before adding or replacing a sub-processor, with the right to object as described in the DPA.
| Sub-processor | Purpose | Location | Transfer safeguard |
|---|---|---|---|
| Hetzner | Infrastructure hosting (servers, storage) | European Union | EU/EEA processing — no third-country transfer |
| Brevo | Transactional email delivery | European Union (France) | EU/EEA processing — no third-country transfer |
What you will not find here
No external AI providers — log analysis and recommendations run on a self-hosted language model on our own infrastructure, so your CI data is never sent to OpenAI, Anthropic, or any other AI vendor. No third-party analytics or tracking vendors — web analytics runs cookie-less on our own self-hosted instance (Umami) on the same EU infrastructure, so it involves no sub-processor and its data never leaves our servers.
Payment processing (future)
When paid plans launch, checkout and payments will be handled by a Merchant of Record acting as an independent controller of payment data — not as our sub-processor. We will name it here and in the Privacy Policy before paid plans go live.
Change notifications
Changes to this list are announced by email to organization owners and admins at least 30 days in advance, and this page always carries the last-updated date. Questions: office@trimci.com.