Shield.N-O-Y-B
Fully Private Browser Based AI Chat Assistant with Context
Browser-local context · Encrypted proxy streaming · Enclave model server
End to End Encryption for AI
Client-Side Data
All conversations, memory embeddings, and context retrieval live exclusively in your browser. Nothing is written to any server database.
End-to-End Encrypted
Queries and responses are encrypted in the browser using HPKE before transit. The server proxy sees only ciphertext — it cannot read your messages.
Attested Enclave
Inference runs inside a Tinfoil attested enclave. Your browser verifies the enclave's identity via remote attestation before sending any data.
How it works
You type a message. It's saved to IndexedDB in your browser — never sent to our server.
Context and history are assembled locally. The full request is encrypted with HPKE before leaving the browser.
The server forwards opaque ciphertext to an attested enclave. Only the enclave can decrypt and respond — encrypted all the way back.
Why it works
IndexedDB
Your browser's built-in database. Conversations and memories stay on your device, not on any server.
HPKE Encryption
A modern encryption standard. Your messages are locked in the browser before they travel anywhere. The server only sees scrambled data.
Tinfoil Enclave
A sealed computing environment that runs the AI model. Even the people who operate the server cannot peek inside while it is running.
Remote Attestation
A hardware-backed check your browser runs before sending anything. It confirms the enclave is genuine and has not been tampered with.
Zero-Knowledge Proofs (RISC Zero)
The server proves it followed the rules without revealing any private data. Your browser can verify the proof independently.
sqlite-vec
A lightweight vector database running entirely in your browser. It powers the memory search that gives the AI relevant context from past conversations.