Plain English version: Workshop is a small tool run by one designer. We collect what we need to keep your projects on the screen, and not a scrap more. No analytics yet. No trackers. No ads. No selling your work to anyone.
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.
Six things, all of them obvious if you think about what the product does:
Your sign-in details. Email address, and a one-way scrambled version of your password (we never see the password itself). If you sign in with Google instead, we get the email and a stable identifier from Google.
Your profile. The name, avatar, and short “about” line you put on your settings page. Optional — leave them blank and Workshop still works.
Your projects and artefacts. Everything you type into the canvas: project names, folder names, personas, jobs, journeys, problem statements, briefs. This is the work itself. We store it so you can come back to it.
Pairing keys. When you pair Workshop with Claude Code, we generate a long, random key that lets your Claude Code talk to your projects. We store the key so we can tell it’s really you, and nothing else. You can revoke it from your settings page at any time.
Connection records. Light, technical breadcrumbs about your Claude Code connection — when it last connected, whether it’s online — so the canvas can show “paired” or “not paired” correctly.
Semantic-search embeddings. When you save an artefact, Workshop generates a short numeric fingerprint (an embedding) so Cmd-K search can find it. The fingerprint travels through OpenRouter to reach an OpenAI embedding model and back. We store the fingerprint against your artefact and discard the request transcript.
When you pair Claude Code, any AI writing runs inside your own Claude Code session — Workshop never sees the prompt or the model output. The canvas only stores what Claude Code writes back to your project.
Analytics. There are no third-party analytics on Workshop today. If we ever add product analytics, you’ll see a banner asking before anything starts measuring you.
Tracking pixels, ad networks, affiliate links, or fingerprinting. None. If a request leaves your browser, it goes to Workshop or to a service Workshop pays directly to run the product.
Your browsing history, location, contacts, calendar, or anything else outside Workshop’s own canvas.
Payment card numbers. When billing turns on, Stripe handles the card — Workshop only sees a customer reference and the subscription state.
Three cookies, all functional, none for tracking:
Sign-in cookie. Keeps you signed in between visits. Essential — without it Workshop forgets who you are on every page load.
Theme cookie. Remembers whether you picked light or dark. Optional, easy to clear.
Sidebar cookie. Remembers whether your sidebar is open or collapsed. Optional.
A small, named list of services Workshop pays to run the product. They process your data on Workshop’s instructions and they don’t use it for their own purposes.
Supabase hosts the database where your projects live and handles the sign-in machinery. Data sits in EU regions (Frankfurt and Paris).
Vercel runs the website itself — the page you’re reading right now. Vercel sees the standard request information any hosting service does (your address, the page you asked for, a timestamp).
OpenRouter routes the short numeric embedding requests Workshop generates for Cmd-K search. Your artefact title and summary travel through OpenRouter to reach the embedding model. AI writing happens inside your paired Claude Code session, never through OpenRouter.
Stripe will handle payment when billing turns on. Stripe sees the bits payment processors need to see (your card, your country); Workshop only gets a customer reference back.
That’s the full list. There is no other party with access to your projects.
For as long as your account is open. The moment you delete your account, your projects, artefacts, profile, and pairing keys are removed from the database. Backups roll off on their normal schedule (typically thirty days) and after that the data is gone for good.
Translation cache entries (only relevant on the unpaired path) are keyed to your project — they leave with the project.
Quite a lot. Workshop tries to make the obvious actions one click away rather than a support ticket.
Export everything. Settings → Account → Export your data downloads every project, artefact, and folder you own as a single JSON file. No queue, no email-confirm, no waiting.
Delete everything. Settings → Account → Delete accountwipes your account and all the projects in it. There’s no recovery. We’d rather you keep that power than have to email us for it.
Edit anything wrong. Profile, projects, folders — all editable from inside the app. If something can’t be edited and you think it should be, tell us.
Revoke Claude Code. The pairing key you generated for Claude Code can be revoked from settings. New key, old one stops working.
UK and EU users: under GDPR you also have the right to ask for a copy of the data we hold about you, ask us to correct or delete it, ask us to restrict how we use it, and complain to your local data protection authority. The export and delete buttons cover most of that already; for anything else, email us at hello@workshop.aicity.dev.
Best-effort, not enterprise-grade. Your traffic is encrypted in transit, your password is one-way scrambled, your database access is row-level scoped so one user can’t read another’s projects, and your pairing key is stored as a one-way hash so even we can’t read it back to you. If you’re storing legally sensitive material, please use a tool built for that.
If we change the way Workshop handles your data, we’ll update this page and email you about anything material before it takes effect. Cosmetic edits (clearer wording, fixed typo) 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 counts as fair use” and “who’s responsible for the output” lives at Terms.