Self-audit checkpoint
Your AI now lives in a vault that only one machine on Earth can open
We regularly audit our own setup against the promises we make on this site. One item we wanted closed this cycle: making sure the hardware holding your chats, documents, and memories is encrypted at rest — in a way that survives theft, power cycles, and "we forgot to patch this."
It's done. Here's the plain-English version of what that actually means.
The short version: your data now sits inside a full-disk encrypted volume — everything on it is scrambled the moment it hits storage, and it only un-scrambles on the one machine that was built to hold it.
The fun part: it unlocks itself, and it can only be unlocked there.
Most "encrypted server" stories end with a key sitting somewhere on the same machine — a bit like keeping the safe's key under the doormat. Ours doesn't. The unlock key is bound to a TPM chip — a tiny security processor physically part of the server's motherboard. It can only authorize this exact piece of hardware, on this exact boot chain. So:
🔒 Stolen drive? A terabyte of beautiful, worthless noise.
🔒 Server moved to a different machine? Still locked.
🔒 3 AM reboot after a power blip? It wakes up, verifies itself, and comes back online — no humans, no passwords, no waiting.
No half-states either. The system is wired so that nothing starts up before the vault is verified and open. There's no window where your data exists "mostly decrypted" while things boot. Open, or nothing.
Was it worth the downtime? The only cost is a handful of CPU cycles per read and write — modern processors do this encryption with dedicated hardware, so fast that the disk runs out of breath long before the encryption does. In practice: no measurable difference.
The honest fine print (because we'd rather tell you the truth of it than hide behind a marketing page): we operate the hardware, so "encrypted" means "useless to everyone else," not "invisible to us." That's the whole reason the rest of our setup exists — no admin path into your conversations, deletion that's actually final (indexes and embeddings included), and isolation enforced at the network level rather than by a checkbox in a settings page.
Checkpoint closed. Next audit window, we move on to the next line on the list.