Trust center
What runs where, and what leaves.
Kyvvu decides inside your own process. This page covers what reaches our platform, how the record is kept, and how to get the documents your security and legal teams need.
By design
What the design keeps on your side.
- 01
Decisions in your process
The engine is a library inside your agent. No step passes through us before it runs, and an agent keeps deciding with its cached policies if our platform is unreachable.
no proxy
- 02
You choose what's sent
Policies and assignments go out to your agents. Step traces and incidents come back, unless one setting keeps traces on your own machines.
traces optional
- 03
A record you can check
Each task is recorded as an ordered trace of its steps, with the verdict on each one, hash-chained when it reaches the platform.
hash-chained
- 04
Hosted or yours
Use the hosted platform, or run it in your own infrastructure on Enterprise & Public: on-prem and air-gapped included.
self-hosted
- 05
Open-source SDK and policies
The Python SDK and the policy library are published under the Apache 2.0 licence.
Apache 2.0
- 06
Policies in your git
Your own policies are YAML files in your own repository, reviewed and versioned like the rest of your code.
policies as code
Questions
For your security and legal teams.
01Do you sign a DPA?
Yes. Every plan comes with our standard DPA; on Enterprise & Public we negotiate it with you.
02What data reaches the platform?
The agents you register, the policies assigned to them, and the step traces and incidents your agents send back. If you keep traces on your own machines, they don't reach us.
03Can we keep everything in our own environment?
Yes, on Enterprise & Public: run the platform in your own infrastructure, including on-prem and air-gapped.
Documents
Request our DPA, or ask your security questions.
Tell us what your security or legal team needs, and we'll get back to you by email.
Prefer to start with the docs? docs.kyvvu.com
Next
See the architecture on your agents.
For security teams
Request a demo
Thirty minutes on what runs where, with someone who builds it.