Fragment sealed
The encrypted capsule lives after # in the URL, so the destination is not part of the normal HTTP request to Cipher.
Turn a destination into a classified capsule. Add clearance, a mission timer and a one-browser burn sequence — without giving Cipher a destination database.
CREATE TRANSMISSION ↓A sealed link will materialize here. The destination stays out of server storage.
Cipher is deliberately dramatic at the interface layer and deliberately boring at the cryptographic layer: standard Web Crypto, explicit limits, no proprietary protocol.
The encrypted capsule lives after # in the URL, so the destination is not part of the normal HTTP request to Cipher.
Add an access code and the decryption key is derived in the recipient browser instead of travelling with the link.
Cipher does not need a short-link table, account, analytics pipeline or destination log to route a capsule.
Operational note. Expiry and burn are recipient-side controls, not remote revocation or DRM. A determined recipient who possesses the capsule and required code can modify client software. Use Cipher for controlled presentation and link privacy, not as a substitute for authorization on the destination itself.