Disclosure Policy
What we will say, to whom, and when — stated to you rather than only enforced against you.
Version 1.2 · effective 2026-08-28
Why there is a boundary at all
itriX works on the representation of computation. The value of that work sits in mathematics, in eligibility judgement and in implementation know-how, protected partly by patents and partly as trade secrets. If we explained the implementation to everyone who asked, there would be nothing left to license — and licensing is how the work reaches anyone.
So the boundary is not there to make you feel excluded. It is there so that there is something real to give you.
The four levels
- Public — anyone. What our technologies do and why it matters, our positioning, our products, the shape of the commercial path, and these instruments.
- Controlled — a visitor who has described their situation. A reflection of your problem, a brief written for your role, and the route we would examine first.
- Under NDA — a client whose NDA protects the relevant disclosure and whose current work has explicit authorization for the specific material. Within that approved scope, controlled technical explanation, eligibility conditions, proof summaries, validation boundaries, benchmark methodology, and a scoped assessment may be available. An NDA alone does not authorize every protected item.
- Under contract — a contracted customer, within the scope of the applicable agreement and content authorization. Your assessment, your evidence, your deployment material, your success plan.
And one that is not a level: implementation. Source code, the full transformation pipeline, kernel-level detail, our benchmark harness, unfiled invention detail and another customer’s results are not disclosed at any level, to anyone, without a licence. If we would not show it to you, we are not showing it to your competitor either.
An account is not a disclosure level
Holding an account is not a disclosure level.
What we can show and discuss is determined by the stricter of the position you are in and the stage the work has legitimately reached. It is not determined by whether you have an account or whether you have confirmed your email address.
A person who registers and says nothing reaches exactly what an unregistered visitor reaches. Signing in changes where your work is kept; it does not change what we can show you.
An NDA protects an authorized disclosure. It does not, by itself, authorize every protected item or expand access beyond the content and stage separately approved for the relationship.
What you can have before an NDA
A great deal. What our technologies address, which of them is likely relevant to you and why, where in your stack the pressure probably sits, what a proof would have to demonstrate, what an engagement would look like, and what additional material may be considered after the relevant agreement and authorization are in place.
That is enough for a serious first conversation, and we would rather have that conversation than a vague one.
What we will not do before an NDA
- Quote a performance figure, a benchmark result, or a saving.
- Explain how a method works at implementation level.
- Ask you for your confidential technical information — and if you send it anyway, we apply restricted handling and would still rather you had waited.
- Give you a price, a term, or an exclusivity position.
How we talk about evidence
We separate three things and never blur them. Proven — established mathematically, under stated assumptions. Measured — observed in a benchmark, under stated conditions, on stated hardware. Hypothesis — worth testing, not yet tested in your environment.
A negative result is reported as a negative result. A partial result is reported as partial. Neither is re-described afterwards as a learning, a promising signal, or a partial success. The credibility of everything we tell you later depends on this one, and it is the commitment on this page we would least like to be caught breaking.
Automated responses, and asking for more
The platform’s automated responses answer only from material approved for your level. They cannot be argued, prompted or persuaded into a level you have not reached, and neither can a document you upload. If you ask something above your level, you will be told plainly what would unlock it — and offered a person.
Material at controlled level or above is given for your organisation’s evaluation. Please do not publish it or pass it outside your organisation without asking.
If the boundary is in the way of a decision you are genuinely trying to make, say so. A person can explain which agreement, stage and content authorization would be required; an NDA alone does not create entitlement.