Terms of Service

The short version

code-anything.com turns a written description into a working, hosted app, and can edit a repository you already have. You own what it produces. We claim nothing in your prompts or your code. The output is written by AI models, so it can be wrong, and checking it before you ship it is your job, not ours. You pay for what you use. We can suspend an account that is being used to attack people. The rest of this page is the detail.

Agreement, and who may use the service

These terms are the agreement between you and code-anything.com (“we”, “us”) for the website at code-anything.com and the application behind it (the “service”). You accept them by creating an account or by using the service. If you do not accept them, do not use it.

You must be at least 16 years old and old enough where you live to enter a binding contract. If you are using the service for an employer or a client, you are saying that you have authority to bind them, and “you” in these terms means both you and them.

Your account

One human, one account, with a real email address we can reach you at. Sign-in is by one-time email link or by Google or GitHub — we hold no password of yours. Keep access to that inbox and that identity provider secure, because whoever has it has your projects. Everything done through your account is treated as done by you.

Tell us at hello@code-anything.com if you think someone else is in your account. Do not share an account to avoid paying for a second one, and do not create accounts to get around a suspension or to collect repeated free allowances.

What the service does

You describe what you want. The service plans it, writes the code in an isolated build sandbox, runs its own checks, and gives you a running preview. You can iterate in chat, edit files directly, connect a GitHub repository and push to it, import an existing repository and make scoped edits to that instead, and publish the result to our hosting. Builds are metered, and what a build cost is shown to you.

The service is under active development. Features appear, change and occasionally get withdrawn. Anything described as beta or experimental is exactly that.

Your content, and who owns it

You own your code. Your prompts, your briefs, the documents and images you attach, the files you write, the repository you import and the source code the service generates for you are yours. We claim no ownership of any of it, and no share in whatever you build with it. What the service produces is ordinary source code: you can push it to your own GitHub repository, read every line of it, and run it somewhere else entirely.

To the extent we hold any rights in generated output, we assign them to you. Two honest caveats. First, AI models can produce the same or similar output for two different people, so you should not assume your generated code is unique, and we cannot promise it is. Second, generated code includes open-source libraries and sometimes code patterns that carry their own licences — those licences are yours to comply with, and we do not override them.

The service itself is not yours: our software, our models’ orchestration, our designs, our templates as a collection, our documentation and our branding stay ours. You may use the template code that is written into your project as part of your own app, but you may not lift the platform.

The licence you give us

We need permission to do the thing you are asking for, and nothing beyond it. You grant us a non-exclusive, worldwide, royalty-free licence to store, copy, transmit, display and process your content, and to send it to the AI model providers and infrastructure providers listed in our Privacy Policy, for these purposes only: running the builds and edits you ask for, showing you your projects, hosting the apps you publish, keeping the service working, and meeting the law.

That licence lasts as long as we hold the content and ends when you delete it. It is not a licence to publish your work, to show it to anyone else, or to sell it. We do not use your prompts or your code to train our own models, and we do not licence them to anyone else to train theirs.

AI output, and your responsibility to review it

This is the section that matters most, so it is not buried at the bottom.

The code this service writes is generated by AI models. It can be wrong. It can look correct and be subtly broken. It can contain security holes, mishandle personal data, get an authorisation check backwards, or reproduce code that infringes someone else’s rights. It can be confidently wrong about a library’s behaviour. None of that is a rare failure mode; it is the normal behaviour of this technology, and no amount of tooling has removed it.

The service does run an automated review of its own work — it checks the build, exercises the app, and a separate reviewer reads the diff before the work is accepted. That catches a great deal. It is a quality step, not a guarantee, and it is not a substitute for your own review. Do not treat a passing review as a security audit, a code review, a legal review, or a fitness-for-purpose assessment.

So: before you put anything in front of real users, take real payments, or handle anyone’s personal or health or financial data, read the code, test it, and have someone competent check it. You decide what ships. You are responsible for what ships. If your app needs professional advice — legal, medical, financial, regulatory — get it from a professional; neither we nor a language model is that professional.

Acceptable use

This is a platform that writes and runs code and then puts it on the internet, so the rules are about what you build and host, not just about how politely you use the website. Do not use the service to:

• build, refine or distribute malware, ransomware, spyware, credential stealers, botnets, exploit kits or phishing pages — including “for research” or as a “demo”;
• host or distribute illegal content, child sexual abuse material, non-consensual intimate images, content that incites violence, or material you have no right to publish;
• impersonate a real person, company, bank or public body, or build anything designed to deceive people into giving up money, credentials or identity documents;
• send spam or bulk unsolicited messaging from an app you host with us, or use the service to operate a service that does;
• attack the platform: break out of the build sandbox, reach another tenant’s data or projects, probe or exhaust shared infrastructure, bypass the sandbox network restrictions, or interfere with anyone else’s builds;
• circumvent metering, rate limits or credit accounting — including scripted or automated use designed to consume compute faster than the interface allows, and sharing or reselling access so more people use one plan than it is priced for;
• resell our compute: running a build farm, a proxy, a mining or distributed-compute workload, or reselling the service as your own AI coding product;
• scrape or crawl the service, extract our prompts, templates or model routing, or use the output to train a competing model;
• do anything unlawful, or anything that infringes someone else’s intellectual property, privacy or other rights.

API requests are rate-limited, and builds have spend limits. Those limits exist to keep the platform up and to stop a runaway agent emptying your balance. Working around them is a breach of these terms.

Apps you publish, and the people who use them

An app you publish runs on our infrastructure under a URL we provide, but it is your app. You are its operator. You are responsible for what it does, what it collects, and what you tell its users — including its own privacy notice and terms, a lawful basis for any personal data it handles, and any consent, accessibility, consumer or sector rules that apply to it. If your app collects data about other people, you are the controller of that data and we process it on your instructions.

We do not review published apps before they go live, and hosting one is not an endorsement of it. We can take down an app that breaches these terms, that is unlawful, or that is causing harm to our infrastructure or to other people.

You can take your work with us out at any time by pushing it to your own GitHub repository. There is also a handover flow for transferring a project to someone else, and it is worth knowing what it can and cannot do: a GitHub repository can genuinely be transferred, but the hosting project and the managed database cannot be moved between accounts by any API that exists — those have to be recreated under the new owner’s own account, and the handover record says so rather than pretending otherwise.

Third-party services and your own credentials

The service connects to other people’s systems: GitHub, Stripe, AI model providers, our hosting and database providers, and whatever your app itself talks to. Your use of those services is governed by their terms, not ours, and we are not responsible for what they do, how they change, or when they are down.

If you paste in your own API keys or environment secrets, they are encrypted and used only to run your project, as described in the Privacy Policy. You are responsible for having the right to use those keys, for what is spent on them, and for rotating them if you think they have been exposed. Connecting GitHub grants read and write access across your repositories, because GitHub’s authorisation has no narrower option; if that is more access than you want to give, do not connect it.

Plans, metering and payment

Payments are handled by Stripe. Card details are entered on Stripe’s checkout and never reach our servers.

• Plans. A paid plan is a monthly subscription, charged in advance. Each plan grants an allotment of build credits for the period. Current plans and prices are the ones shown on our pricing page and in your billing settings at the time you buy.
• Credits reset, they do not accumulate. A plan’s allotment is granted at the start of each billing period and unused credits from the previous period do not roll over.
• Metering. Builds and edits consume credits based on what they actually cost to run — model usage and sandbox compute time. A long or ambitious build costs more than a small edit. What each run cost is recorded and visible to you.
• Top-ups and add-ons. You can buy one-time credit packs, and some capabilities — a dedicated database for a project, for example — are separate paid add-ons. These are charged when you buy them.
• Taxes. Prices exclude any VAT or sales tax that applies, which is added at checkout where required.

We can change prices, plan contents and credit rates. We will give account holders reasonable notice by email before a change affects a subscription you already have, and the change takes effect at your next renewal. If you do not want the new price, cancel before it applies.

If a payment fails, we may pause paid features until it succeeds. Credits and balances have no cash value, cannot be exchanged for money, and are not transferable between accounts.

Cancellation and refunds

You can cancel a subscription at any time; email hello@code-anything.com and we will stop the renewal. Cancelling stops future charges. Your plan runs to the end of the period you have already paid for, and cancelling does not by itself delete your account or your projects.

Charges already made are not generally refunded, because the compute they paid for has usually already been spent on your builds. Two things we will say plainly. If the law where you live gives you a refund or cancellation right, that right applies and these terms do not remove it. And if we have billed you for something that did not run, or that failed because of a fault on our side, write to us and we will sort it out — we would rather fix it than argue about it.

Suspension and termination

You can stop using the service whenever you like. Deleting a project from your dashboard removes it and everything attached to it, immediately and permanently. Account deletion is handled by a person, not a button: email us from your account address and we will delete the account and its projects within 30 days, as the Privacy Policy describes.

We can suspend or close an account, or take down a published app, if it breaches these terms, if it is being used unlawfully, if it is threatening the stability or security of the platform, or if payment has failed and stayed unpaid. Where it is reasonable we will warn you first and give you a chance to fix it; where the problem is active abuse, an attack, or something illegal, we will act immediately.

If we close your account for a breach, we may keep it closed. If we close it for any other reason, or discontinue the service, we will give you reasonable notice and a chance to export your work, and we will refund the unused part of a period you have paid for. After an account is closed, do not assume your data is still retrievable.

Availability and changes to the service

There is no uptime commitment on self-serve accounts. We do not offer a service level agreement, and we are not going to imply one we do not run. The service depends on infrastructure and AI providers we do not control, and it will sometimes be slow, degraded or down. Builds can fail. Model providers change or withdraw models, and the models the service uses will change over time.

We may add, change or remove features, and we may perform maintenance without notice. Your projects and files are stored durably, but keep your own copy of anything you cannot afford to lose — pushing to your own GitHub repository is the straightforward way to do that.

Disclaimers

The service is provided as it is and as it is available. To the extent the law allows, we make no warranties about it — not that it will be uninterrupted or error-free, not that a build will succeed, not that generated code will be correct, secure, complete, non-infringing or fit for any particular purpose, and not that defects will be fixed. Any implied warranties are excluded to the extent the law permits.

Nothing here excludes liability that cannot lawfully be excluded, including for death or personal injury caused by negligence, or for fraud. If you are a consumer, your statutory rights stand whatever this page says.

Limitation of liability

To the extent the law allows, we are not liable for indirect, incidental, special or consequential loss, or for lost profits, lost revenue, lost business, lost goodwill, or lost or corrupted data or code, arising out of your use of the service — even if we were told such loss was possible.

Our total liability to you for all claims in any twelve-month period is limited to the greater of the amount you paid us in the twelve months before the claim, or one hundred US dollars.

In particular, and consistent with the section on AI output above, we are not liable for loss arising from code the service generated that you chose to deploy. Reviewing it was your call to make.

Indemnity

If someone brings a claim against us because of what you built, published or hosted with the service, because of how you used it, or because you broke these terms or the law, you will cover our reasonable costs and any damages. We will tell you promptly about any such claim, let you take over the defence of it if you want to, and not settle it without asking you.

Changes to these terms

We may update these terms. The date at the top of this page always says when. If a change materially affects your rights or what you pay, we will tell account holders by email before it takes effect. Carrying on using the service after that means you accept the new version; if you do not, stop using it and ask us to close your account.

Governing law

This section is not finished, and we would rather say so than name a country at random. We have not yet published the legal entity behind code-anything.com or the law and courts these terms run under. We will state both here, and update the date at the top, before we rely on this section against anyone.

Until then: nothing in these terms takes away the protections of the mandatory consumer law of the country you live in, and if you have a dispute with us, write to hello@code-anything.com first — almost everything is solvable that way.

The rest

These terms, together with the Privacy Policy, are the whole agreement between us about the service. If a court finds part of them unenforceable, the rest still stands. If we do not enforce something straight away, we have not given it up. You may not transfer your rights under these terms without our consent; we may transfer ours if the business is sold, and we will tell you if that happens.

Contact

Questions about these terms, a bill, or an account: hello@code-anything.com. Security problems go to the same address — please tell us before disclosing publicly.