Security architecture

We can't read what you share. Here's how to check.

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.

  • AES-256-GCM on your device
  • Key only in the link
  • Hosted in Germany
  • Public SDK source

The fragment-key model

Anatomy of a share link

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/#t=k9Xq…&k=Xo3f…

https://download.konfidant.app/

Download host

Ours, or your own domain on Premium and Enterprise.

#

Fragment

Everything after # stays in the browser. Browsers never send it to any server, including ours.

t=k9Xq…

Single-use token

Issued by Konfidant. It unlocks the ciphertext exactly once, then it is destroyed.

&k=Xo3f…

Decryption key

256 random bits created on your device. It exists only in the link; Konfidant never receives it.

Lifecycle

What happens to a secret, step by step

  1. 01Encrypted on your device

    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.

  2. 02Only ciphertext is uploaded

    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.

  3. 03The key is added to the link locally

    Our server returns a link with only the token. Your browser or SDK appends the key to the fragment itself.

  4. 04Opened once, decrypted by the recipient

    The recipient's browser sends only the token. The token is destroyed before any content is returned, and decryption happens in their browser.

  5. 05Burned

    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

What we can and can't see

Konfidant can never see

  • The content of your texts and files
  • The decryption key
  • File names and file types
  • The content after a share is opened: no copy of it is left

Konfidant can see

  • Which account created shares, and when (usage records, plus audit logs if your organization turns them on)
  • The size of the encrypted content
  • When the share was opened, if your organization uses verified burn (Enterprise)
  • IP address, browser and requested URL in server logs, deleted after 14 days at the latest. The URL never includes the fragment, so logs never contain keys

When is a share destroyed?

First open
The single-use token is destroyed before any content is returned.
File after opening
The encrypted file is deleted when the download ends, also if it is cancelled.
Text after opening
It existed only inside the token, which opening destroys.
Never opened
The token expires at the time you chose; storage lifecycle rules remove the file.
Upload never finished
The upload slot expires after 2 hours; lifecycle rules remove the file.

Open encryption format

Verify it yourself

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.

  • AES-256-GCM with a new 32-byte key per share from a cryptographically secure random generator
  • Chunked STREAM construction: every chunk has its own nonce, so chunks cannot be reordered, duplicated or cut off unnoticed
  • The header is authenticated with every chunk; file name and type are inside the encrypted data
  • Any tampering, truncation or wrong key makes decryption fail completely, never partially
Read the KNF1 format
  1. 1Create a share in the dashboard and copy the link.
  2. 2Open your browser’s network tab: the upload contains only ciphertext, and opening sends only the token.
  3. 3Or decrypt the link with the public SDK:
$ npm install @konfidant/sdk
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

What encryption doesn't solve

No tool is a guarantee. These are the trade-offs we think you should know before you rely on us.

In the browser, you trust the code we serve

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.

The link is the secret

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.

Metadata is visible to us

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

Where your data lives, and who processes it

Hosted in Germany

The application, database and the Vault that holds single-use tokens and text shares run on Hetzner servers in Germany.

EU or US file storage

Encrypted files are stored in Cloudflare R2. Premium and Enterprise choose the EU or the US; Free uses the US.

Hardened download pages

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.

API keys stored as hashes

We keep only a hash and a visible prefix. Keys are scoped, rate-limited, and can be revoked at any time.

GDPR Data Processing Agreement

Our DPA under Art. 28 GDPR is part of every contract and lists all sub-processors and technical and organisational measures.

Short log retention

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

Found a vulnerability?

Please email us the details and steps to reproduce. When testing, don't access other people's data and don't disrupt the service.

hello@konfidant.app

Have a security review to pass?

We'll walk your security team through the architecture and answer their questions.