Terms of Service

By creating an account, signing in, or otherwise using the software (the “Software”), you agree to these Terms of Service on behalf of yourself and the organization that operates the deployment (the “Customer”, “you”). If you do not agree, do not use the Software. If you are accepting on behalf of an organization, you confirm you are authorized to do so.

ChronoFlow is licensed for self-hosted and private deployments. The agreement under which your organization obtained the deployment — an order form, licence terms, or a separate written agreement (the “Applicable Agreement”) — governs the licence grant, fees, term, support, and liability.

These terms are supplementary and do not replace the Applicable Agreement. If these terms conflict with it, the Applicable Agreement controls.

• Accounts are for named individuals and must not be shared. You are responsible for keeping your credentials confidential and for everything done under your account.
• Where your organization requires it, enable two-factor authentication or a registered security key. Tell your workspace administrator promptly if you believe an account or a key is compromised.
• Access is capped by the licence of the deployment. The evaluation tier allows 10 users and 50 workflows; Pro allows 100 users and 500 workflows; Enterprise has no user or workflow cap in its licence. Administrators can see the current tier and usage in Billing.
• You are responsible for the accuracy of the account details your administrators record, and for removing access when someone leaves the organization.

You agree not to, and not to permit anyone else to:

• use the Software for anything unlawful, or to process data you are not authorized to process;
• attempt to bypass access controls, tenant isolation, licence checks, rate limits, or audit logging;
• probe, scan, or test the security of a deployment you do not operate without written permission from its operator;
• upload malware, or use the Software to interfere with other systems or networks;
• resell, sublicense, or white-label the Software except as the Applicable Agreement allows;
• use the Software in a way that would require it to make a decision that must by law be made by a person.

Workflow definitions, form submissions, task and approval decisions, uploaded files, and audit records are stored in the Customer’s own deployment and database. Operating the deployment does not send that content to a central ChronoFlow store. Your organization decides who can read it, where it is hosted, and how long it is kept.

Features that you explicitly connect to an external service — for example an AI provider, a mail server, a webhook destination, or a single sign-on identity provider — send data to that service when you use them. Those integrations are configured and controlled by the Customer, under that service’s own terms.

You are responsible for having a lawful basis to process the data you put into the deployment, and for the notices your own users receive. See the Privacy Policy for what the Software itself stores.

The Software is provided under the warranty terms, if any, in the Applicable Agreement. Except for those terms, and to the maximum extent permitted by law, the Software is provided “as is” and “as available”, without warranties of any kind, express or implied, including merchantability, fitness for a particular purpose, and non-infringement.

No statement on our website, in our documentation, or in a sales conversation creates a warranty beyond the Applicable Agreement.

• Because the Software runs in your environment, availability depends on your infrastructure and on how the deployment is configured, patched and backed up.
• We may change, improve, or deprecate features over time. Material changes are described in the release notes for your deployment.
• The Free tier is an evaluation tier for pilots. Its capacity and features may change, and it is not a performance or availability commitment.
• Licence limits are enforced by the product. They are capacity limits, not guarantees of throughput.

Your organization may stop using the Software at any time. Access may be suspended if the licence expires or is invalid, if these terms or the Applicable Agreement are breached, or where the law requires it.

The deployment and its data remain in the Customer’s control. Deleting the deployment, and deciding what happens to the data inside it, is the Customer’s responsibility.

Except as the Applicable Agreement provides, and to the maximum extent permitted by law, we are not liable for indirect, incidental, special, or consequential damages, or for lost profits, revenue, data, or goodwill, arising out of or related to the Software.

Nothing in these terms limits liability that cannot be limited by law.

We may update these terms. The “last updated” date at the top of this page changes when we do. Material changes are announced in the product or to the Customer’s administrators. Continuing to use the Software after an update means you accept the revised terms.

Questions about these terms, or about the agreement that covers your deployment? Contact the ChronoFlow team. Your own administrator or account team is the fastest route for deployment-specific questions.

This document is a standard starting template, not legal advice, and it is deliberately generic. It does not name a governing law, a jurisdiction, or an entity address, because those depend on the Applicable Agreement for each deployment. Your counsel should add them — along with any notice, liability, or procurement terms your organization requires — before you rely on it.