Data sovereignty
You decide where your data lives and who can read it.
Collabase is developed in Zurich and operated in Switzerland. You choose how it runs: the Isolated Cloud in a Swiss data centre or your own infrastructure. Content only leaves your environment when you switch that on.
Three commitments
Three commitments, by which sovereignty can be measured.
Where your content is stored, who can see it and when it leaves your environment.
Your data stays in Switzerland
Your content is subject to Swiss law. In managed operation it sits encrypted on servers in a Swiss data centre, in self-hosted operation you choose the location yourself. In the standard setup it stays out of reach of the US Cloud Act. Connect an external AI provider and its terms apply to the content you send there.
AI only once you switch it on
Collabase AI is optional and enabled per space. You connect the provider of your choice with your own key, whether OpenAI, Anthropic, Gemini or Infomaniak in Switzerland. Without activation every piece of content stays in your environment.
Encrypted, including with us
In managed operation your content sits encrypted on Swiss servers. Collabase cannot technically read it.
Occasion
When the question of data location comes up.
Sovereignty is rarely an end in itself. Usually someone outside the project raises it: an audit, a customer or a new requirement.
- A requirement says that personal data must stay in Switzerland.
- An audit asks who has technical access to your content.
- You want to use AI without handing content to a provider you did not choose yourself.
Evidence
Evidence for the compliance review
Information security is certified to ISO 27001 and processing meets the nFADP and the GDPR. The documents are ready before you ask for them.
Evidence, certificates and hosting location in one place.
Test Collabase with your own content.
In the proof of concept you work with your own content. That way you answer your audit's questions on the real system before you decide on a licence.