Security & Data Sovereignty
Enclave's security model is simple: wherever possible, your data should never pass through us at all. Here are the five places where that principle lands in the engineering.
Self-hosted: data stays on your machine
Enclave uses a one-person-one-world architecture of independent instances. When you self-host, conversations, memories, notes and files all live in a database you control — local disk, your own server, or a cloud drive you choose. There is no central server and no background sync.
Hosted cloud: minimal-data principle
If you choose the official hosted cloud, we collect only the minimum needed to operate: account identifier, subscription status, error traces and request logs. None of it is used for advertising or shared with third parties — it exists solely for operations and billing.
MIT open source: every line is auditable
Enclave is fully open source under the MIT license. How data is stored and what gets sent to model providers isn't something you have to take on faith — you can read the source to verify it, or change it yourself.
Model connections under your control
AI conversation content is sent only to the model provider you configure (OpenAI, Anthropic, Google, DeepSeek and others, or a local model you host yourself). With your own API key, both billing and the data channel run directly between you and the provider.
Backupable, migratable, deletable
When self-hosting, your data simply is the data files on your machine: backups, migration to another instance, and complete deletion are all things you do directly. Managed-cloud accounts can be closed anytime, with data permanently archived and unrecoverable. We keep no copies you can't delete.