Open standard · v1.0 · July 2026
The disclosure boundary.
Our infrastructure handles only what this page says it may handle. The rule is simple enough to audit: the wire line equals the disclosure line. If an artifact would be unsafe to show a stranger, it never reaches us — it stays on the inventor’s machine, inside the Kit, under the inventor’s control.
What may cross the wire.
Four things, each non-confidential on its face. Everything we host, review, or route is built from these and nothing else.
Filing date
Month and year of a provisional or nonprovisional filing. This sets the countdown and the conversion deadline. Application numbers stay with the inventor until a formal buyer-side process asks under its own terms.
Field category
The domain and problem area — the same granularity a conference program uses. Never the mechanism, never the approach.
Fit briefs
Documents conforming to the published Fit Brief format, which excludes claims, mechanisms, drawings, and enabling detail by construction. A brief that violates the format gets flagged and returned; it does not enter the routing pool.
Contact details
Name and email, used for countdown notices and routing correspondence the inventor initiated.
What never crosses.
These stay on the inventor’s machine at every price, including the highest. Our paid products are built to make this possible: research packs are assembled from public sources and mapped against the private record locally, by the inventor’s own tools.
The invention itself
Claim text, specifications, mechanisms, formulas, algorithms, architectures, drawings, enabling examples, lab records, and the filed corpus. We structurally cannot leak, lose, or be compelled to produce what we never receive.
The working record
Inventor notes, model conversations, adversarial reviews, draft claims, and strategy documents. These stay in the matter workspace on the inventor’s machine, where the Kit’s source-separation rules keep them organized and priority-safe.
How the boundary is enforced.
The approval gate
Nothing leaves the seal without the inventor’s word-level approval. Every fit brief, every routing note, every artifact shown to a buyer-side owner is approved by the inventor first, in writing.
The audit trail
Every routed matter carries a record of what was shared, with whom, when, and under whose approval. The inventor holds a copy.
Non-confidential intake only
No form, product intake, or email flow we operate asks for anything past the four items above. If we ever ask for more, this page is the standard to hold us to.
Data-use policy.
What we do with the little we hold.
Aggregate patterns only
We study category-level patterns across matters — which fields are filing, which briefs earn invitations, which buyer categories respond — to improve routing. Analysis stays at category level; details from one matter are never surfaced to another, and nothing from inside a seal exists on our side to analyze.
No training on inventor material
We train no models on invention material, and the boundary makes this checkable: the material never reaches us.
Buyer-side symmetry
Buyer desks receive only conforming fit briefs matched to their declared categories. Their rejection reasons feed routing quality as category-level patterns, under the same aggregation rule.