The deal between us

Who this agreement is with

This is an agreement between you and Croft ("Croft", "we", "us"). If you are using Croft on behalf of a company or other organisation, "you" means that organisation, and you are confirming you have authority to accept these terms for it.

Our Privacy Policy is part of this agreement. It describes what we hold and what we do with it, and where the two documents touch the same subject, it is the more specific one.

Your account

You need an account to use Croft. Croft is passwordless: you sign in with a link or a short code sent to your email address, which means control of that mailbox is control of your account. Keep it secure, and tell us promptly if you think someone else has reached it.

Give us an address that works and that is yours. You are responsible for what happens under your account, including anything an agent does with an API key you issued.

Croft is not for children. You must be at least 16 to hold an account.

Workspaces and your team

Work in Croft happens inside a workspace, which belongs to an organisation. Members of an organisation and of a workspace hold one of three roles — owner, admin or member — and anyone you invite into a workspace can see what is in it: its workflows, their runs, the step-by-step record of what those runs did, and the data and files they touched.

Invite deliberately. Adding someone to a workspace is how they get access, and removing them is how it stops; there is no per-document permission underneath that.

Where a workspace belongs to a company, that company — acting through its owners and admins — controls it, including the content in it and who may reach it. If you joined a workspace someone else created, they, not you, decide what happens to it.

What the service does

You describe a recurring task. An agent writes a workflow in TypeScript that performs it. Croft compiles that workflow, stores it, and runs it — on a schedule, on a trigger, or when you ask — recording every step so you can see what happened.

Workflow code runs in a sandbox with no ambient access to the network, the filesystem, the real clock, or real randomness. Everything a workflow reaches on the outside — an email sent, a row written to a sheet, a call to a connected account, a prompt to a model — crosses back out of that sandbox into Croft, where it is checked against the grants you made and written into the run's record.

Agents reach your workspace through croft.now/mcp using an API key you create, scoped to one workspace and to the grants you attach to it. Treat that key like a password: anything holding it can do what you allowed it to do. You can revoke one at any time.

Agents and generated code

This is the part of these terms worth reading twice.

The workflows Croft runs are written by a language model, and the AI steps inside them produce output the same way. That output is not guaranteed to be correct. It may misread your intent, mishandle an edge case you did not describe, or do the right thing on the run you watched and the wrong thing on the run you did not. The same input will not always produce the same output.

A workflow acts with the access you gave it, as you. When it sends mail, it is your mail. When it writes to a connected account, it is your write. You are responsible for what your workflows do, including the ones you did not write yourself.

So: read a workflow before you turn it loose on something that matters. The product gives you the tools for that — the source is visible and editable, a test run shows you what a workflow would do before it does it, and a run you were happy with can be pinned as a test that later versions have to keep passing. Use them, particularly for anything that sends, deletes, or spends.

Do not use Croft as the only safeguard on a decision that needs a human, or in any setting where a wrong or missed run causes injury, financial loss you could not absorb, or a breach of a legal duty you owe someone else.

Accounts you connect

Croft is only useful once it can reach the tools you already use. When you connect an account, you authorise Croft to act on that account on your behalf, limited to the scopes that connection was granted. We store the resulting credential encrypted, and we use it for nothing but running your workflows.

You must have the right to connect each account, and to let your workflows do what they do with it. Your agreement with that provider still applies to you, and nothing here overrides it — if their terms forbid something, connecting them to Croft does not make it allowed.

You can disconnect at any time, which removes the stored credential. We do not control the services you connect and are not responsible for them: if one changes its API, revokes access, rate-limits you, or goes down, your workflows that depend on it will feel it.

What you may not do with it

A short list, and we mean each line of it. Do not use Croft to:

• — Break the law, infringe someone's rights, or handle content you have no right to handle.
• — Send bulk unsolicited email, or any message whose recipients did not agree to hear from you. Croft can send mail; it is for your work, not for a list you bought.
• — Scrape, harvest, or hammer a third-party service in a way that service forbids, or route traffic through Croft to disguise where it came from.
• — Attack the sandbox: escape it, reach another workspace's data, or interfere with anyone else's runs. Security research is welcome — email us first and we will talk.
• — Mine cryptocurrency, resell raw compute, or run workloads whose point is the resources rather than the work.
• — Process data that carries obligations we have not signed up to. Croft is not built for protected health information, payment card data, or anything requiring HIPAA or PCI compliance, and we are not certified for it.

We do not read your workspace content looking for violations. But if something is reported to us, or a workload is damaging the service for other people, we will look, and we may act under Suspension and ending it.

Who owns what

Yours

Everything you put into Croft, and everything your workflows produce, is yours: the workflow source — including the code an agent wrote for you — your documents, files, records, artifacts, and the run history. We claim no ownership of any of it.

You give us the permission we need to actually run the product: to store your content, to compile and execute your workflows, to display them back to you and your workspace, and to pass what a step sends to the provider that step calls. That permission exists to operate Croft for you and for nothing else. We do not sell your content, and we do not use it to train models.

Ours

Croft itself — the service, the runtime, the canvas, the SDK, the name and the look of it — stays ours. These terms give you the right to use it, not to copy it, resell it, or rebuild it from the inside.

Feedback

If you tell us what is wrong with Croft or what it should do next, we may act on it freely and without owing you anything for it. We would rather have the feedback than the ambiguity.

Money

Croft does not charge you today. There is no paid plan, no card on file, and no billing system behind this page. Croft is early, and while it is, using it costs nothing.

We do count usage per workspace — active workflows, runs, AI tokens, agent calls to /mcp, and bytes stored — because we need to know what the service costs to run and what a fair price would look like.

When we do start charging, it will be for the workspace and the team in it, not for each run or task, and we will tell account holders by email before any charge, with time to export and leave if the price is not for you. We will not turn on a bill you did not agree to.

Availability, and the fact that this is early

There is no uptime commitment and no service level agreement. We run Croft carefully and we want your scheduled workflows to fire on time, but we are not promising that they will, and you should not build something around Croft where a missed run is a serious problem for you.

We are still changing the product, including the SDK your workflows are written against. We may add features, change how existing ones behave, and remove things that are not working. Where a change would break workflows you already have, we will try to keep them running and will tell you when we cannot.

Suspension and ending it

You can stop using Croft whenever you like, and take your work with you: workflow source, documents, files and records are all exportable from the product. Nothing here is designed to keep you.

We may suspend or close an account that breaks the acceptable use rules, that puts the service or other customers at risk, or that we are legally required to act on. Except where something is urgent or unlawful, we will tell you what the problem is and give you a chance to fix it first.

Deleting a whole account or workspace is not yet self-service. Email [email protected] and we will do it. What deletion actually removes, and how long backups keep a copy, is set out in the Privacy Policy.

Disclaimers

Croft is provided as is and as available. To the fullest extent the law allows, we disclaim all warranties, express or implied, including any implied warranty of merchantability, fitness for a particular purpose, and non-infringement.

In plainer words: we do not warrant that Croft will be uninterrupted or error-free, that a workflow will run when you expect it to, that generated code or model output will be correct or fit for what you need, or that a connected service will keep behaving the way it does today. Some jurisdictions do not allow these exclusions, and where that is so, they do not apply to you.

Limits on liability

To the fullest extent the law allows, neither party is liable for indirect, incidental, special, consequential, or punitive damages, or for lost profits, lost revenue, or lost or corrupted data, arising out of your use of Croft — even if we were told such damages were possible.

Our total liability arising out of or relating to these terms is capped at the greater of the amount you paid us for Croft in the twelve months before the claim, or one hundred US dollars. While Croft is free, that means one hundred US dollars, which is the honest consequence of an early product that costs you nothing.

Nothing in these terms excludes liability that cannot lawfully be excluded — including for fraud, or for death or personal injury caused by negligence.

Indemnity

You will defend and indemnify us against third-party claims arising from your content, your use of Croft, the messages your workflows send, or your breach of these terms. We will tell you promptly about any such claim and let you control its defence, and we will not settle it without your agreement.

Changes to these terms

We will update this page when these terms change, and move the date at the top. If a change materially reduces your rights or adds an obligation, we will tell account holders by email before it takes effect rather than relying on you to notice. Continuing to use Croft after a change takes effect means you accept it; if you do not, stop using Croft and ask us to delete your account.

Governing law

These terms are governed by the laws of the State of Delaware, United States, without regard to its conflict of laws rules, and the courts located there have exclusive jurisdiction over any dispute — except that either of us may bring a claim in small claims court, and either of us may seek an injunction anywhere to protect intellectual property or confidential information.

If a provision of these terms is held unenforceable, the rest stays in force. Our not enforcing something is not a waiver of it. These terms, together with the Privacy Policy, are the whole agreement between us about Croft. You may not assign them without our consent; we may assign them to a successor if the business changes hands.