Is my confidential spec safe with you?
IC specifications are among a design house's most sensitive assets. This page states the four data-governance commitments plainly — what holds today and what sits on the roadmap; like the product itself, we do not overstate our own maturity.
1.0 · FOUR THINGSFour data-governance commitments.
① Sandbox: no real specs required
The sandbox will run on demonstration data — once it opens, you can walk "specs in, evidence out" end to end without uploading a single real part number or spec. Evaluating with real parts belongs to a deployment conversation, after an NDA is in place.
② Data residency & isolation (cloud-edition design principles)
For the cloud edition (planned), data residency, tenant isolation (each company's data fully separated) and encryption design are confirmed to you in writing before deployment — these are commitments that go into contracts, not adjectives on a web page.
③ No training on customer data
Your specs and decision records are never used to train any model. AI appears only at build time, preparing rules from public regulation text; the runtime decision engine is deterministic code — same input, same result, no model inside.
④ Every conclusion auditable
Each conclusion carries inputs, rule version, source lines and a timestamp; the ruleset carries a version hash. You can always answer "what was this decided on at the time" — a product feature that doubles as the data-governance baseline.
Security certification (such as SOC 2) sits at roadmap Stage 4 — honestly labeled: planned, not yet obtained. Current commitments are the four above plus the deployment contract.
Data-governance details go fastest face to face.
Sandbox access is being prepared (demonstration data) — reserve now and be notified at opening. The cloud edition is planned for roadmap Stage 1.