Your keys and your data
Watch: your keys never enter a prompt · 62 seconds · animated, sound on
The vault has no endpoint that reads a secret back out. A key that cannot be fetched cannot wander into a chat, a log, or a model's context. Not by accident, not by request.
The write-only vault
Passwords and API keys are stored encrypted on your own disk. The design detail that matters: the vault is write-only by design. There is no "show me the secret" endpoint, so nothing, including Cronus itself, can pull a key back out into text. The only things that ever come back from the vault are names, domains, and timestamps.
Local means local
With a cloud model, your text travels to someone else's computer and gets processed under someone else's policy. With a local model, your text never leaves this machine. For sensitive work, that is the strongest privacy guarantee there is, and Cronus lets you pick per job.
Everything important is on your disk
- Memory is a folder. Copy it, back it up, delete it.
- Transcripts are yours to keep or destroy.
- Settings live locally. No account, no cloud, no telemetry.
No platform stands between you and your work, which means no platform can take your work away. The ownership page covers why that matters.