Encrypted by default. Local first.
The questions your security team will ask, answered plainly.
Encrypted at rest
The whole vault database is encrypted with SQLCipher using a random key, itself wrapped by your vault key. Attachments and files are encrypted with AES-256-GCM.
Keys in the keychain
Passphrases and API tokens live in the operating system's keychain, not in config files.
Local-first
Each vault lives on its owner's machine. The local API listens on localhost only and requires a bearer token. Models can run locally through Ollama.
Sharing you control
Hive sharing is per connection and per project. Shared content is encrypted at rest on the relay. It is not end-to-end encrypted: a running relay decrypts to fan out, so run it on infrastructure you trust.
Approval gates
Destructive curation such as purging is approval-gated and goes through the trash; archiving and roll-ups are reversible.
Sandboxed connectors
Loom connectors run in a sandbox limited to the hosts and folders they declare. Two hand-reviewed connectors (Gmail, Google Photos) run as trusted code.
Secrets stay outside the sandbox
Connector credentials live in the OS keychain. Connectors receive only an opaque handle; authenticated requests are made host-side.
Off until you turn it on
New features ship disabled. Integration tokens see a reduced tool set; primary-only tools stay with the owner.
Request access
Bring Cortexa to your team.
Tell us a little about your team and what you would use it for. We read every request.
Request access