Terms

These terms cover your use of Cruma during early access. They’re an agreement between Cruma, Inc., a Delaware corporation (“Cruma”, “we”, “us”), and the company or organisation that uses Cruma (“you”). By creating a workspace, using Cruma or clicking to accept, you agree to them. We’ve written them plainly on purpose; please read them.

1. This agreement

• Who agrees. Cruma is for businesses. If you accept these terms for a company, you confirm you have authority to bind it. If you don’t have that authority, or don’t agree, don’t use Cruma.
• What’s included. This agreement is these terms, our Privacy policy, and any order form, signed agreement or data processing agreement (“DPA”) between us.
• If documents conflict. A signed agreement or order form wins over these terms, but only for what it expressly changes. A signed DPA wins over these terms and the Privacy policy on how we process personal data for you.

2. The service and early access

Cruma is a workspace where your team and AI crew members work on the same jobs, with a shared memory and rules you set. Crew members include our own agents and outside agents you connect (for example through the Model Context Protocol).

Cruma is in early access. It’s a pre-release service. Features will change, and some will be added or removed without notice. There may be bugs, interruptions and data loss while we build it. There’s no service level or uptime commitment during early access unless we agree one in writing. Please keep your own copies of anything important.

3. Accounts and workspaces

• Who can use it. Users must be at least 16 and use Cruma for work. Cruma isn’t for personal, family or household use.
• Admins. The people who manage your workspace (“admins”) control who joins, what each crew member may do, and which apps are connected. You’re responsible for their choices.
• Your users. You’re responsible for what everyone in your workspace does there, and for making sure they follow these terms.
• Sign-in. Keep sign-in details safe, don’t share accounts, and tell us promptly at hello@cruma.ai if you think someone has got in without permission.

4. Your content

• What counts. “Your content” is what you and your users put into Cruma (messages, files, records, instructions, and lessons you teach the crew), what the crew reads from apps you connect, and what the crew produces for you (“output”).
• It’s yours. As between you and us, you keep all rights in your content, and we assign to you any rights we have in output. We don’t claim ownership of either.
• Our permission to use it. You give us a limited, worldwide licence to host, copy, process, transmit and display your content only as needed to run Cruma for you, keep it secure, prevent abuse, and meet our legal duties. That includes sending it to the providers listed in our Privacy policy to do those things.
• No training. We don’t use your content to train AI models, and we use model providers whose terms don’t allow them to train on it.
• Your promises. You confirm you have the rights and permissions (including any notices and consents from people) needed for us to process your content as these terms describe, and that your content doesn’t break the law or anyone’s rights.
• Output isn’t unique. AI can produce the same or similar output for other people. What your crew makes for you is yours, but that doesn’t give you rights over similar output someone else gets.
• Usage data. We may collect information about how Cruma is used (for example feature use, errors, performance and spend) and use it to run, secure and improve Cruma. We only share it outside Cruma in aggregated form that doesn’t identify you, your users or your content.

5. What your crew does for you

• Your crew acts for you. Crew members, including outside agents you connect, act on your behalf and under your authority. You direct them; they have no authority of their own. Cruma provides the software they run on. We don’t act as your agent, and we aren’t a party to what your crew does for you.
• You set the rules. For each crew member you choose what happens on its own (Yes), what asks a person first (Asks first), and what never happens (No). Sending anything outside your company, spending, signing, inviting people and deleting always ask a person first. An owner can give standing approval for some of these, but spending always asks.
• Actions within your settings are yours. When a crew member acts within the permissions you or your admins set, or with a person’s approval, the action is yours. You’re responsible for it and its results as if your own staff had taken it, including messages sent, money spent, documents signed and data changed in connected apps. That includes actions a crew member takes on its own because you set it to Yes or gave standing approval.
• You supervise your crew. You’re responsible for the permissions you grant, for checking what you approve, and for keeping an eye on what your crew does. Grant the least access that gets the job done, and change or revoke it when you need to.
• What we’re not responsible for. To the fullest extent the law allows, Cruma isn’t responsible for the consequences of actions a crew member takes on your behalf within your settings or with your approval, or for what outside agents do under their own providers’ terms. This doesn’t cover a crew member acting outside your settings because Cruma failed to apply them; sections 15 and 17 deal with that. It also doesn’t exclude any liability the law doesn’t allow to be excluded.
• The record. Cruma logs which person or crew member took each step, and when. You can use this record to review work. Our record of an approval is evidence that it was given, unless you show otherwise.
• Things go wrong. Software, models and connected apps can fail, misread an instruction, or act late or twice. Cruma checks your settings on every action and we design the crew to follow them, but we can’t promise it always will. Don’t allow a crew member to act on its own where a mistake would cause harm you can’t accept.

6. AI output

• AI can be wrong. Output may be inaccurate, incomplete, out of date, biased or offensive, and it can sound confident when it’s wrong. Check it before you rely on it or share it.
• Not professional advice. Output isn’t legal, medical, financial, tax, safety or other professional advice. Don’t rely on it for those without review by a qualified person.
• Decisions about people. Don’t use Cruma to make decisions that have legal or similarly significant effects on a person (for example about hiring, credit, housing, insurance, education or access to essential services) without meaningful human review, and only where the law allows.
• Your responsibility. You decide how to use output, and you’re responsible for that use, including making sure it’s lawful and doesn’t infringe anyone’s rights.

7. Connected apps and outside agents

• Your connection, your terms. When someone in your workspace connects an app (such as email, calendar, files, chat or a CRM) or an outside agent, you confirm they’re allowed to, and you authorise Cruma to access that app or agent on their behalf, within the permissions they grant.
• Their terms apply. Your use of connected apps and outside agents is governed by your agreements with their providers, not by us. You’re responsible for following those terms.
• We don’t control them. We don’t control, and aren’t responsible for, connected apps or outside agents, their availability, their output, or what they do with data. Their providers can change or end access at any time, which can stop parts of Cruma working.
• Outside agents act for you, not us. An outside agent you connect (for example Claude Code or Codex) runs on its provider’s systems, under your agreement with that provider. We don’t control how it works or what it decides. When it acts in Cruma, it acts on your behalf like any other crew member, and section 5 applies.
• Outside agents follow your rules. While working in Cruma, outside agents go through the same permission checks as the rest of your crew, see only what they’re given, and can’t approve their own requests. What they do outside Cruma is outside our control.

8. Acceptable use

You and your users (and any agent acting for you) must not use Cruma to:

• break the law, or help anyone else to, including sanctions and export laws;
• infringe or misuse anyone’s intellectual property, privacy or other rights;
• send spam or unsolicited bulk messages, impersonate anyone, or mislead people about who (or what) they’re dealing with;
• harass, threaten, defraud or harm anyone, or create content that exploits or harms children;
• create malware, run cyberattacks, or get unauthorised access to any system or account, including through a connected app;
• probe, scan or test Cruma’s security, or get around its permissions, limits, spend controls or safety measures, including through prompt injection or jailbreaks, unless we’ve agreed in writing;
• use output to create weapons capable of mass harm, or break the usage policies of the model providers we use;
• process special-category or highly sensitive data (for example health, biometric or payment card data) unless we’ve agreed in writing that Cruma is suitable for it;
• copy, reverse engineer or resell Cruma, scrape it, overload it, or use it (or its output) to build a competing product; or
• let anyone outside your organisation use your workspace, except guests and contractors you invite for your own work.

9. Fees

Cruma is a paid service. What you pay, and how the crew’s work counts against it, is set out in your order form or plan, or as we otherwise agree in writing. We’ll tell you about any change to what you pay at least 30 days before it applies, and you can choose whether to continue. We may set reasonable usage limits.

10. Our rights in Cruma

• Your licence. While this agreement lasts, we give you and your users a non-exclusive, non-transferable right to use Cruma for your internal business purposes, under these terms.
• What we keep. We and our licensors own Cruma: the software, models we build, our own system prompts, designs, documentation and everything we develop, including improvements. That doesn’t include your content, including the instructions, skills, workflows and lessons you add. Apart from the rights in these terms, we don’t give you any rights in Cruma.
• Feedback. If you send us ideas, suggestions or feedback, we may use them for any purpose without owing you anything. We won’t identify you as their source without your permission.
• Your name. We won’t name you as a customer or user publicly without your permission.

11. Confidentiality

Each of us may receive the other’s non-public information (“confidential information”). Your content is your confidential information; anything we share about unreleased features, pricing or security is ours. The one receiving it will:

• use it only for this agreement, and protect it with at least reasonable care;
• share it only with employees, contractors, advisers and providers who need it for this agreement and are bound to keep it confidential; and
• be allowed to disclose it where the law requires, after giving the other notice if the law allows.

This doesn’t cover information that’s already public through no fault of the recipient, that the recipient already had or developed independently, or that it got lawfully from someone else.

12. Privacy and security

Our Privacy policy explains how we handle personal data. For personal data in your content, we act as your processor and follow your instructions, which are this agreement and your settings in Cruma. If you need a DPA (for example under the GDPR), write to privacy@cruma.ai and we’ll provide one. We keep reasonable technical and organisational measures to protect your content, as described in the Privacy policy.

13. Suspension

We may suspend some or all access, for you or a specific user, crew member or connection, if we reasonably believe:

• there’s a breach of section 8 (Acceptable use) or a serious breach of these terms;
• there’s a security risk to Cruma, you or anyone else, or an account has been compromised; or
• the law or a provider we depend on requires it.

Where it’s practical and lawful, we’ll tell you first and give you a chance to fix the problem. We’ll limit the suspension to what’s needed and restore access once the issue is resolved.

14. Ending the agreement, and your data

• You can stop using Cruma and close your workspace at any time.
• We can end early access, or this agreement, on at least 30 days’ notice. We can end it sooner if you seriously breach these terms and (if it can be fixed) don’t fix it within 10 days of our notice, or if the law requires.
• Your data. For 30 days after the agreement ends, you can ask us for an export of your content, and we’ll provide it. After that, we delete it as described in the Privacy policy, except what the law requires us to keep.
• What lasts. Sections that by their nature should continue after the end (including 4, 6, 10, 11, 15, 16, 17 and 20) continue.

15. Warranties and disclaimers

Each of us confirms it has authority to enter this agreement. Beyond that, and to the fullest extent the law allows, Cruma, output, connected apps and outside agents are provided “as is” and “as available”. We make no other promises, express or implied, including about merchantability, fitness for a particular purpose, title, non-infringement, accuracy, or that Cruma will be uninterrupted, secure or error-free, or that any crew member will always act as instructed.

16. Indemnity

You’ll defend us, our affiliates and our people against any third-party claim, and pay the resulting damages, fines, settlements and reasonable legal costs, to the extent the claim arises from:

• your content, including a claim that it infringes someone’s rights or that we processed it without the required notice or consent;
• actions your crew members, including outside agents you connect, take on your behalf within the permissions you set or with your users’ approval, and your use of output;
• your connected apps and outside agents; or
• a breach of section 8 (Acceptable use) by you, your users or anyone acting for you.

We’ll tell you promptly about the claim, let you control the defence and settlement (though you can’t admit fault for us or settle in a way that binds us without our consent), and give reasonable help at your cost.

17. Limits on liability

• No indirect losses. Neither side is liable for indirect, incidental, special, consequential, exemplary or punitive damages, or for lost profits, revenue, goodwill or data, or the cost of substitute services, even if told they were possible.
• A cap. Each side’s total liability arising from or relating to this agreement is limited to the greater of (a) the fees you paid us for Cruma in the 12 months before the event that caused the claim, and (b) US$100.
• Exceptions. These limits don’t apply to your obligations under section 16 (Indemnity), your breach of section 8 (Acceptable use) or section 10 (Our rights in Cruma), fees you owe, either side’s fraud, gross negligence or wilful misconduct, or any liability the law doesn’t allow to be limited.
• Why. These limits apply however the claim arises (contract, tort, or otherwise), and even if a remedy fails its essential purpose. They reflect that Cruma is pre-release.

18. Events outside our control

Neither side is liable for a delay or failure caused by something beyond its reasonable control, such as natural disasters, war, terrorism, riots, labour action, government action, epidemics, internet or power failures, cyberattacks, or outages at a hosting or model provider. This doesn’t excuse payment of fees owed.

19. Changes to these terms

We may update these terms. For changes that matter, we’ll tell you by email or in Cruma at least 30 days before they take effect. Changes needed for legal reasons, or that only cover new features, can take effect sooner. If you keep using Cruma after the date a change takes effect, the new terms apply; if you don’t agree, stop using Cruma and close your workspace. The date at the top shows the latest version.

20. General

• Governing law. This agreement is governed by the laws of the State of Delaware, without regard to its conflict-of-laws rules. The UN Convention on Contracts for the International Sale of Goods doesn’t apply.
• Where disputes go. Disputes go exclusively to the state and federal courts located in San Francisco County, California, and each side agrees to their jurisdiction. Either side may seek urgent relief (such as an injunction to protect confidential information or intellectual property) in any court with jurisdiction.
• Notices. We’ll send notices to the email address of your workspace’s admins, or show them in Cruma. Send legal notices to hello@cruma.ai, with a copy by post to 262 Chapman Rd, Ste 240, Newark, DE 19702. Notices by email count as received the next business day.
• Assignment. Neither side may transfer this agreement without the other’s written consent, except to a successor in a merger, acquisition or sale of all or most of its business or assets, with notice to the other.
• Trade laws. You confirm you aren’t in, or owned or controlled by anyone in, a country or on a list subject to US or other applicable sanctions, and you won’t give access to anyone who is.
• Relationship. We’re independent contractors. Nothing here creates a partnership, employment or agency relationship, and there are no third-party beneficiaries.
• Entire agreement. This agreement (as described in section 1) is everything we’ve agreed about Cruma, and replaces earlier discussions about it. Terms on your purchase orders or other documents don’t apply.
• Severability and waiver. If a court finds part of this agreement unenforceable, that part applies to the extent it can and the rest stays in force. Not enforcing a right now doesn’t mean giving it up.

21. Contact

Cruma, Inc., 262 Chapman Rd, Ste 240, Newark, DE 19702. Questions about these terms: hello@cruma.ai.