Architecture — Zero-Knowledge by Design
A verifiable demonstration that Zkomi processes health data without ever possessing it.
Published:
Zkomi is built on a zero-knowledge architecture. All health-sensitive computation — dose timing, body clock position, compound scheduling — happens entirely on your device. No health data is transmitted to any server at any point.
This page demonstrates that architecture in action. Open your browser's Developer Tools, go to the Network tab, and observe: zero health data calls. Nothing leaves your device. Nothing can be demanded that doesn't exist.
Live Proof of Concept
This demo runs entirely in your browser. No server receives your input. No database stores your data. No analytics track your behavior.
How It Works
1. Local Encryption
Your health data is encrypted on-device using AES-256-GCM before it's stored. The encryption key is derived from your passphrase and never leaves your device.
2. Zero Server Transmission
Protocol data, dose schedules, and health information are never sent to any server. The network tab in your browser confirms this.
3. Verifiable Privacy
Unlike policy-based privacy claims, Zkomi's architecture is verifiable. Inspect the code. Monitor the network. The proof is in the property: we cannot access what we never receive.
The Two Modes
Fox Mode
No backup. No recovery. Delete the app, and everything is cryptographically erased. This is the pure zero-knowledge path.
Encrypted Backup
For users who want recovery options, data is encrypted with a user-held key, optionally split via Shamir's Secret Sharing across trusted locations. We hold nothing.