End-to-end Encrypted Secret Sharing

About Ombra

Ombra is an end-to-end encrypted, one-time secret sharing service. It was built out of frustration with existing tools that ask you to trust their servers with your plaintext. With Ombra, the server never sees your secret; encryption happens entirely in your browser before anything is sent.

It's open source and designed to be self-hosted.

FAQ

Why would I use this?

When you share a password, API key, or private note over email or Slack, that message gets stored, backed up, indexed, and cached across multiple systems. A one-time secret link solves this: the recipient opens it once, the secret is destroyed, and there's no persistent copy floating around.

How is Ombra different from other services?

Ombra is end-to-end encrypted. Your secret is encrypted in the browser using AES-256-GCM with a key derived from your passphrase (PBKDF2-SHA256, 600k iterations) before it ever reaches the server. The server only stores opaque ciphertext, so it cannot read your secret, even in theory.

Most other services, including onetimesecret.com, encrypt on the server side. That means the plaintext passes through their infrastructure, and you're trusting them not to log or inspect it. With Ombra, that trust isn't required.

Can you read my secrets?

No. The server receives ciphertext and has no access to the passphrase or the derived encryption key. There is nothing to read.

The link alone is not enough. The recipient also needs the passphrase to decrypt the secret. You should share the link and the passphrase through separate channels (e.g., link over email, passphrase over Signal).

Even if someone intercepts both, the secret can only be viewed once. After that, it's permanently deleted.

Can I retrieve a secret after it's been viewed?

No. Secrets are deleted from the database immediately on first retrieval. There is no undo, no backup, no recovery. That's the point.

The production instance uses a Redis/Valkey backend with persistence disabled, i.e., no dump files, no append-only log on disk. Data lives only in RAM.

What if no one opens it?

Secrets have a configurable TTL, from 1 minute to 14 days. When the TTL expires, the secret is automatically deleted. You can also manually burn a secret before it's been viewed.

What about law enforcement or data requests?

After a secret is read or expires, there is nothing to hand over. The server stores ciphertext that it cannot decrypt, and deletes it on first access. No plaintext is ever stored. No access logs tie a secret to its content.

Why should I trust you?

You don't have to. Ombra is open source you can read the code, verify the cryptography, and host it yourself. The entire encryption and decryption process happens in your browser using the Web Crypto API. The server is deliberately kept ignorant. Here is the JS implementation.

Why only text?

Text is simple, predictable, and carries no hidden metadata. Files and images can contain EXIF data, embedded scripts, or other information you didn't intend to share. Keeping it text-only reduces the attack surface and keeps the tool focused.

What's the crypto?

PBKDF2 is not memory-hard, so it's weaker than Argon2id against GPU brute-forcing of weak passphrases. Unfortunately, the Web Crypto API doesn't expose Argon2id. Use a strong passphrase.