By using Workshop you’re agreeing to a small handful of things, written here in the same voice as the rest of the product. The point is to be clear, not clever. If anything below is genuinely confusing, that’s a bug — tell us.
Last reviewed by counsel: pending — please consult counsel before public launch. This page is written by the founder in designer voice and has not yet been across a lawyer’s desk. Treat it as a statement of intent until that review lands.
Workshop is a tool. It gives you a structured canvas for thinking through a product idea and — when you pair Claude Code — a way to produce a brief you can hand off to another tool that builds the thing.
Workshop is nota creative team, not an agency, and not a partner on your project. The output of the canvas is yours — what it says, whether it’s any good, whether it should ship — that’s on you, the same way it would be if you wrote the brief on a piece of paper.
The projects you create in Workshop are yours. We’re hosting them so you can come back to them; we’re not claiming any ownership of the words, sketches, or briefs you put in.
You’re responsible for keeping your sign-in details to yourself. If someone else gets into your account because you shared the password, that’s on you.
One human, one account. Don’t share an account with a team — Workshop is built for one person at a time. Team workspaces are a later question, not a hidden upgrade.
You can leave at any time. Settings → Account → Delete account wipes you out, no exit interview required. Export your data first if you want a copy.
Most of this is common sense. The list exists so we can point at it if we ever need to.
Don’t use Workshop to plan or generate illegal content. That covers the obvious things — child exploitation, targeted harassment, malware, fraud — and anything else that would land on the wrong side of UK or EU law.
Don’t paste in things you don’t have the right to use. If your brief contains someone else’s copyrighted material or confidential information, that’s your call to make, not ours, and the consequences are yours too.
Don’t abuse the canvas at scale. Scripted bulk writes, multi-account schemes, or shared-account farming will get the account turned off.
Don’t try to break into someone else’s account, read someone else’s projects, or poke around the infrastructure looking for weaknesses without telling us first. If you find a real security hole, please email us at hello@workshop.aicity.dev.
Don’t resell Workshop — either the product, or a wrapper around it — without asking us. We’re a small operation; cloning the surface and sticking a price on it isn’t a fair use of what’s here.
Best-effort, not an enterprise contract. We aim for the kind of uptime you’d expect from a serious small product, but Workshop is run by one designer plus the services listed in the Privacy page — if any of those have a bad day, Workshop has a bad day.
When you pair Claude Code, the AI writing runs there — and a Claude Code or Anthropic hiccup further down the chain will sometimes mean a write fails. Try again.
We don’t make uptime promises with numbers attached. If your work depends on a hard service-level guarantee, please use a tool that offers one.
Today it’s free if you bring your own Claude Code, and $19 a month if you don’t. The full version of that story is on the Pricing page. If we ever need to change the price, we’ll say so plainly, give you fair notice, and grandfather existing subscribers in.
Refunds: if Workshop goes properly wrong on us — sustained outage, we lost your data, the translate path stayed broken — email us and we’ll sort it. We’re not robotic about that.
You can leave whenever you like — delete your account from settings and that’s the end of it.
We can also stop the relationship from our side, but only for good reason: if you’re using Workshop to do something on the “things you can’t do” list, if your account is causing harm to other people, or if the law tells us to. We’ll tell you why before we close anything down, unless we’re prevented from doing so.
Workshop is provided as-is. We do our best, but we don’t promise it’ll be the right tool for every job, that it’ll be available every minute of every day, or that the briefs it produces will be flawless — AI output is fallible and you should read what comes out before you act on it.
If something Workshop does (or doesn’t do) ends up costing you money, our liability is capped at the amount you’ve paid us in the previous twelve months. If you’re on the free tier, that figure is zero. We’re not on the hook for indirect or consequential losses — lost revenue, lost contracts, lost weekends — even if we should have seen them coming.
Nothing in these terms tries to cut out rights you have under your local consumer protection law. UK and EU consumers especially: your statutory rights stand whatever this page says.
To be confirmed once Workshop has its operating entity formally set up. The intent is that these terms are governed by the law of the country that entity is registered in, with disputes heard in that country’s courts — subject to any consumer-protection rights in your own country. Please consult counsel before launching publicly — this is the line that most needs a lawyer.
If we change the meaningful bits — what you can do, what we’re responsible for, what you’re paying — we’ll email you about it before it takes effect, with enough notice that you can leave if you don’t want to carry on. Cosmetic edits (a clearer sentence, a fixed link) won’t trigger an email.
Workshop is run by one designer, so the support address goes straight to a human: hello@workshop.aicity.dev. The companion document for “what we know about you and how to wipe it” lives at Privacy.