> For the complete documentation index, see [llms.txt](https://docs.ilert.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ilert.com/trust-center/legal/subprocessors.md).

# Sub-processor List

*Version 1.1 · Last updated: 25 September 2026*

This is the canonical list of sub-processors engaged by ilert for the delivery of its SaaS services.

Customers receive 30 days' prior written notice of any new or replacement sub-processor, with the right to object.

## Current Sub-processors

| Sub-processor                       | Address                                                                 | Service                             | Data Location                             | Transfer Mechanism            |
| ----------------------------------- | ----------------------------------------------------------------------- | ----------------------------------- | ----------------------------------------- | ----------------------------- |
| **Amazon Web Services EMEA SARL**   | 38 avenue John F. Kennedy, L-1855 Luxembourg                            | Cloud Hosting                       | Frankfurt, Stockholm, Dublin              | Privacy Framework, SCCs       |
| **Bird B.V.** (MessageBird)         | Keizersgracht 268, 1016 EV Amsterdam, Netherlands                       | Telecommunication                   | Netherlands                               | N/A (EU-based)                |
| **Vonage B.V.**                     | Prins Bernhardplein 200, 1097 JB Amsterdam, Netherlands                 | Telecommunication                   | Netherlands                               | N/A (EU-based)                |
| **Twilio Inc.**                     | 101 Spear Street, 1st Floor, San Francisco, CA 94105, USA               | Telecommunication                   | United States (optional for EU customers) | SCCs, BCRs, Privacy Framework |
| **Stripe Payments Europe, Limited** | 1 Grand Canal Street Lower, Grand Canal Dock, Dublin, D02 H210, Ireland | Billing and Payments                | Ireland                                   | Privacy Framework, SCCs       |
| **HubSpot Germany GmbH**            | Am Postbahnhof 17, 10243 Berlin, Germany                                | Customer Service                    | Germany                                   | Privacy Framework, SCCs       |
| **PostHog Inc.**                    | 2261 Market St., #4008, San Francisco, CA 94114, USA                    | Product Analytics, Customer Service | Frankfurt (EU Cloud)                      | Privacy Framework, SCCs       |
| **X.AI LLC**                        | 1450 Page Mill Rd., Palo Alto, CA 94304, USA                            | AI Features, AI Voice Agent         | EU (eu-west-1)                            | SCCs                          |
| **Fly.io, Inc.**                    | 2045 W Grand Ave, Ste B, Chicago, IL 60612, USA                         | Sandbox Environment for AI Products | Frankfurt                                 | Privacy Framework, SCCs       |

SCCs = Standard Contractual Clauses. BCRs = Binding Corporate Rules.

Amazon Web Services EMEA SARL and HubSpot Germany GmbH are EU companies. The transfer mechanisms listed for them cover their onward transfers to Amazon Web Services, Inc. and HubSpot, Inc. in the United States.

X.AI LLC and Fly.io, Inc. process data only for accounts that have enabled AI features. Accounts with AI features disabled are not processed by either provider.

## Changes

ilert notifies customers in writing at least 30 days before adding or replacing a sub-processor. Customers may object on reasonable grounds within that period.

For questions about sub-processors, contact <privacy@ilert.com>.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ilert.com/trust-center/legal/subprocessors.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.