Terms

Last updated 28 August 2026. Also referred to as the Terms of Service or Terms of Use; they are one document.

The short version

Crited compiles a specification into an application and deploys it into accounts you own. The code it produces is yours, with no licence back to us and nothing to unwind if you leave. We do not host what you build. What follows is the long form of that, plus the parts about payment and liability that any agreement needs.

Who you are agreeing with

These terms are between you and Menuo Inc., a Delaware C corporation, operating from Chicago, Illinois, United States. Crited is our product. Reach us at info@crited.com.

You must be at least 16 to hold an account. If you accept these terms for a company, you are confirming you may bind it, and “you” means that company.

What you own

The code Crited generates for you is yours. We claim no ownership of it, take no licence to it, and impose no restriction on what you build with it or how you make money from it. It is committed to your GitHub repository under your account.

The same applies to your specifications, your architecture, your content and your data. Code you write by hand inside a generated project stays yours and is never overwritten by a rebuild.

We own Crited itself: the compiler, the interface, the documentation and the brand. Nothing here transfers any of that to you.

Your own accounts, your own bills

Crited deploys into your Vercel and your Supabase. Those are your accounts and your relationships, governed by those companies’ own terms and billed by them directly. We are not a party to them and cannot act on your behalf beyond the tokens you connect.

If an application you build carries an assistant, it runs on a model provider key you supply, inside your own deployment. That usage is billed to you by that provider. We do not resell model access and never charge you for it.

A domain bought through Crited is bought with your Vercel token, into your Vercel account, in your name. The charge is between you and Vercel. We are not a registrar or a reseller, and domain registrations are not refundable. Nothing purchases anything without you confirming the exact amount first.

What we ask of you

  • Keep your credentials to yourself, and tell us promptly if an account is compromised.
  • Do not use Crited to build anything unlawful, or anything designed to harm people, deceive them, or breach their privacy.
  • Do not attempt to break, overload, reverse engineer or circumvent the limits of the service, or resell access to it.
  • You are responsible for what you build and for what it does to the people who use it, including complying with the laws that apply to it.
  • Do not upload content you have no right to upload, or use connected accounts you are not authorised to use.

Plans, payment and limits

Paid plans are billed in advance for the period you choose and renew until you cancel. Cancelling stops the next renewal; it does not refund the period already running. Prices can change, and we will tell you before a change affects a renewal you have not yet paid for.

Each plan carries limits on projects, deployments, members and model spend. Those limits are enforced by the product rather than merely stated here: past your budget the agents keep working on a cheaper model rather than stopping, and there is a generous hard ceiling above that. Reaching a limit does not delete anything you have already made.

Free accounts are provided as they are. We may change or end the free plan with reasonable notice.

Ending the agreement

You can stop using Crited and delete your account at any time, and you keep everything you have built: the repositories, the databases and the deployments are already in your accounts and are unaffected.

We may suspend or close an account that breaches these terms, that puts the service or other people at risk, or that goes unpaid. Except where a breach is serious or ongoing, we will tell you first and give you a chance to put it right.

What we do not promise

Crited is provided as it is. We work hard on it, but we do not warrant that it will be uninterrupted, error free, or fit for a particular purpose, and we do not warrant that generated code is free of defects. Review what the compiler produces before you put it in front of your users; it is your application and your responsibility once it ships.

We are not responsible for third party services you connect, including Vercel, Supabase, GitHub, Stripe and model providers, or for what they charge you.

Liability

To the extent the law allows, neither party is liable for indirect, incidental or consequential loss, including lost profits, lost revenue or lost data, and our total liability for any claim is limited to what you paid us in the twelve months before it arose.

Nothing here limits liability that cannot be limited by law, including for fraud or for death or personal injury caused by negligence.

Changes to these terms

We may update these terms. If a change materially affects your rights we will give notice before it takes effect, and continuing to use Crited after that date means you accept the new version. The date at the top is always the current one.

Governing law

These terms are governed by the laws of the State of Delaware, United States, without regard to its conflict of law rules. Disputes will be brought in the courts of Delaware, unless the law where you live gives you the right to bring them somewhere else.

Privacy

How we handle personal data is set out in our Privacy Policy, which forms part of this agreement.