---
title: "Key and vault, kept apart"
description: "Why an AI agent should never hold your vault and its keys on one machine, and how Clavitor keeps them apart."
lang: en
url: https://clavitor.ai/en/separation
markdown: https://clavitor.ai/en/separation.md
authoritative: true
translations: [de, fr, es, it, pt, nl, pl, sv, da, no, fi, uk, ru, tr, ja, ko, zh, hi, th, vi, id]
publisher: Clavitor LLC
---

# Separation: The key and the vault never sit together.

An agent that holds both your vault and the keys to it can open everything in it, and so can anyone who takes over that agent. Clavitor keeps your vault on a server in the city you choose, hands each agent only the entries it is named to, and keeps your most private fields behind a key no agent and no server ever holds.

[How Clavitor protects your data →](https://clavitor.ai/en/security)
[Agent access in detail →](https://clavitor.ai/en/developers/agents)

## Why it matters: Whoever holds both, holds everything.

When a vault lives on the same machine as the agent that uses it, that machine is the only wall. A subverted skill, a prompt injection or a stolen laptop then reaches the vault file and the keys to open it, and what the agent could read, the attacker can read. Encryption only protects you while the key is somewhere else.

So the question to ask of any setup that gives credentials to a bot is simple: if this agent were taken over, what could it reach?

## How Clavitor keeps them apart: Four walls, each on its own.

- **The vault is at arm's length.** It lives on a Clavitor server in the city you choose, never on the agent's machine. The agent can't read the vault file, so it can't pry into entries it hasn't been given.
- **An agent gets only what it is named to.** Its scopes decide which entries the vault hands it; outside them it never receives even the encrypted value. No agent-facing endpoint lists the vault.
- **Your most private fields need your hardware key.** Card numbers, passport and ID numbers and the other fields under Identity Encryption are encrypted in your browser with a key that only your fingerprint, face or security key unlocks. No agent receives it, and no server ever sees it.
- **A stolen vault file is ciphertext.** Every entry is sealed under its own key, and the key that opens the vault is never stored on the server. A stolen copy of a vault file is ciphertext, and even a compromised server or a hostile sysadmin never gets the keys to your passwords or your private fields.

## If an agent is taken over: The damage stays small, and you see it.

- **Its token works only from where it first connected.** Every agent token is bound to the network address it first used; a stolen token used from anywhere else is refused.
- **It can't harvest.** Reads are rate-limited. An agent that keeps reading past its limit is frozen until you unlock it with your hardware key.
- **You cut it off alone.** Each agent is revoked on its own, without touching the others, and every read it made is in your audit log under its name.

## See it for yourself.

The full model, field by field, and how an agent connects.

[Read the security model →](https://clavitor.ai/en/security)
[Connect an agent →](https://clavitor.ai/en/developers/agents)
