EU hosting statement
Where data lives and where models run. Stated as the target environment that is confirmed contractually and technically with each customer during the pilot.
Environment
| Component | Location |
|---|---|
| Application, worker, database | Hetzner, Falkenstein, Germany (EU) |
| Backups | Same region; encrypted; 35-day purge after deletion |
| Language model | EU-resident option: self-hosted open-weights model (e.g. Llama 3.1 70B via vLLM) on the same infrastructure, so no CRM or accounting data leaves the EU. Where a frontier API is used, only public source text and approved facts are sent, under a DPA and with EU data-residency where the provider offers it. |
| Customer CRM | Stays in the customer's HubSpot account and region |
Transfers
No routine transfer outside the EU/EEA. Any exception is listed per sub-processor with its legal mechanism (adequacy decision or SCCs) on the Security page.
Moldova
Customers and users in Moldova access an EU-hosted service; company-level data collected from Moldovan public sources is processed in the EU under Legea 195/2024 rules for cross-border transfer, which we document in the DPA.
Verification
Region, sub-processors, retention and transfers are confirmed in writing in the pilot agreement and can be verified by the customer's security team before go-live.
Items highlighted like this are filled in per customer or before launch. We describe controls we operate; we do not present GDPR compliance, AI Act conformity or ISO certification as achieved results until verified.