Guide
How classified protects a one-time secret
classified is built for the moments when email, chat, or a ticketing system is too permanent: sending a password, a contract note, a client record, or a short private file. The service stores only encrypted data, and the readable content is available to the recipient once.
1. The browser encrypts first
When you create a note or file share, the plaintext stays in your browser while Web Crypto creates an encrypted payload. The server receives that payload, not the readable message. For links without a manual password, the decryption key is placed in the URL fragment, the part after #, which browsers do not send to the server in normal HTTP requests.
2. The link carries access, not the server
The share URL contains an identifier for the encrypted blob and, when applicable, the secret needed to decrypt it. Anyone handling the server-side request sees the identifier and encrypted bytes, but not the readable content. If you add a password, send it over a separate channel.
3. Opening destroys the stored copy
The recipient deliberately reveals the note or downloads the file. In that same flow, the stored encrypted blob is consumed so the same link cannot reveal the content again. This reduces long-lived copies in inboxes, chat history, support tools, and shared docs.
What this does not replace
classified is not a password manager, document management system, legal archive, or identity verification service. It is a narrow tool for temporary transfer. Keep permanent records in systems designed for retention, audit, and access control.