ZetaMem™
by ZetaVault
ZetaMem · How it works
Built so we can't read your memories.
Every memory is encrypted on your device before it travels. Our cloud stores what it cannot open — that's the whole design, and here's exactly how it flows.
Your device
Where your memory lives in the clear
Your AI session talks to ZetaMem locally — Unencrypted data only lives on your machine.
On-device AI builds your search index locally. Your content is never sent away for processing.
Your keys lock every memory with end-to-end encryption before anything leaves. They never leave the device.
ZetaVault cloud
Where everything arrives encrypted
Stores encrypted objects — your memories arrive encrypted and are stored exactly that way.
Finds without reading — Proprietary encrypted keyword indexing returns your records, nothing that reveals what they say.
Holds no keys — there is no admin view, no support backdoor, no way for us to open your content.
Crosses the line
Encrypted memory objects · limited operational data needed to store & find them
Never crosses
Readable memory content · your encryption keys
Diagram 01 · Saving a memory
Encrypted before it travels
Six steps from “remember this” to encrypted storage. Everything readable happens on your device; only the encrypted result moves.
Step 01 · AI session
Your AI asks ZetaMem to save a memory
The request is first written into local memory — on your machine, under your account.
Step 02 · Guardrails
Every write is checked first
Only approved memory types can be written, and each one must pass structure and permission checks before anything else happens. Malformed or out-of-bounds writes are rejected on the spot.
Step 03 · On-device AI
Indexed locally, so search works later
A local AI model running on your device breaks the memory into searchable pieces and builds the index material — no cloud AI ever sees your content.
Step 04 · Sealing
Encrypted with your key — on your device
The memory content, its keywords, and its searchable pieces are all locked with military-grade encryption using keys that exist only on your device. Sensitive material is wiped from working memory the moment it’s no longer needed.
plaintext stops here — only encrypted objects continue
Step 05 · Delivery
The encrypted object travels over an encrypted connection
Delivery is built to be safe under failure: if the network drops, ZetaMem retries without ever creating duplicate memories.
Step 06 · Encrypted storage
Stored exactly as it arrived: encrypted
The cloud keeps the encrypted object plus the minimum operational data needed to store, find, and return it. Every account’s records are isolated from every other’s at the database level.
Diagram 02 · Recalling a memory
Opened only on your device
The cloud can locate your records. It still can’t read them — unsealing happens after they’re back in your hands.
Step 01 · AI session
Your AI asks for a memory
The request is written to the memory buffer and the keywords extracted
Step 02 · Local search
Two kinds of search, combined
ZetaMem searches by exact keywords and by meaning — using the index built on your device at save time — then merges both into one ranked list of likely matches.
Step 03 · Cloud fetch
The cloud returns encrypted records
The gateway looks up the requested records and sends them back still encrypted — it never opens what it stores.
Step 04 · Unsealing
Decrypted on your device, held in protected memory
Your device opens the records with your key and keeps the recalled content in guarded working memory — never written to disk in the clear.
Step 05 · AI session
Your AI continues with your context
The recalled memories are available to your session locally — your AI picks up where you left off.
