Konfidant is built so that our servers only ever hold ciphertext. This page explains exactly what happens to a secret, what we can and can't see, where our limits are, and how to verify the encryption yourself with our public SDK source.
The fragment-key model
The whole design rests on one property of the web: the part of a URL after # is never sent to a server. That is where the key lives.
https://download.konfidant.app/
Ours, or your own domain on Premium and Enterprise.
#
Everything after # stays in the browser. Browsers never send it to any server, including ours.
t=k9Xq…
Issued by Konfidant. It unlocks the ciphertext exactly once, then it is destroyed.
&k=Xo3f…
256 random bits created on your device. It exists only in the link; Konfidant never receives it.
Lifecycle
Your browser or our SDK creates a fresh 256-bit key and encrypts the content with AES-256-GCM. For files, the name and type are encrypted too.
Texts are held inside a single-use HashiCorp Vault token on servers in Germany. Files go straight from your device to Cloudflare R2, in the EU or the US.
Our server returns a link with only the token. Your browser or SDK appends the key to the fragment itself.
The recipient's browser sends only the token. The token is destroyed before any content is returned, and decryption happens in their browser.
File ciphertext is deleted as soon as the download ends, even if it is cancelled. Text ciphertext only ever lived inside the destroyed token.
Visibility
Open encryption format
The browser app and our SDKs use the same documented format, KNF1. The SDK source is public, so you can read every line that touches your key, and decrypt a link from the dashboard with it.
import { openShare } from '@konfidant/sdk';
// A link you made in the dashboard.
// Opening it here uses it up.
const share = await openShare(link);
console.log(share.text);Limits
No tool is a guarantee. These are the trade-offs we think you should know before you rely on us.
Web encryption runs JavaScript delivered by Konfidant. Download pages load no third-party code at all and use a strict Content Security Policy. If you need to remove that trust entirely, use our SDKs: they encrypt inside your own code.
Until it is opened, whoever has the full link can open it once. Send it directly to the recipient, not to a shared channel. If your recipient finds the link already used, someone else opened it first: rotate the secret.
We cannot read content, but we do see the account, sizes and times listed above. We need them to run the service, enforce plan limits and bill usage.
Infrastructure & compliance
The application, database and the Vault that holds single-use tokens and text shares run on Hetzner servers in Germany.
Encrypted files are stored in Cloudflare R2. Premium and Enterprise choose the EU or the US; Free uses the US.
No analytics, consent banner or sign-in code. Nonce-based Content Security Policy, no referrer, no framing, and the key is removed from the address bar after opening.
We keep only a hash and a visible prefix. Keys are scoped, rate-limited, and can be revoked at any time.
Our DPA under Art. 28 GDPR is part of every contract and lists all sub-processors and technical and organisational measures.
Server and application logs are deleted after 14 days at the latest, Cloudflare Worker logs after 7 days. The share gateway never logs tokens or content.
Full details: Data Processing Agreement and sub-processors · Privacy Policy
Responsible disclosure
Please email us the details and steps to reproduce. When testing, don't access other people's data and don't disrupt the service.
We'll walk your security team through the architecture and answer their questions.