TAOM™ Sub-processors

Who besides us sees data.

Clause 16.8 of our terms undertakes that we keep and provide this list. Here it is – no request needed, open to anyone. It names every service that processes personal data on our behalf in delivering TAOM.

Version 1.1 · in force from 14 Sep 2026. Every change receives a new version number; earlier versions are archived under What’s new in the customer account, with additions and removals.

Back to the Trust Center Data Processing Agreement (DPA)

The list

Four services, three legal areas

Provider	Purpose	Types of data	Location	Basis
OptimaNet Schweiz AG Hostfactory, Seuzach	Operating the platform, database, file storage, backups, mail delivery	All content stored in TAOM, account and access data, logs	Lucerne data centre, Switzerland	Processing under the Swiss FADP
n8n GmbH, Berlin n8n Cloud	Automation layer between the editor and the language model	Process text and context of an AI request including the result, execution logs	Microsoft Azure, Frankfurt, Germany (EU)	The provider’s data processing agreement with standard contractual clauses
OpenAI	Processing AI requests through the respective language model	Process text and context that the user puts into a request	United States by default; EU processing available at the provider, only for approved accounts	The provider’s data processing agreement; API content is not used for training by default. In the standard configuration, time-limited retention under the provider’s terms may occur. For suitable Enterprise configurations, zero data retention (ZDR) can be agreed, in so far as enabled by the provider for the endpoints and models used.
Microsoft	Appointment booking via Bookings on the contact page	Name, email address and details from the booking form	Microsoft cloud	The provider’s terms

Enterprise deviations. The list above describes the TAOM standard configuration. With Enterprise configurations this standard configuration may differ: sub-processors, models, automation services, hosting, processing region and data retention are laid down contractually there – up to running the model in your own environment.

Where zero data retention is agreed, the technical configuration applicable to it – including provider, region and the services concerned – is documented in the respective Enterprise agreement. The sub-processors actually used for that customer remain part of the documentation governing that contract.

What follows from this

The route of an AI request

1 · Editor

The process text is created in TAOM and sits on the Swiss server. Credentials stay server-side and never reach the browser.

2 · Automation

The request runs through n8n Cloud in Frankfurt. The content thereby leaves Switzerland and is processed within the EU.

3 · Language model

From there the request goes to OpenAI. From that point their terms and processing locations apply.

Without an agent run everything stays in Switzerland: modelling, importing, enriching and exporting work without a single one of these steps. Only starting an agent triggers steps 2 and 3.

Changes

When a service changes

Notice in advance

Customers with an existing Data Processing Agreement (DPA) are informed before a change – as stated in clause 16.8 of the terms.

Documents

The data processing agreement, the technical and organisational measures and the evidence from the providers named here are put together for your review.

Request documents →

This list is maintained whenever something changes in the services used. What governs is the terms and conditions, clauses 16.8 to 16.11.