Terms of service

What Rendeer does

You describe a design tool. Rendeer builds it: a working application with controls that drive a canvas. You can run it, edit it by describing the change, export what it draws, publish it, or take it away as a React component.

Tools are generated by AI models. That is the product, not an implementation detail, and the section on AI output below is the most important part of this page.

Your account

You need an account, you must be at least 16, and you are responsible for what happens under it. One person, one account. Do not share your credentials, and tell us if you think somebody else has them.

Credits, plans and refunds

Builds and edits are paid for in credits. Current prices are on the plans page and are quoted at the moment you buy.

Subscriptions renew automatically until you cancel, and cancelling takes effect at the end of the period you have already paid for. Credits included with a subscription do not carry over past the period they were granted in. Credits you buy as a top-up do not expire while your account is open.

If a build fails through our fault, the credits are returned automatically. If you stop a build yourself, the credits are returned too. Beyond that we do not offer refunds, except where the law where you live says otherwise, and in the EU and the UK it does: you have a statutory right to cancel a purchase within 14 days, which you waive for the portion already delivered once a build has run.

Who owns what

You own what you make. The prompts you write, the tools built from them and everything they export are yours. We claim no ownership of them.

You give us the limited licence we need to run the service: to store your content, to send it to the model providers that build your tool, to display it back to you, and, if you publish it, to show it to other people. That licence ends when you delete the content, except for copies other people have already remixed.

Rendeer owns the service itself: the site, the build pipeline, the runtime that generated tools are built on, and the Rendeer name and mark. Generated tools include a copy of that runtime, and you may use, modify and ship it as part of a tool you built here.

AI output, and what we do not promise about it

This is the part worth reading twice.

Tools are written by AI models. We check every build before handing it over: each control is driven and measured against the canvas, and a control that does nothing is repaired rather than shipped. That is a real check and it catches real failures. It is not a guarantee of correctness, fitness for any purpose, or originality.

AI models are trained on large bodies of existing work and can produce output that resembles something else. We do not screen output for infringement and we cannot. If you are going to use a generated tool or its output commercially, satisfy yourself that you are entitled to.

Two people who describe the same thing may get similar tools. Nothing in these terms gives you exclusivity over an idea, a technique or a visual style.

You are responsible for what you do with what you build. Do not use a generated tool where a failure would hurt somebody, and do not present its output as verified by us.

Publishing and the community

Publishing a tool makes it visible to everyone and lets anyone remix it. A remix is a copy that belongs to the person who made it. You cannot un-publish somebody else’s remix, and deleting your original does not delete theirs.

What you may and may not publish is set out in the acceptable use policy, which is part of these terms. We may remove content that breaks it, and we may suspend an account that does so repeatedly.

Agent and API access

Rendeer can be driven by an AI agent over MCP using an API key tied to your account. Everything done with that key is done by you, is charged to you, and is subject to these terms. Keep the key secret and rotate it if it leaks.

Availability

Rendeer is offered as it is. We do not promise it will be available, we do not offer a service level agreement, and we may change or withdraw features. We will give notice before a change that would break something you rely on, where we can.

Builds are stored on infrastructure that can fail. Keep your own copy of anything you cannot afford to lose. Idle accounts have their built files reclaimed on the schedule in the privacy policy, and you are always warned first.

Liability

To the extent the law allows, we are not liable for indirect or consequential loss, for lost profit, or for lost data. Where we are liable, our total liability is capped at the greater of the amount you paid us in the 12 months before the claim, or 100 US dollars.

Nothing here limits liability for death or personal injury caused by negligence, for fraud, or for anything else that cannot lawfully be limited. If you are a consumer, your statutory rights are unaffected.

Ending it

You can close your account at any time. We can suspend or close an account that breaks these terms or the acceptable use policy, and we will say why unless saying so would make the problem worse.

If we close the service, we will give you at least 30 days to export your work and we will refund the unused part of any subscription.

The rest

These terms are governed by the law of England and Wales, and the courts there have jurisdiction. If you are a consumer, this does not deprive you of the protection of the law where you live.

If a clause turns out to be unenforceable, the rest survives. Our not enforcing something once does not mean we have given it up.

We may update these terms. If a change is material, we will email you before it takes effect, and continuing to use the service after that means you accept it.