EU hosting and European AI processing: what to ask.

Where the application runs is one part of the answer. Follow the information through the model, integrations and operational services too.

AI-generated editorial brand image

Start with a clear scope

Ask which service and data categories a statement covers. Application records, model inputs, account details and backups may follow different paths. A country mentioned on a homepage is most useful when it is tied to a named service, a provider and a current contractual commitment. Optional integrations should be described separately from the standard configuration.

Distinguish hosting from inference

Hosting is where the application and its stored data run. Inference is where the model processes a request. Feleo’s own platform runs on Hetzner in Germany, while its text AI uses Mistral’s EU endpoint. Mistral’s regional documentation describes EU/EFTA locations and separately handled operational metadata. A regional endpoint therefore does not establish the location of every kind of data.

Mistral: Regional inference ↗

Ask separately about training and retention

Training opt-out and Zero Data Retention are different controls. ZDR concerns supported request and response content at the model provider; it does not delete the conversation history your application needs. In Feleo’s current stateless text setup, API training is disabled and ZDR is enabled. Check the scope again for audio, files or any new feature instead of extending a text-processing assurance by assumption.

Mistral: Zero data retention ↗

Look at the full provider chain

A provider’s headquarters, processing locations and subcontractors answer different questions. Ask who can access which data, from where, and under what terms. A signed processing agreement is an important document, but it should be read together with the actual setup and its annexes. The current Feleo trust page explains the confirmed scope and the points still being clarified.

Hetzner: Data protection ↗

Keep this checklist

  • Name the service and data categories
  • Check storage, processing and access separately
  • Separate training rules from retention
  • Keep dated documents for the actual configuration

Prepared by the Feleo team. Examples are planning guidance, not customer results. Confirm the scope of your own pilot before launch.

What could we take
off your plate?