Sub-processors
Last updated: 29 July 2026
Foundry IX ApS (“Foundry IX”, “we”, “us”) engages the third-party sub-processors listed below to deliver Alloy. Each sub-processor may process personal data only to provide its service to us, under a written agreement imposing data-protection obligations consistent with our Privacy Policy and, where applicable, your organisation’s Data Processing Agreement.
Current sub-processors
| Sub-processor | Purpose | Processing location | Transfer safeguard |
|---|---|---|---|
| Microsoft Corporation | Identity (Microsoft Entra ID) and cloud hosting of the Alloy platform (Microsoft Azure) | European Union | Processing within Microsoft’s European data centres |
| Google LLC | Sign-in and OAuth identity provider | EEA / United States | EU Standard Contractual Clauses |
| xAI | AI model inference for assistant responses | United States | EU Standard Contractual Clauses |
| OpenAI | AI model inference for assistant responses | United States | EU Standard Contractual Clauses |
| Anthropic | AI model inference for assistant responses | United States | EU Standard Contractual Clauses |
| Mistral AI | AI model inference for assistant responses | European Union | Processing within the EEA |
| ElevenLabs | Voice synthesis and transcription for voice features | United States | EU Standard Contractual Clauses |
| GitHub, Inc. | Source-code hosting and distribution of published skills and plugins | United States | EU Standard Contractual Clauses |
Content sent to AI model and voice providers is processed through their APIs solely to produce responses and is not used to train their models.
Connected systems and AI clients are not sub-processors
Systems your organisation connects through Data Connections (e.g. SQL Server, Business Central, Azure AI Search, Resend, e-conomic, Harvest, Dinero, Uniconta, Azure DevOps, Meta Ads, Google Ads) are services your organisation has its own relationship with. Your organisation controls those systems and the credentials used to access them; they are not sub-processors of Foundry IX. This includes data your organisation instructs Alloy to send outbound to such a system — for example ad copy, targeting parameters, budgets and video or image creative written to a Meta ad account your organisation owns, or campaigns, ad groups, keywords and ad text written to its Google Ads account.
The same applies when your organisation instructs Alloy to move content between two systems it connects — for example uploading a video from your organisation’s Google Drive to its Meta ad account. Alloy transfers it on your organisation’s instruction, using the credentials of the member who asks; both systems remain your organisation’s own.
The same applies in the outbound direction: external AI clients your organisation authorises to access Alloy’s MCP endpoint (for example, a third-party assistant your organisation connects to Alloy) act on your organisation’s behalf, under your organisation’s agreement with that provider. Data those clients request is transferred to them at your organisation’s instruction; they are not sub-processors of Foundry IX.
Changes to this list
We may add or replace sub-processors as the service evolves. When we do, we update this page and the “Last updated” date above. Any notification or objection rights your organisation has regarding new sub-processors are set out in its Data Processing Agreement.
Contact
Questions about our sub-processors can be sent to info@foundryix.com.