Your key never leaves
Everything is encrypted in your browser. The server only ever sees ciphertext.
01The product
Don't trust us. Verify us.
Every guarantee is enforced by the code path your data travels — not a policy page.
Answers in an enclave
Your context decrypts only inside the session — never on disk, never in logs.
Every answer, signed
10 cryptographic checks run in your browser. No trust in us required.
Delete means delete
“Forget” returns a Merkle proof the memory is gone — not a hidden flag.
Private retrieval
What’s relevant to you is found inside the enclave — and never leaks out.
Anchored on Solana
Build registry and receipt anchors are real mainnet transactions.
02How it works
Write. Ask. Verify.
From your device to a provable answer in three moves.
01
Write
Notes encrypt in your browser. Your key stays on your device.
02
Ask
Retrieval + the model run over your memory inside the enclave.
03
Verify
A signed receipt proves what happened. Anchor it on mainnet.
03The upgrade
Same agent. New superpowers.
Put MNEMOX under any assistant and here's what changes.
Agent without MNEMOX
Agent + MNEMOX layer
Memory
Forgets you between sessions
Memory
Persistent memory, every fact a commitment
Privacy
Provider reads every prompt
Privacy
Ciphertext only — key never leaves your device
Deletion
“Deleted” = a hidden flag
Deletion
Merkle proof the memory is gone
Trust
A policy page you believe
Trust
Signed receipt, 10 checks in your browser
Audit trail
Nothing to show anyone
Audit trail
Receipts anchored on Solana mainnet
One query through the layer
Your device
encrypts the question + memory
Enclave
retrieval + model, no logs
Receipt
ed25519-signed, browser-verified
Solana
anchored on mainnet
04Verifiable memory
Memory you can hold to account
Three capabilities no mainstream assistant has.
Not hidden in a UI — revoked and proven gone.
Every add, use and forget is a Merkle-commitment transition you can recompute yourself, so the “forget” button comes with a proof instead of a promise.
Provable use
See exactly which memories shaped each answer — revealed to you, no one else.
Provable deletion
Forget a fact and get a Merkle proof it’s gone from the new root — not hidden.
Boundary control
The memory policy is baked into the measured build and echoed in every receipt.
05Architecture
Five layers. Zero plaintext exposure.
Your data never leaves your control in the clear.
Client encryption
X25519 + XChaCha20. The key never leaves your device.
Encrypted storage
The operator holds ciphertext only. No keys, no reading.
Enclave inference
Context decrypts only inside the session. No logs kept.
Solana mainnet
Build registry, receipt anchors, SOL/USDC billing — live.
Verifiable memory
Add, use, delete — every operation is a provable event.