Blog
How it actually works, in plain language.
Zero-knowledge is a claim anyone can print on a landing page. These posts explain the mechanics behind ours — what runs in your browser, what reaches our servers, and how you can check the difference yourself instead of taking our word for it.
Why we judge businesses by how they deliver
Long before anyone reads the first page of a contract, they have formed an opinion about the organisation that sent it. Why the way sensitive information arrives became part of the message — and the design decision that follows from it.
What “zero-knowledge” actually means — and what it doesn’t
The phrase gets attached to products that still hold a copy of your key. Here is the concrete test we hold ourselves to: what a full dump of our database would reveal to an attacker who also owns every disk in the cluster.
How your files are encrypted before they leave the browser
A walk through the upload pipeline: deriving keys with Argon2id, sealing content in 8 MiB XSalsa20-Poly1305 segments, and why the encrypted bytes travel straight to a storage node instead of through our API.
Why we publish a tamper-evident audit log
Encryption stops us from reading your files. It does nothing to stop us from quietly rewriting the record of who touched them. So we chained the log with BLAKE3, anchored the roots to Bitcoin, and shipped the verifier as a separate program.
What GCN.ONE is, and why we built it
The no-jargon introduction, written for the people who sign the contracts: what the service does, what a business would use it for, and the one question — who holds the keys? — that separates it from ordinary cloud storage.
Send an encrypted file without creating an account. Nothing to install.
Send a file