Most security pages stop at “military-grade encryption”. Here is what actually happens to a secret you send through Host Dada Secrets, including the parts that some readers will want to weigh up for themselves. The core idea is simple: the key is part of the link, and we don’t keep the link.
What happens when you create a secret
- It reaches the server over HTTPS. Your browser doesn’t encrypt the secret itself. It sends it through the same protected connection as the rest of the site.
- The server generates a random token. That’s 32 bytes from a cryptographically secure random generator, and it becomes the last part of your link.
- A key is derived from the token. HKDF-SHA256 combines the token with a separate random 16-byte salt to produce a 256-bit key.
- The secret is encrypted on arrival. It’s sealed with AES-256-GCM before being written to the database. GCM also detects tampering, so altered data fails rather than decrypting to something misleading.
- The token is handed to you and forgotten. It’s returned once, inside the link, and isn’t saved. That’s why the link can’t be shown a second time.
What’s kept, and what isn’t
| Stored | Never stored |
|---|---|
| The encrypted secret and its salt, until it’s opened or expires | The readable secret |
| A keyed hash of the token, used to find the record | The token, and therefore the link |
| For a file, its encrypted contents and encrypted filename, until it’s opened or expires | The encryption key |
Your dashboard also needs a record that the secret existed, so we keep some details alongside it that are not encrypted: your name, your private label, the times it was created, opened or revoked, its size and, if we emailed the link for you, the recipient’s address. That’s why you shouldn’t put anything sensitive in a label. Our privacy page says how long those details are kept.
The hash that finds the record is an HMAC keyed with a secret held outside the database. A plain hash would let anyone with a copy of the database check guesses offline. This way, the copy alone isn’t enough to test even one.
What happens when it’s opened
When the recipient presses the button, their browser posts the token back to the server, which finds the record and removes the encrypted data in one atomic database operation. Only the request that wins that operation gets the data, so a link can’t be read twice, even by two people clicking at the same moment. The server then derives the key from the token, decrypts the secret and returns it. The secret is removed before decryption, on purpose. Doing it the other way round would leave a brief window for a second read.
Files work the same way, in chunks
Files also get a key derived from the link, separate from the one a text secret would use. They’re encrypted as they arrive, in sealed chunks of 1 MiB, before being written to disk. Each chunk is verified before any of it is released, so a tampered file fails instead of delivering altered content. The filename is encrypted too, so even your own dashboard can’t display it.
What this does protect against
- A stolen database or backup. Without the link, the encrypted data can’t be decrypted. A backup taken before a secret was opened holds only that encrypted data.
- Link replay. Once opened, the data is gone and the link is dead, so one found later in an inbox opens nothing.
- Forgotten secrets. Anything never opened stops working at expiry and is removed automatically.
What it doesn’t protect against
- Someone in control of the running server. Encryption happens on the server, not in your browser, so this is not end-to-end encryption. An attacker able to tamper with the live application could capture secrets as they arrive or leave. Stored secrets stay safe, but new ones passing through wouldn’t. If your threat model rules that out, encrypt the content yourself first and share the key another way.
- Anyone holding the link. The link is the key. Whoever has it first can read the secret. You’d see that it had been opened, but not by whom.
- A compromised device at either end. Malware on a computer can read what’s on its screen, however well the secret travelled.
- The recipient. Once read, a secret is in that person’s hands.
No tool removes every risk. What this one aims to do is make sure a secret doesn’t linger, and that a leak of our stored data doesn’t become a leak of yours. For everyday use, see how to share a password securely.