Terms of service
Last updated: June 21, 2026
These Terms of Service govern your access to and use of AI Colleagues websites, Orcheo, Orcheo Beta, related APIs, and any services we provide for workflow engineering, automation, and human-AI collaboration. By using our services, you agree to these terms.
1. Using our services
- You must use our websites, applications, APIs, and services lawfully.
- You must not attempt to disrupt, abuse, or reverse engineer our systems.
- You are responsible for the information, data, files, workflows, credentials, and configurations you submit or connect.
- You must only connect third-party accounts, data sources, and integrations that you are authorised to use.
- You must not use the services to process unlawful, harmful, infringing, or unauthorised content.
2. Orcheo Beta notice
Orcheo may be made available through beta or preview environments, including beta.orcheo.cloud (the "Beta Service"). The Beta Service is a pre-general-availability environment intended for evaluation, testing, feedback, and early workflow development.
In short: treat the Beta Service as experimental. Data and workflows you create may be reset, deleted, become incompatible with the generally available release, or not be migrated. Do not use the Beta Service as your only storage location for critical production data unless separately agreed with AI Colleagues in writing. The binding terms that govern beta data and migration are set out in Section 3 below.
3. Beta data and migration
This section sets out the binding terms governing data created or stored in the Beta Service. Customer data, workflow configurations, credentials, logs, execution history, uploaded files, workspace settings, and other content created or stored in the Beta Service may be deleted, reset, become incompatible with generally available schemas, or not be migrated to the generally available version of the service. You may need to recreate workflows, reconnect integrations, regenerate credentials, or re-upload files when Orcheo reaches general availability.
We may offer migration or export tools at our discretion, but we do not guarantee automatic migration unless agreed separately in writing. For approved design partners, AI Colleagues will make commercially reasonable efforts to support migration of agreed production-relevant data to the generally available release.
4. Beta data categories
The following table explains the migration expectations for common Orcheo Beta data categories. These expectations may change as the product evolves.
| Data type | Migration expectation |
|---|---|
| Workflow definitions | May change or require migration. |
| Node configurations | May not be compatible with generally available schemas. |
| Execution history | Usually not migrated. |
| Logs and traces | Usually not migrated and may be deleted. |
| Uploaded files | May not be migrated unless agreed separately. |
| API keys and credentials | May need to be regenerated or reconnected. |
| Workspace settings | May be reset. |
| User accounts | May be preserved, but are not guaranteed unless stated separately. |
| Billing data | Handled separately from beta workspace data. |
5. Export and reset notices
Automatic migration to the generally available release is not guaranteed. Before a planned beta reset, deletion, or migration window, we will make commercially reasonable efforts to provide advance notice and, where practical, export or migration options for supported data such as workflow definitions and configuration metadata.
Our intended communication process is to notify affected users before a planned reset or deletion, provide export or migration instructions where available, and confirm after the reset, deletion, or migration has occurred.
6. Different beta commitments
Different beta users may receive different migration or continuity commitments. General beta users are not guaranteed automatic migration. Design partners with agreed use cases may receive separate migration guidance. Paying beta customers are governed by these terms and any separate written agreement that applies to their use.
7. Customer data and integrations
You retain ownership of the data, files, workflows, and configurations you provide to the services. You grant AI Colleagues the limited rights needed to operate, secure, troubleshoot, maintain, and support the services on your behalf. We do not use your customer data, workflows, files, or credentials to train AI or machine-learning models without your explicit consent. How we handle personal data is described in our Privacy Policy.
If you connect third-party services such as email, messaging, documents, storage, or collaboration tools, you are responsible for ensuring that the connection is lawful and authorised. Connected accounts and credentials added during beta may not transfer to the generally available environment and may need to be reconnected later.
8. Intellectual property
AI Colleagues owns its websites, product interfaces, documentation, software, branding, and materials unless stated otherwise. These terms do not transfer any ownership rights in AI Colleagues intellectual property or in your customer data.
9. Service changes and availability
We may change, suspend, discontinue, or limit access to any feature, beta environment, API, or service at any time. Where a change materially affects paying beta customers or design partners, we will make commercially reasonable efforts to provide advance notice.
10. Disclaimer
Services and website content are provided on an "as-is" and "as-available" basis unless a separate written agreement says otherwise. We do not guarantee that the services will be uninterrupted, error-free, secure, or compatible with every workflow, integration, data source, or production use case. Beta services are experimental and may contain defects, incomplete functionality, compatibility changes, or data continuity limitations.
11. Limitation of liability
To the maximum extent permitted by law, AI Colleagues is not liable for indirect or consequential losses, lost profits, business interruption, loss of goodwill, or loss of data arising from use of our websites, beta environments, APIs, or services.
12. Indemnification
You agree to indemnify and hold AI Colleagues harmless from claims, damages, and expenses arising from your unlawful use of the services, your breach of these terms, or your use of third-party accounts, data sources, or integrations that you were not authorised to connect.
13. Termination
You may stop using the services at any time. We may suspend or terminate your access to any service or beta environment if you breach these terms, if required by law, or if we discontinue the service. Where practical, we will make commercially reasonable efforts to provide advance notice before terminating access to a service you actively use.
On termination or cancellation, your right to use the affected services ends and your customer data may be deleted in accordance with Sections 3 to 5 and our Privacy Policy. Where practical, we will make export options available for a reasonable period before deletion.
14. Governing law and dispute resolution
These terms are governed by the laws of the Netherlands, without regard to its conflict of law rules. Any dispute arising out of or relating to these terms or your use of the services will be subject to the exclusive jurisdiction of the competent courts of the Netherlands, unless a separate written agreement says otherwise or mandatory law provides otherwise.
15. Changes to these terms
We may update these terms by publishing an updated version on this page. If changes materially affect your use of Orcheo or Orcheo Beta, we will take reasonable steps to notify affected users.
16. Contact
Questions about these terms can be sent to [email protected].