Deployment and data handling, discussed openly.
Built in Switzerland. Swiss-hosted and on-premise options. Privacy, residency and human-control requirements are part of each solution definition.
Deployment options
- Swiss hosting for agreed managed deployments.
- On-premise options for organizations that require them.
- Your own cloud subscription (Azure, AWS or other), installed by you or your integrator.
- Residency and operating requirements documented before activation.
Human control
- Workflows start supervised; checkpoints can be removed as runs prove them.
- Approval points and responsibilities are defined for the use case.
- Realistic scenarios are tested before activation.
Data protection
- Support for GDPR and Swiss nDSG requirements.
- A data-processing agreement is prepared with each engagement before signature.
- Data scope and retention agreed for each deployment.
Technical evaluation
- Review of the systems and access rights involved.
- Clarification of the data needed for the use case.
- Documented operational and responsibility boundaries.
Security and privacy from the start
Swiss hosting & on-prem options
GDPR + nDSG support
A data-processing agreement is prepared with each engagement before signature
Human approval points
Organization-specific access control
Agreed data requirements
Transparency summary v2
Security and compliance claims you can verify.
Each claim states its scope and maturity. Detailed control mechanisms and sensitive evidence are reviewed privately during a guided technical evaluation.
Version v2 · Last reviewed 10.11.2026
| ID | Claim | Status | How to verify |
|---|---|---|---|
| C01 | Every workflow run keeps an event history, with redacted run views for authorised integrators. | In place | Ask for a workflow run and its redacted event history using your integrators’ role. |
| C02 | Controlled test runs can produce verifiable evidence; scope and maturity are confirmed for each engagement. | In preparation | Ask for a controlled test run and the available verification result. |
| C03 | Workflows can require a designated human approver before publication or an outbound action. | In place | Ask for a test that pauses before the selected effect and resumes after approval. |
| C04 | Controlled integrations enforce agreed access and operating boundaries. | In place | Ask for a permitted operation and a refused operation within the agreed test scope. |
| C05 | Organization and member checks are enforced before workflow processing. | In place | Ask for a two-organisation cross-access test. |
| C06 | Deployment, residency and data-handling requirements are documented before activation. | In place | Ask for the deployment-specific summary and responsibility matrix. |
In place means supported in the stated scope, not universally deployed. Detailed controls, evidence and remediation information are reviewed privately.