Trust
What is yours stays yours. What is ours stays ours. The rest is written down first.
How a program's terms are settled, which controls are code and which are a promise, and what nobody has certified yet. One page, so the two never disagree.
01 · IP and data
Agreed before the first run, not after the result.
The terms below are settled while the brief is being written, when both sides can still walk away, which is what makes agreeing them easy.
You
Us
Yours
Your pre-existing designs, materials and confidential inputs stay yours. Nothing you send becomes ours by having been sent.
Ours
The platform, the models and the physics underneath them stay ours. A program licenses their output, never the framework.
What the program creates
Defined before work begins, and it varies: customer use rights, exclusivity in a field of use, joint ownership, or a commercial license. It is a term to negotiate rather than a default to discover.
What the platform learns
Where the agreement permits it, generalised and de-identified experimental learning improves the model. A measurement that missed teaches it as much as one that hit.
Who writes it
Wilson Sonsini is counsel. The patent estate and what stays a trade secret instead is the remit of an officer whose doctorate is in materials science.
The policy, in full
SuperMatics protects both partner confidentiality and the integrity of its platform.
Partners retain ownership of their pre-existing designs, materials, and confidential inputs.
SuperMatics retains ownership of its core software, models, and foundational know-how.
Rights to inventions created during a program are defined before work begins and may include customer use rights, field-specific exclusivity, joint ownership, or commercial licenses.
Where permitted, SuperMatics uses de-identified and generalized experimental learning to improve the platform for future work.
02 · Private by default
Some of this is enforced by software. The rest is the agreement, and the two are labelled.
In practice a program meets three of these in its first week: it signs in through its own directory, it gets a workspace, and the brief it agrees says what each bench partner will be shown. Everything after that is the agreement.
Enforced by the platform
Encryption
In transit and at rest, across everything a program puts into the platform and everything it gets back.
Who can sign in
Single sign-on through your own identity provider. Access follows the directory you already run, so removing somebody there removes them here, without asking us.
Workspace isolation
One workspace per program, and nothing reads across them. A bench partner is given a workspace holding what it has to make and measure.
Enforced by the agreement
Scope
A program's inputs are used for the work its brief describes. What a partner sends is scoped to that program.
What a bench is told
What it has to make and measure, and nothing it does not need in order to do that. Which of those it is gets decided by a person while the brief is being written, not by a permission.
What the platform learns
Generalised and de-identified experimental learning improves the model where the agreement permits it. That permission is a term to negotiate, never a default.
Not claimed at all
Certifications and audits
There is no certification to cite: no SOC 2 report, no third-party audit of the platform, and no published region or residency commitment. The three controls above are real, and none of them has been examined by anybody outside this company. When one has been, it will be named with its date and its auditor.
Every term on this page is settled before a program starts, and both sides sign the same page.