Privacy-First Developer Guides

A privacy claim is only as good as the architecture behind it. These guides cover what actually leaves the browser, how zero-knowledge designs hold up under scrutiny, and how to check the tools you rely on.

The guides here keep asking the same question: what actually leaves the device? The zero-knowledge explanation is the short answer and the whitepaper is the long one; both describe the same property, where the server holds ciphertext and never the key. The rest apply that test to ordinary work: an .env file that should be encrypted before it is committed, a prompt that should not carry a customer record into a chat window, an image that can be resized in a canvas instead of uploaded, and a QR code that encodes a contact detail you may not want on a printed poster.

The weakest dependency is the one that decides the answer, so the collection also covers how to check the tools you already use: whether a request leaves the browser when you press submit, what a CDN is able to see, and what a "nothing is uploaded" claim has to prove. Start with the architecture guides if you are designing something, or with the workflow guides if you are deciding what to paste where.