How we build, and what that means for your data.
This page exists so the people responsible for risk in your organisation can read our position directly, rather than reconstructing it from a sales conversation. It is written to be forwarded.
Everything below is a design requirement in every Orchyn build. Where a claim has a limit, the limit is stated. Anything specific to your operation is fixed in the design phase and written into the engagement before a line of code is delivered.
Five commitments that shape every build.
Your data stays in your environment
Operational data is processed within infrastructure you control. It is not pooled with other clients, not resold, and not used to train external models. Where a system needs to send data outside your environment, that route is documented, agreed in writing and limited to what the task requires.
AI identifies. Code calculates
A language model is used where judgement over messy input is genuinely needed, such as reading an unfamiliar invoice layout or reconciling inconsistent supplier feeds. Every figure that follows is computed by deterministic code against a named source. No number in an Orchyn system is written by a model.
Every output traces to its source
A finding is not useful if you cannot defend it. Each result records the input it came from, the rule applied and the calculation performed, so any figure can be reconstructed and put in front of a counterparty, an auditor or a board.
A person holds authority
Systems are assisted, never executed. Where an action carries commercial, legal or reputational consequence, the system prepares and evidences the decision; a named person in your organisation makes it. Automation removes the work, not the accountability.
You own the system outright
The system, the source code and the data are yours. There is no licence that expires and no platform you are renting. You can host it elsewhere, hand it to another supplier or run it yourself. Nothing in the commercial arrangement depends on you being unable to leave.
The questions your risk and IT teams will ask.
Answered as we would answer them in a procurement review, including where the honest answer is a qualified one.
Where is our data processed and stored?
In infrastructure you control, in a region agreed at design stage. UK and EU hosting are both standard. The specific arrangement is fixed in the design phase, before any build begins, and written into the engagement.
Is our data used to train AI models?
No. Your operational data is not used to train external models and is not contributed to any shared or pooled dataset. Where a third-party model provider is used, it is on terms that exclude training on submitted data, and we will name the provider and show you those terms.
Do you use third-party AI models, or run everything in-house?
Most builds use a hosted third-party model for the interpretation step, chosen for the task and named in the design. This matters, so we state it plainly rather than implying more isolation than exists: interpretation may involve a documented external provider under terms that exclude training and retention, while your operational data, records and calculations remain within your environment. Where a build genuinely requires that nothing leaves your infrastructure, that is a different architecture with different cost and capability, and we will tell you so before you commit.
What happens to our data if we stop working with you?
Nothing changes for you. You already own the system and the data, and it already runs in your environment. Our access is removed. There is no export process to negotiate because there is nothing of yours held anywhere else.
How do we verify a figure the system produces?
Every figure carries its working. You can trace any result back to the source document, the rule applied and the arithmetic performed. This is a design requirement in every Orchyn build, not a reporting feature added at the end.
Who at Orchyn can access our systems?
Access is limited to the named individuals delivering your engagement, on the least privilege needed to do the work, and is removed when the engagement or retainer ends. Orchyn is a two-founder consultancy, so the list of people is short and we will tell you exactly who is on it.
What personal data does a build typically involve?
That depends on your operation and is established during design. Where a system processes personal data, we document what is processed, on what lawful basis, how long it is retained and who can see it, and we will complete your data protection paperwork rather than asking you to infer it from a brochure.
Can our IT or security team review the build?
Yes, and we would prefer it. The design is documented before the build starts, specifically so that the people responsible for risk can read it and object early rather than late. You own the source code, so there is nothing we can hide in it.
Bring the people who will say no.
If your security, IT or compliance team has a question this page does not answer, put it to us before you commit to anything. We would rather resolve it now than discover it at contract stage.