Private delivery
Share passwords, tokens, access codes, and confidential notes through a flow built specifically for sensitive data.
The password is never sent to the server.
Use the QR code only if the recipient can open the link immediately.
Key Features
Secure sharing for information that should not linger.
Ad Nihilum is designed for sensitive exchanges that require more control, less exposure, and a cleaner path from sender to recipient.
Ephemeral by design
Secrets disappear after the first successful retrieval or when the server-side lifetime runs out.
Controlled access
Add an optional password layer so the link alone is not enough to reveal the message.
Reduced exposure across everyday channels
Keep sensitive information out of long email threads, chat histories, shared docs, and screenshots that are difficult to control later.
Fast, low-friction sharing
Create a protected share in seconds and move information where it needs to go without breaking the workflow around it.
Built for real operational use
Useful for administrators, developers, support staff, and anyone who handles sensitive information as part of daily work.
Why it stands out
- Client-side encryption keeps the decryption key out of the server.
- Single-use retrieval and expiration reduce unnecessary persistence.
- Simple enough for quick sharing, serious enough for confidential data.
Less exposure
A cleaner alternative to sending secrets through channels that were never designed for them.
How It Works
Three steps from secret creation to disappearance.
The workflow is built to stay short: encrypt in the browser, share the link, then let the stored blob vanish after use.
Compose and encrypt locally
Write the secret here. The browser encrypts it before upload, and the key stays in the link fragment instead of going to the server.
Share the generated link
Send the resulting link to the recipient. If needed, share the optional password through a different channel.
Open once, then lose access
When the recipient opens the full link, the secret is retrieved, decrypted in the browser, and removed from the server after the first successful fetch.
Operational note
The server stores encrypted blobs in RAM with a fixed time limit, so anything not opened still ages out instead of lingering indefinitely.