Volume 01 — Issue 001
Generate an encrypted, one-time link. Send it to a client, vendor, or partner. They submit credentials through a secure form — never through a thread, never indexed, never recoverable from a sent folder.
The workflow
01
Open the portal, name a recipient, set expiration and one-time use.
02
Share the generated link by any channel. The token is single-use and signed.
03
Recipient submits credentials through an encrypted form. No account needed.
04
You're notified. View once. Delete on demand or let auto-retention purge.
Security architecture
Every credential field is encrypted with a per-payload IV before it touches the database.
Link tokens are stored as SHA-256 hashes. The plaintext never lives in the database.
Default 48-hour windows, one-time consumption, automatic status transitions.
Configurable retention purges credentials after a set number of days.
Every create, view, submit, and delete is logged with IP and user agent.
Only authorized administrators can read credential metadata. Service role decrypts on demand.