> For the complete documentation index, see [llms.txt](https://docs.cleric.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cleric.ai/security/eu-hosting-data-processing.md).

# EU Hosting & Data Processing

EU-hosted instances run the application, database, and model inference in Europe. Operational logs, traces, error analysis, and product analytics are processed centrally in the US. EU hosting is not an EU-only data boundary.

| Data category     | Used for                                     | Location              |
| ----------------- | -------------------------------------------- | --------------------- |
| Application       | Running your dedicated instance              | EU (`europe-west1`)   |
| Database          | Storing investigation data and tenant Memory | EU (`europe-west1`)   |
| Model inference   | Real-time investigation reasoning            | EU regional endpoints |
| Operational logs  | Operating and supporting the service         | US                    |
| Traces            | Debugging and improving agent behavior       | US                    |
| Error analysis    | Detecting and fixing application errors      | US                    |
| Product analytics | Measuring product usage                      | US                    |

## What Runs in the EU

* **Application**: The dedicated instance (frontend and backend) runs on GCP in `europe-west1` (Belgium).
* **Database**: The dedicated application database, which stores investigation data and tenant [Memory](/learning/memories.md), runs in `europe-west1`.
* **Model inference**: Real-time model calls route from the instance to model provider endpoints in EU regions.

Data queried from your environment during an investigation (logs, metrics, code, documentation) is processed in the EU at runtime. Cleric does not store this raw data. It persists extracts of the evidence for citations, suggestions, and recommendations: a query over ten minutes of logs stores only the suspicious error lines. These extracts are stored in the application database in `europe-west1`. See [Data Storage and Retention](/security/security-data-privacy.md#data-storage-and-retention).

## What Is Processed in the US

Cleric operates observability and analytics from a central US control plane for all instances, including EU-hosted ones.

* **Operational logs**: Application and system logs export to Cleric's central US environment. The Cleric team uses them to operate and support the service. Log entries can include investigation context such as queries executed and error output. Retention follows [Data Storage and Retention](/security/security-data-privacy.md#data-storage-and-retention).
* **Traces**: Agent execution traces, including model inputs and outputs, are recorded in the US. Cleric engineers use them to debug and improve agent behavior. Your data is never used to train or fine-tune models. See [No Model-Training Risk](/security/security-data-privacy.md#no-model-training-risk).
* **Error analysis**: Application errors report to centralized error monitoring in the US.
* **Product analytics**: Usage analytics from the Cleric web application are processed in the US.

The one-way execution telemetry described in [Product Improvement Data Flow](/security/security-data-privacy.md#product-improvement-data-flow) is also processed in the US.

{% hint style="info" %}
If these US data flows conflict with your compliance requirements, contact <support@cleric.ai> or your dedicated Slack Connect channel.
{% endhint %}