Skip to content

AI providers and your data

Agents use an AI model to read documents and prepare work, and that model is run by a provider. This page explains how the provider is chosen with you, what data is sent, how the provider’s terms are reviewed before your documents reach a model and the options for stricter handling.

The page names no provider. The choice is made with you, for your engagement.

The first agreement comes before day one of the Discovery Sprint. The Working Prototype runs your real documents through an AI model before any agent exists. So we agree in writing with your IT manager on two things: which AI model provider the prototype may use and on what terms, and where our forward-deployed engineers’ working copies and the prototype run. No document of yours reaches an AI model before that.

Then, before our engineers build the first agent, we agree with you, in writing, on which AI model provider each workflow may use. If your company already has an approved provider or an AI policy, we start from that.

To make the decision, you see three things for each workflow:

  1. Which steps call a model and which do not.
  2. What data each of those steps sends.
  3. The provider’s terms on training and retention.

A later change of provider or model is a change like any other. It is tested, the workflow owner signs it off and your IT manager agrees to it first.

AI model usage is billed at cost in every stage. In the Discovery Sprint that is only the prototype’s usage. Stages and terms lists the terms.

A model is called for one step of a workflow and receives the data for that step. It does not receive a copy of your ERP.

Illustrative example, for the front office of a manufacturer:

Step What is sent to the model What is not sent
Read an emailed purchase order The email and its attached PDF The rest of the inbox
Match the part numbers on that order The order lines and the candidate items The whole item master, costs and margins
Draft a follow-up email to a late supplier The late purchase order lines and the supplier contact Other suppliers’ prices
Answer an order-status question That customer’s open orders and ship dates Any other customer’s orders

Much of a workflow calls no model at all. Looking up a price, checking a credit limit and comparing a quantity are done by ordinary rules in the operations layer. A workflow at Level 0 (Recorded) has no agent, so its day-to-day work sends nothing to a provider. Before the review that moves it to Level 1 (Assisted), the agent is tested on work recorded at Level 0, and that test does send the recorded documents to the agreed provider.

The audit trail records the inputs of every agent action, so you can check afterward what an agent used. Audit trail and monitoring covers how.

Provider terms are reviewed before go-live

Section titled “Provider terms are reviewed before go-live”

Before a workflow with an agent goes live, we review the provider’s terms with your IT manager and the workflow owner. For the Working Prototype, the same review is part of the written agreement made before day one of the Discovery Sprint. Two questions come first:

  • Training. May the provider use what is sent to train its models?
  • Retention. How long does the provider keep what is sent, and for what purpose?

The answers are written into the records for that workflow, with the date and the people who reviewed them. If the terms do not meet your requirements, the workflow does not go live on that provider.

We quote no provider’s terms here. They differ from one provider to the next, and they change. The review is repeated when the provider, the model or the terms change.

If the default is not strict enough for a workflow, a customer or a kind of document, there are five options. Each has a cost. The choice is written down for each workflow before it goes live.

Option What it does What it costs
Mask fields Names, prices or account numbers are removed before a step is sent and put back afterward Some steps get harder for the model without the field, so the workflow is measured again
Exclude Named customers, suppliers or document types never go to a model. People handle them. That work stays manual
Stricter provider terms A provider arrangement with tighter terms on retention or on where data is processed Depends on what the provider offers. Usage is billed at cost.
A model you host The model runs in infrastructure you control, so the data stays there Fewer models to choose from, and hardware or hosting for you to pay for and run
No model The workflow stays at Level 0. The software captures the work and people do it. No agent on that workflow

We control what is sent, to which provider, under which reviewed terms, and what is logged. We do not control a provider’s own systems. That is why the choice of provider is yours to approve and why the stricter options exist.