Privacy & About

Circuitrize is an early, solo-built tool that's currently in testing. This page describes what it actually does — no legal boilerplate, nothing overstated.

What this tool does

You upload a KiCad schematic (.kicad_sch), and optionally a board file (.kicad_pcb) and project file (.kicad_pro). Circuitrize runs a set of deterministic checks against them — the same kind of electrical-rule and design checks a careful reviewer would do by hand — and shows you a readiness score, a bill of materials, and a copper-layer view. There's an optional AI-assisted layer for plain-English explanations and a second-opinion review, described below.

What happens to an uploaded file

This is described from what the code actually does, not from a policy written in advance:

• It's processed in memory / a temporary folder, then deleted. When you upload a file, it's extracted to a temporary working directory on the server for the duration of that single analysis request. That directory is deleted automatically the moment the request finishes — whether the analysis succeeds or fails. This isn't a policy decision layered on top; it's built into how the request is handled, so there's no code path where an uploaded file's contents persist afterward.
• Nothing is stored. There's no database, no account system, and no server-side session of any kind. Your board data lives in your browser tab for that session and nowhere else on the server after the request completes.
• Server logs stay minimal. If a board or project file fails to parse, a line noting the failure (filename and error type) may be written to the server's own operational log, for debugging — never sent back to you or anyone else. The errors this tool deliberately raises are not designed to carry your design content (component values, net names, etc.). That's not an absolute guarantee for every conceivable failure: for an unexpected internal error, the raw error text is logged as-is, so in an unusual case it could in principle carry a small fragment of your data — for example, an internal value that happens to match one of your net names.
• Standard web server access logs apply. Like effectively any web server, requests are logged with the basics (timestamp, path, status code, requesting IP) for operating the service — not file contents.

The AI-assisted features

Circuitrize has an optional layer — "Explain with AI", "Run AI Review", and a follow-up Q&A box — that uses Anthropic's Claude models. This is separate from the deterministic checks above and is clearly labeled as AI-assisted wherever it appears.

• It's off by default while this tool is in early testing. Nothing is sent to Anthropic unless you act: clicking "Explain with AI", clicking "Run AI Review", or sending a message in the Q&A box.
• When you use these features, the following is sent to Anthropic: your file's name; every component's reference designator, value, footprint, and library ID; every net's name, and the pins on it; the score; and every finding. If you use the Q&A box, your typed question and every earlier message in that conversation are sent too.
• Your uploaded file itself is never sent. A project filename can still carry a client or product name, though — rename the file before uploading if that matters to you.
• That data is subject to Anthropic's own API data-handling terms, the same as any application built on their API.

Distributor part search

The parts-search feature (looking up real part numbers) sends your search text to Mouser and/or Digi-Key's own APIs to fetch real pricing and stock — never your board file, and only the text you actually typed or a part number an AI suggestion proposed.

Who's behind this

Circuitrize is built by one person, currently in early testing. It isn't a company with a support team yet — treat it accordingly: useful for a second opinion before ordering boards, not a substitute for your own judgment or a professional review on anything safety-critical.