Last updated: July 2026 · written in plain language.
Krucible brings product thinking to your AI agents — it drives your agent through discovery, spec, build, review, and launch, inside the tools you already use and on your own model key. It runs locally, so your idea, your code, and your decisions stay with you.
So the work happens on your machine, in your agent, on your key. The only thing Krucible sends on its own is an anonymous, opt-out usage count — no code, no content, no account. If you join the early-access list, we keep the email you give us to tell you when your plan opens. We don't sell your data and we don't train on your work. The rest of this page is the detail — exactly what leaves your machine, what never does, and how to switch it off.
The build itself — discovery, design, architecture, the build loop, the reviews, the gates, launch, and docs — runs inside your agent harness (Claude Code, Claude Cowork, and more soon) on your own model key. Your prompts and code go straight to the model provider you chose, under your key; we never see them, and their privacy policy governs that exchange. Deliverables are written to your own git repo and your own Notion board. Commands like ask, review, and build-story read only your local project and produce local files; their answers and exports stay on your machine.
Two steps hand content to a tool you own, under your own account: code-review sends the code being reviewed to OpenAI Codex for a second opinion, and your backlog is written to your Notion workspace. Both run under your accounts and their terms — Krucible passes the data through, it doesn't keep a copy or route it to us.
So we can see whether people actually use what we ship — without accounts — Krucible sends a small, anonymous ping when a command runs: a random ID, the command name, the version, and your operating system. Never your code, prompts, product, files, name, location, or any personal identifier. Opt out any time with krucible telemetry off and nothing is sent at all.
What we collect. The early-access form appears on the landing page and at the foot of most pages here. When you submit it we store your email address, the date and time, and which page you signed up from. After that we ask one optional question — “what would you build with it?” — and if you answer, we store that too. Skipping it changes nothing. That is the whole list: no name, no company, no cookies set by the form, no tracking pixel, no profile built about you.
Why we collect it. To send you one email when Krucible opens, and to count how many people are waiting. The optional answer helps us build the right thing. We never sell it, rent it, share it, or add you to a drip sequence. If a signup count is ever shown publicly it is a total only — your address is never published, and no page on this site can read the list.
Where it is stored. In a private Google Sheet owned by Krucible, written through a Google Apps Script endpoint. Google acts as our processor; the sheet is access-controlled and not public. If you submit the same address twice, we keep the one record rather than adding another.
How long we keep it. Until Krucible opens and we have sent that one email, or until you ask us to delete it — whichever comes first. If the launch email bounces or you never engage, we remove the record within 12 months.
How to get it deleted. Email hello@krucible.build from the address you signed up with, or naming it, and we will delete the row — email, note, source, and date — and confirm when it is done. You can also ask us to show you what we hold, correct it, or send you a copy. No account or form is needed.
The site uses privacy-friendly, cookieless analytics — page views only, no advertising profiles. Krucible products carry no ads, the site sets no marketing cookies, and there's no consent banner to click through.
Here's everyone who might touch your data, and why. Each operates under its own privacy policy:
Some of these processors are based in the United States, so the anonymous metrics and any email you give us may be processed there and in other countries. Where the law requires it, those transfers rely on the providers' standard contractual clauses and transfer safeguards. Your product itself — code, decisions, deliverables — never enters this flow; it stays in the places you already own.
Krucible isn't directed at children and isn't intended for anyone under 16. We don't knowingly collect data from children. If you think a child has sent us something, email hello@krucible.build and we'll delete it.
We hold as little as possible and protect it with the controls of the services above — an access-controlled sheet for the waitlist, reputable processors for the rest. No system is ever perfectly secure, but there's very little here to lose: the build, and everything sensitive in it, stays on your machine.
Turn off usage metrics any time with krucible telemetry off. For the email we hold, you can ask us to show it, correct it, delete it, or send you a copy — just email hello@krucible.build. Depending on where you live you have rights under the GDPR (access, correction, deletion, portability, objection, and the right to complain to your data-protection authority) and the CCPA/CPRA (know, delete, correct, and opt out of any sale or sharing). We don't sell or share your personal information, we honor Global Privacy Control signals, and we'll answer any request within the time the law allows.
We don't collect your code or product content, we don't require an account to build, we don't sell or share personal data, and we don't train anything on your work. If any of this changes, this page changes first — and anything that leaves your machine stays opt-out.
You're free to use Krucible to design, build, and ship your own products. You may not resell or redistribute Krucible itself, pass it off as your own, or try to reverse-engineer how it works.
Anything you create with Krucible — your product, your code, your decisions — belongs to you. You're also responsible for it: that what you build and ship is legal, works, and is safe for the people who use it. Krucible helps you decide and review, but the final call, and the accountability, are yours.
Don't use Krucible to build or ship anything illegal, harmful, or abusive — malware, fraud, harassment, infringement, or anything that breaks the law where you or your users are. Don't attack or overload our website or services. If you do, we may stop providing Krucible to you.
Krucible is provided "as is," without warranties of any kind. It guides an AI agent, so it can be wrong, miss things, or produce results you didn't expect — and we don't promise it will be uninterrupted, error-free, or fit for a particular purpose. Always review what it produces before you rely on it or ship it.
To the extent the law allows, Krucible and its maker aren't liable for indirect, incidental, or consequential damages, or for what you build, ship, or lose while using it. Nothing here limits any liability that can't be limited by law.
Pro and Team are coming soon. When they open, their billing terms — price, renewal, cancellation, and refunds — will be set out here and at checkout, and handled through our payment processor. Everything described as Free stays free to use.
If we update this privacy policy or these terms, we'll change the date at the top and, for anything material, note what changed right here. Continuing to use Krucible after a change means the updated version applies.
Questions about your privacy, your data, or these terms? Email hello@krucible.build.