Data ownership
Swiss data ownership: who runs Crew, where your data lives, and who can reach it
Crew is made by Netgen Switzerland AG in Zürich and hosted in Germany or Switzerland, your choice. The public instance runs on servers of Hetzner Online GmbH in Germany; for any client we can host in Switzerland instead, or on your own servers. Your data stays yours: you can read all of it through the API and the MCP server, and the public website runs without analytics or tracking.
Last updated:
Where Crew is hosted
Crew runs on servers of Hetzner Online GmbH in Germany (Nuremberg). Files are stored in Falkenstein, Germany. Backups are kept on Hetzner storage as well. So on the public instance your data stays within the European Union.
We have two server locations, Germany and Switzerland. Hosting Crew in Switzerland is possible on request and no problem; you can also run it on your own servers. The public instance crew.avidia.ai itself currently runs on Hetzner in Germany. If your data must stay in Switzerland, tell us and we host it there.
Swiss FADP and GDPR
Netgen Switzerland AG is the controller for the personal data processed through Crew and this website. Because we are a Swiss company that hosts in Germany or Switzerland, our privacy policy is written for both the Swiss Federal Act on Data Protection (revFADP) and the EU General Data Protection Regulation (GDPR).
This page describes how Crew is built and run. It is not legal advice. Whether a setup meets your own obligations is a question for your data protection officer or lawyer.
Who else processes data
We name our processors rather than gloss over them. At time of writing the privacy policy lists:
| Processor | Purpose | Location |
|---|---|---|
| Hetzner Online GmbH | Hosting and file storage | Germany (EU) |
| Resend | Sending transactional email | EU / USA |
| Anthropic PBC | AI features and agent runs, when you use them | USA |
If you connect Crew to another system, such as Jira, Slack, GitHub or Microsoft Entra, data is exchanged with that system on your instruction, and that provider's terms apply.
The US CLOUD Act, briefly
The US CLOUD Act (2018) lets US authorities require providers under US jurisdiction to hand over data in their possession, custody or control, even when the data is stored outside the US. So choosing an EU data centre of a US provider does not by itself take the data out of reach of US law.
Crew is built so that no US provider is required. Exposure to the CLOUD Act only arises through US-based sub-processors, and on the default public instance two of them are in use: a US-hosted AI model API (Anthropic) for AI features and agent runs, and a US email service (Resend) for transactional email. The content you send through them is subject to that. We do not claim the default public instance is free of US providers.
In a sovereign setup both are replaced by Swiss or own components: own AI models instead of a US model API (first setups run on Infomaniak in Switzerland with open models such as Qwen, Mistral AI or the Swiss AI Apertus model; the EU nodes are running today), and your own SMTP server instead of Resend. Hosted in Switzerland that way, the setup has 100% data sovereignty and no US CLOUD Act exposure through sub-processors. This is a description of how Crew is built and run, not legal advice; for the legal side, talk to your lawyer.
AI models and email under your control
Two services of the default public instance are US providers: the model API behind the AI features and agent runs, and the transactional email service. Neither is required. Crew can run on your own AI models, for example open models such as Qwen, Mistral AI or the Swiss AI Apertus model, and the first setups run on Infomaniak in Switzerland. The EU nodes are running today; the same can run in Switzerland.
For email, the transactional mail service (Resend) can be replaced by your own SMTP server. With both replaced and hosting in Switzerland, no US sub-processor is involved.
No trackers on the public site
There is no Google Analytics, no Matomo, Plausible, PostHog or Hotjar, and no advertising pixel. We set only strictly necessary cookies, so there is no consent banner. One exception we name openly: the interface font is loaded from Google Fonts at time of writing, so your browser contacts a Google server when a page loads. We are moving to self-hosted fonts.
Own your data
- REST API (v1, documented with OpenAPI): tasks, comments, worklogs, projects, users, notes, attachments and more.
- MCP server at /mcp: AI assistants such as Claude can read and change Crew data as the person who owns the token, never more.
- Exports where you need them, for example checklists and form submissions as CSV and billing reports as PDF.
- Account data and content are deleted on request or after termination, subject to statutory retention.
Where AI agents run
Agent runs execute in isolated Linux containers (LXD) on Crew's own servers, one environment per project, with git worktrees per run. They are not run on a third-party agent platform. On the public instance the language model calls go to Anthropic's API; with your own models they stay with your provider. With an on-premise installation, the containers run on infrastructure you control.
The Crew access token an agent works with is bound to its project, so through Crew it cannot reach other projects. Its work stops at approval gates where a person decides.
Frequently asked questions
Is Crew hosted in Switzerland?
Yes. On request we host Crew in Switzerland, and that is no problem. We have two server locations, Germany and Switzerland, and both work. The public instance crew.avidia.ai currently runs on Hetzner in Germany; for any client we can host in Switzerland instead, or on your own servers.
Is Crew GDPR and FADP compliant?
Our privacy policy is written for both the Swiss FADP and the EU GDPR, and we name our processors and where they are. Whether your use is compliant depends on your setup; this page is not legal advice.
Does the CLOUD Act apply to Crew?
Crew is built so that no US provider is required. Exposure to the CLOUD Act only arises through US-based sub-processors, such as a US-hosted AI model API or a US email service. The default public instance uses two (Anthropic for AI features, Resend for email). In the sovereign setup both are replaced by Swiss or own components: own AI models on Infomaniak in Switzerland (open models such as Qwen, Mistral AI or the Swiss AI Apertus model) and your own SMTP server. Hosted in Switzerland that way, there is no US CLOUD Act exposure through sub-processors. This is not legal advice; ask your lawyer how it applies to you.
Can we use our own AI models and our own mail server?
Yes. Instead of a US model API you can use your own models, for example Qwen, Mistral AI or the Swiss AI Apertus model; the first setups run on Infomaniak in Switzerland. Transactional email can go through your own SMTP server instead of Resend.
Can we get our data out?
Yes. Everything you can see in Crew you can read through the REST API or the MCP server, with your own permissions.
Talk to us about hosting
Want to choose where your data lives, or run Crew on your own servers? Request beta access and tell us what your data requirements are.
Request beta access