The evidence is yours.What leaves, what doesn't, and who can prove it — written down in one place.
Where the data sits
A cloud project in your name
The agent is deployed into a project you open, on your billing. There is no second copy on our side.
A European region
The data and the engine serve from a European region. It doesn't cross that line for us.
Your project, your billing
The bill and the control stay with you. Encryption is the cloud's own, at rest and in transit.
What leaves, and what doesn't
Nothing comes to us
We have nowhere to collect it. The only thing that leaves is an alert to your own team, to a destination you choose, with personal details removed first.
Our access, and how you end it
Deploy-time only
A temporary grant for the installation. At handover you remove it yourselves — so no standing access remains with us.
It closes when the work ends
Support is an access granted for a specific request and revoked after it. Not a door left open.
You switch it off, without asking us
Revocation happens in your project, in your permissions. We are not a party to it.
The record you hold
Every action is written down
What was done, when, how long, what it cost — a line for every action the agent takes.
It lives in your project
The log is written on your side, not ours. If we part ways, it stays.
A certificate expires.An architecture doesn't.
We will meet the standards as we grow into them — and we will tell you exactly which we hold and which we don't. Until then, what we offer instead isn't a promise: the agent runs in your project, so "we don't see the data" is a fact about the pipe, not a clause in a contract.