Terms
There is nothing here for you to accept.
There is no self-serve signup, no free tier and no trial you can start by entering a card, so there is no click-through agreement and nothing on this website binds you to anything. Reading these pages creates no relationship, and no button here accepts terms on your behalf.
What governs the service is a signed agreement negotiated with your legal team. This page says what it covers and what our starting position is, so nobody spends a week discovering it.
Website terms that nobody reads protect nobody. So there are none.
The one thing worth stating about this site: the pages are ours, the claims on them are meant to be relied on during an evaluation, and if you find one that is wrong we would rather hear about it than have it quoted back at us later.
What the agreement covers
The six things it settles.
| Clause | Our starting position |
|---|---|
| Scopewhat you are buying | Access for named people to named environments, through the connectors that are actually working. The catalogue distinguishes what is built from what is modelled, on connected systems, and we do not sell against the modelled column. |
| Term and exithow you leave | Annual, and leaving means your data is removed or returned and your access record exports first. Nothing about the design creates lock-in: there is no copy of your data here to migrate out, and the assistant contract was always yours. |
| Datathe processing terms | A separate agreement, summarised in plain English on data processing, signed alongside this one. |
| Availabilitywhat we promise | A commitment agreed per client, written against your environments and working hours. There is no single number on a website that would fit both. |
| Securityand what happens if | The obligations follow the model on the security model, which is written for your reviewer and covers isolation, secrets and identity. Breach notice is in the processing terms. |
| Intellectual propertyyours and ours | The platform is ours. Your data, your written rules and your configured vocabulary are yours, including where our engineers helped draft them. Anything encoding your own process stays yours if you leave. |
Before you draft
Three positions worth knowing early.
Each of these has cost somebody a redraft somewhere. They are here so the first version of the contract can already account for them.
We do not warrant the answers
This platform governs which systems a person may reach and records what happened. It does not make an assistant correct, and no clause anybody drafts will change that. Accuracy is something to verify in your own evaluation, and we will say so in the meeting as well as here.
Changes happen only where you switch them on
Writing into your systems is off by default. Where you switch it on for a project, each change is shown as a line-by-line preview and posted only after a named person confirms it, on a credential separate from the one that reads. Which projects and which people may do that is your decision, and it is written into the agreement for that project.
The assistant vendor is not in this contract
You hold your own agreement with whoever supplies your assistant, and what they do with a conversation is governed there. We are not a party to it and cannot make commitments on their behalf, which is the most common thing procurement tries to put in this document.
Pricing
Why there is no price on this website.
The platform is priced for a company, not per head: a platform fee plus the environments you connect. A per-seat figure on a website would start a headcount negotiation about a fixed cost. You get a number in the first conversation.