End-to-End Encrypted

We can't read your data.
Even if we wanted to.

Our "Zero-Knowledge" architecture means encryption happens on your device, not our servers. Type below to simulate exactly what happens when you save a memory.

Your Device
Client Side

This password generates the encryption key. It is never sent to Huddle.

Huddle Database
Public Cloud

Without your device's key, this JSON is mathematical garbage.

Live Encryption via WebCrypto API (PBKDF2 + AES-GCM)

The Key is Derived Locally

We use PBKDF2 with 210,000 iterations to turn your password into a cryptographic key. This computationally expensive process happens 100% on your CPU, ensuring we never see your actual password.

AES-GCM Encryption

We use industry-standard AES-GCM (Galois/Counter Mode). This ensures both confidentiality (data can't be read) and integrity (data hasn't been tampered with).

Zero Knowledge

As shown in the JSON output, Huddle only stores the `ciphertext` and the `salt`. Without the password (which lives in your head), the data cannot be reversed by our engineers, hackers, or governments.

Privacy shouldn't be a mystery.

Start Your Private Space