Terms of Service

These terms cover what we offer when you use Digitorn: the desktop client, the Hub marketplace at hub.digitorn.ai, and the cloud surfaces you reach from this website. They're written to be read once. If something here is unclear, write to us at legal@digitorn.ai.

1. What Digitorn is

Digitorn is an open-source framework for building AI agents declaratively. You can run it in two places. Digitorn Cloud is what you reach at digitorn.ai: we host the agents, store their data and run the LLM calls for you, so you can use the same agents from any browser without installing anything. The local install is the desktop client running on your own machine; your agents, conversations, files and credentials stay there. By default a local install still routes its LLM and tool calls through Digitorn Gateway, so a single Digitorn account is enough to access every supported provider. You can turn the Gateway off on any agent and connect your own provider keys instead. The framework itself is licensed under the terms shipped in the source repository. Those terms govern the code, these terms govern the hosted services.

2. Your account

You sign in with Google, Microsoft or Apple. We store the email address, display name and avatar the provider returns, plus a rotating session token. You're responsible for keeping access to the OAuth account you used; we can't recover an agent or a Hub publication without it.

3. What you build

Your agents, YAML, prompts, attachments and conversations are yours. We don't claim a licence over any of it. In local mode that content never leaves your machine. In cloud mode it lives on the infrastructure we operate on your behalf and we handle it strictly as your processor. See the Privacy page for the inventory.

4. Provider access

Models, storage backends and integrations need credentials. With Digitorn Gateway turned on, your Digitorn account stands in for those credentials and we proxy the calls on your behalf, settling usage on the Digitorn invoice. With Gateway turned off, you plug your own provider keys in and the calls go straight to the provider. Either way, the provider's terms still apply to the traffic you send (pricing, rate limits, data retention). We don't alter the payloads.

5. Publishing on the Hub

When you publish an agent or an MCP server to the public Hub, you grant Digitorn a non-exclusive licence to display, mirror and index that package so others can install it. You promise the package is yours to share and that it doesn't embed credentials, malware or content that breaks the law where the Hub is reachable.

6. Acceptable use

Don't use Digitorn to build agents that violate other people's rights. That includes generating CSAM, harassment campaigns, mass-scale phishing or anything designed to evade authentication systems you're not authorised to touch. We'll suspend accounts that do, and we'll cooperate with law enforcement when required.

7. Service, as-is

The hosted services run on shared infrastructure and on top of third-party AI providers. We aim for high availability but we don't commit to a specific uptime, latency or model version. AI output is probabilistic; don't rely on it for decisions you wouldn't make on the back of an internet search. To the maximum extent allowed, we exclude implied warranties and cap our aggregate liability at the amount you paid us, if any, in the twelve months before the claim.

8. Ending the agreement

You can stop using Digitorn at any time. Deleting your account removes the account record and signs you out of every device; published Hub packages stay up unless you remove them explicitly. We can suspend or close an account that breaches these terms after written notice when reasonably possible.

9. Changes

If we update these terms in a way that affects you, we'll notify you by email or in-product before the change takes effect. Continuing to use Digitorn after that date means you accept the new version. We keep a public changelog of past versions on request.

10. Reaching us

Legal questions: legal@digitorn.ai. Product support and bug reports go through the in-app feedback channel or the public issue tracker linked from the desktop client.