Terms of Service

Effective date: {{EFFECTIVE_DATE}} Last updated: {{EFFECTIVE_DATE}}

1. The agreement

These Terms are a binding contract between you and {{COMPANY_LEGAL_NAME}}, registered under {{COMPANY_ID}}, with its registered office at {{COMPANY_ADDRESS}} ("Cronspace", "we", "us"), governing your use of the Cronspace service at {{WEBSITE_URL}} (the "Service").

By creating an account or using the Service, you accept these Terms. If you are accepting on behalf of a company, you confirm you have authority to bind it, and "you" means that company.

Our Privacy Policy is part of this agreement.

2. The Service is in private beta

Read this section carefully, because it shapes everything below.

Cronspace is a private beta. That means:

It may contain defects, and features may change, break or disappear without notice.
There is no uptime commitment and no service level agreement.
Data loss is possible. Keep your own copies of anything you cannot afford to lose.
We may change, suspend or discontinue any part of the Service, or the whole thing, at any time. If we shut down the Service entirely, we will give you at least 30 days' notice and a way to export your data, unless circumstances outside our control make that impossible.

Do not use the beta for work where failure would cause serious harm.

3. Eligibility, invite codes and accounts

You must be at least 16 years old and legally able to enter a contract.

Access is by invitation. Invite codes are personal, may have a limited number of uses, and may expire. Do not sell or publicly post one. We may revoke a code, or an account created with one, if it was obtained or shared improperly.

You are responsible for your account: keep your password and any API keys confidential, and tell us at {{SECURITY_EMAIL}} as soon as you suspect unauthorized access. Anything done through your account or your API keys is treated as done by you.

4. Workspaces, roles and privacy inside a workspace

Work in Cronspace lives in a workspace, and every workspace has three roles: owner, admin and member. If you invite others into yours, or join someone else's, understand what that means.

Your conversations are private; their effects are not. Your chats are visible only to you — not to other members, not to admins, not to the owner. But a chat in Cronspace carries the same tools as an agent run: it can query and write to a connected database, spend money on models, produce artifacts and dispatch tasks. Those effects are recorded in the workspace's shared, auditable history with your name on them, and every member can see them. Privacy covers what you said. It never covers what you did.

The owner can export the workspace, and the export includes your conversations. It is a deliberate act, and it is logged to a record every member can read before the export is built — but it exists, and joining a workspace means accepting it. If you would not want an owner to read something, do not put it in their workspace.

Roles carry real power. Admins can configure agents, change approval policies, connect external services, issue API keys and approve agent actions. Only the owner can change roles, control spending, transfer ownership and export. The owner controls membership and is responsible for who is in the workspace.

Leaving is announced, and reversible for 30 days. When you leave a workspace or are removed from one: the scheduled and running tasks you started are paused rather than left firing unowned; your personal connections to external services and your API keys are revoked; and your conversations become inaccessible to everyone, including to you if you rejoin later. For 30 days another member can readopt your paused tasks, and the removal can be undone. After 30 days a scheduled purge deletes your conversations and archives the tasks nobody readopted. That deletion is permanent.

If your workspace belongs to an organization, that organization may control your account and your content, and may access or remove them.

5. Your content

You keep ownership. Everything you put into Cronspace and everything your agents produce for you — instructions, files, transcripts, artifacts — remains yours.

You grant us a worldwide, non-exclusive, royalty-free licence to host, store, transmit, display and process that content only to the extent needed to operate the Service for you, including sending the relevant parts to the model provider you selected. This licence exists so we can run the product; it gives us no other rights, and it ends when you delete the content or close your account.

We do not use your content to train AI models.

Attachments and artifacts are served from unguessable public URLs. Files you upload and artifacts your agents produce live at long, randomly suffixed addresses that are neither listed nor indexed, but that do not require a login: anyone holding the exact URL can open it. Workspace exports are the exception and are served privately. Treat an artifact link as a secret, and do not put anything in one that would harm you if the link were forwarded.

You are responsible for what you put in. You confirm you have the rights to it and that processing it through Cronspace does not break the law or anyone else's rights.

Skills. A skill is a folder of instructions and files that teaches an agent a specific way of working, and that can include scripts the agent runs in its sandbox. Skills you upload, import from a public GitHub repository, or have an agent write for you are your content, and you are responsible for them: you confirm you have the right to use them, that their licence allows it, and that their content complies with section 6. We check every skill automatically when it is added, and that check is a safeguard and not a guarantee — only add skills you trust, because a skill can tell an agent what to do. A skill never raises what an agent is allowed to do: the workspace's approval rules apply to everything a skill makes an agent do, exactly as they do to anything else. We may block or remove a skill that breaks these Terms or that we find unsafe. A skill published to a workspace is visible to every member of it, and stays with the workspace when the person who published it leaves; your personal skills are visible only to you.

6. Acceptable use

Do not use Cronspace to:

Break the law, or infringe anyone's intellectual property, privacy or other rights.
Generate or distribute malware, run attacks, scan or probe systems you do not control, or attempt to breach any security measure — ours or a third party's.
Access data or workspaces you are not authorized to access.
Send spam, run mass unsolicited outreach, or impersonate anyone.
Generate material that sexually exploits minors, incites violence, or harasses people.
Automate access to a third-party service in violation of that service's terms, or to scrape it in a way it prohibits.
Circumvent rate limits, spending limits, approval policies or usage quotas — including by opening multiple accounts.
Resell the Service, or use it to build a competing product.
Overload or interfere with the infrastructure, or with anyone else's use of it.

You are responsible for what your agents do under your configuration. Instructing an agent to do something on this list is doing it yourself.

7. Agents, autonomous actions and your responsibility

This is the section that matters most, so it is the plainest one.

Cronspace runs agents that act on their own. They call tools, run code, browse the web, query your connected services, create files, and execute on schedules you set — including while you are asleep or away.

A conversation is an execution surface, not a scratchpad. A chat turn is given the same toolset as a scheduled run. Asking a question in the chat can result in a query against your data, a write to a connected database, or a call to a third-party service — under the same approval policy, and with the same consequences.

Code runs in an isolated environment we provision for the run, and the isolation is a safety measure, not a guarantee. Do not treat it as a place to run anything whose escape would harm you.

You configure the leash, and you own the consequences. For each agent you decide the approval policy, which tools it can use, which services it can reach, and what its spending limit is. A permissive configuration is your choice, and you are responsible for what an agent does within it. When Cronspace asks you to approve an action, approving it is your decision and your responsibility — including when you approve without reading.

Outputs can be wrong. AI models produce inaccurate, incomplete and fabricated information, confidently. Verify anything before you rely on it. Cronspace output is not legal, financial, medical, tax or other professional advice, and must not be used as a substitute for a qualified professional.

Some actions cannot be undone. An agent may send data to a third party, modify a connected system, or produce an effect that cannot be reversed. Approval policies reduce this risk; they do not eliminate it. Configure them accordingly, and do not connect a production system you are not prepared to see an agent touch.

We do not monitor or endorse what your agents do. We are not a party to whatever your agents produce or the decisions you make from it.

8. Third-party services

Cronspace connects to services you authorize: Shopify, Meta, Google (Analytics and Search Console), databases you provide, and any MCP server you configure.

Those services are governed by their own terms and privacy policies, and you must comply with them. Your agreement with them is yours, not ours.
You confirm you are authorized to connect each account and to let agents access its data.
We are not responsible for a third-party service being unavailable, changing its API, returning wrong data, or terminating your access.
A connector may stop working at any time. When one fails, agents are designed to continue rather than halt, which means a run may complete with incomplete information.

Databases you connect

Connecting a Postgres or MySQL database hands agents direct access to your own data, so the terms are stricter — the blast radius is larger:

You supply the credentials, and their scope is your decision. Give the narrowest credential that does the job. Do not connect a production database you are not prepared to see modified.
Reads run freely; writes do not. Agents may run read-only queries within the limits the product enforces. Writes are structured, capped per run, restricted per table and per verb by the permissions you set, and destructive operations require both your approval and your consent to the specific shape of the operation.
Approving a write is authorizing it. Those limits and approvals reduce risk. They do not make a mistake impossible, and they are not a substitute for your own backups. Back up before you connect.
You confirm you are entitled to grant this access. Where the database holds other people's personal data you remain responsible for it, including for having a lawful basis to have it processed here.

9. Fees

During the private beta, Cronspace is provided free of charge. No fees are payable and none of this is a commitment to keep it free.

We will give you at least 30 days' notice before introducing charges, and you will be able to stop using the Service rather than pay. Spending limits inside the product control your agents' model usage; they are an operational safeguard, not a billing arrangement.

10. Fair use and limits

We apply rate limits and usage quotas to keep the Service running for everyone, and we may adjust them. If your usage is disproportionate or is degrading the Service for others, we may throttle or suspend it — we will try to contact you first, unless the situation requires immediate action.

11. Suspension and termination

You can stop at any time by deleting your account. Deletion removes your content on the schedule in the Privacy Policy. Leaving a single workspace is a different thing, and section 4 describes what happens then.

We may suspend or terminate your access if you breach these Terms, if your use creates legal risk or harm for us or another user, if required by law, or if we discontinue the Service. We will give reasonable notice unless the breach or risk calls for acting immediately.

On termination: your right to use the Service ends, running tasks stop, and your content is deleted as described in the Privacy Policy. Sections 5 (ownership), 7, 12, 13, 14, 15 and 17 survive.

12. Intellectual property

The Service — software, interface, design, documentation and the Cronspace name and marks — belongs to us and our licensors. These Terms grant you a limited, non-exclusive, non-transferable right to use the Service, and nothing more. Do not copy, modify, reverse engineer or create derivative works from it, except where the law says you may despite this clause.

If you send us feedback or suggestions, we may use them freely, without obligation to you.

13. Disclaimers

The Service is provided "as is" and "as available", without warranty of any kind. To the maximum extent the law allows, we disclaim all warranties, express or implied, including merchantability, fitness for a particular purpose, non-infringement, and any warranty arising from course of dealing or usage.

Specifically, we do not warrant that the Service will be uninterrupted, secure or error-free; that defects will be corrected; that data will not be lost; or that AI-generated output will be accurate, complete, current or fit for any purpose.

Some jurisdictions do not allow certain exclusions, so parts of this section may not apply to you.

14. Limitation of liability

To the maximum extent the law allows:

We are not liable for indirect, incidental, special, consequential or punitive damages, or for lost profits, revenue, data, business or goodwill, however caused and under any theory of liability, even if we were told such damages were possible.
We are not liable for actions taken by AI agents you configured, for decisions you made based on agent output, or for effects on third-party systems your agents reached with your authorization.
Our total aggregate liability for all claims relating to the Service is limited to the greater of (a) the amount you paid us in the 12 months before the claim arose, or (b) one hundred euros (€100). During the free beta, that means €100.

Nothing here excludes liability that cannot legally be excluded — including death or personal injury caused by negligence, fraud, or fraudulent misrepresentation. If you are a consumer, your statutory rights are unaffected.

15. Indemnification

You will defend, indemnify and hold us harmless against claims, damages, losses and reasonable legal costs arising from your use of the Service, your content, actions taken by agents you configured, your breach of these Terms, or your violation of any law or third-party right.

16. Changes to these Terms

We may update these Terms. Material changes will be announced by email or in the product at least 14 days before they take effect. Continuing to use the Service after that means you accept the new version. If you do not accept it, stop using the Service and delete your account.

17. Governing law and disputes

These Terms are governed by {{GOVERNING_LAW}}, without regard to conflict-of-laws rules. Disputes will be subject to the exclusive jurisdiction of {{COURTS}}.

If you are a consumer resident in the European Union, this does not deprive you of the protection of the mandatory laws of your country of residence, and you may bring proceedings in your local courts.

18. General

Entire agreement. These Terms and the Privacy Policy are the whole agreement between us about the Service, replacing anything said earlier.
Severability. If a provision is unenforceable, the rest stays in force and the provision is applied as closely as possible to its intent.
No waiver. Not enforcing a right once does not waive it.
Assignment. You may not assign these Terms without our written consent. We may assign them to an affiliate or in connection with a merger, acquisition or sale of assets.
Force majeure. Neither party is liable for failure caused by events beyond its reasonable control.
Language. These Terms are written in English. A translation is for convenience; the English version governs.