Encrypted before it leaves your browser.
Note content is encrypted using the Web Crypto API and AES-256-GCM authenticated encryption. A unique 128-bit salt is generated for every note. The note and the unlock proof use independent random 96-bit nonces and distinct authenticated context strings.
Your password is processed with PBKDF2-SHA-256 at 600,000 iterations. HKDF-SHA-256 derives a non-extractable AES key with a version-specific context. New secrets use your password and a random public salt, so the sharing link needs only the 5-digit ID. Passwords, plaintext notes, and derived encryption keys are never sent to the API.
A short link. A strong password.
New sharing links contain only the 5-digit ID. The ID identifies the secret; it is not a password. Your password is now the only secret protecting the encryption. Use the Generate strong password option for a random 15-character password. A 3-character password is permitted but offers weak protection.
The password never appears in the link. Share it separately. Older version-one secrets still need their original #k= fragment as well as the password; those existing links remain supported. Our pages send no referrer and load no third-party analytics or scripts.
A proof, not your password.
The browser encrypts a random unlock capability alongside the note. The server stores that encrypted envelope and a SHA-256 hash of the capability, not a password hash. A correct password lets the recipient decrypt the capability locally. Older secrets also require their original link fragment. The server verifies the capability hash before releasing the encrypted note.
The management link uses a different random 256-bit capability. Its hash is stored separately. It grants status and deletion access without granting decryption.
One-time viewing and expiration.
A database row lock checks authorization and state, records the first retrieval, and clears a one-time note’s encrypted content in one transaction. Expiration is enforced during every access, independently of the scheduled cleanup job. Deletion removes content, salts, nonces, and encrypted unlock material from active storage.
Status records contain no note content or recipient identity. They are retained for up to 30 days after expiration and then removed by cleanup. Logical deletion does not erase existing provider backups, snapshots, browser memory, screenshots, or copies recipients make.
Safer by default.
Production requires HTTPS. Server-only database access, row-level security, validated request bodies, same-origin mutation checks, nonce-based Content Security Policy, no-store responses, and distributed database rate limits protect the flow. Notes render as text, with no HTML execution.
Password challenge and unlock endpoints have shared limits across server instances, including per-address, per-secret and short burst budgets. ID rotation does not bypass the per-address password-attempt budget. HTTP 429 responses include a retry time.
For new ID-only links, anyone who obtains the encrypted proof can attempt password guesses offline. Rate limits cannot stop those computations. Short or common passwords are weak, even with PBKDF2. We do not claim zero-knowledge or independently audited end-to-end protection. Prefer a random 15-character password and a short expiry.
Temporary encrypted chat rooms.
Room messages and display names are encrypted in the browser using AES-256-GCM. A separate PBKDF2/HKDF key context keeps room encryption separate from notes and files. The server stores ciphertext and hashed access tokens, and checks membership before every message read or write.
Rooms last 30 minutes to 7 days and allow up to 10 memberships, including the creator. Passwords are verified locally. Use a strong random 15-character password: someone who obtains the encrypted proof can try password guesses offline, outside server rate limits.
Members share a room key, can read the available room history, and may retain messages they have seen. Display names are not verified identities. This is not the WhatsApp protocol and does not provide forward secrecy. Ending or expiring a room blocks future retrieval and removes its encrypted messages, membership records and stored encryption material. Saved copies cannot be recalled.
Only a random membership credential is kept in session storage to reconnect after a reload; passwords, encryption keys and decrypted chat content are not saved there. The creator’s credential controls End room. Keep the creator’s tab available until you are done.
Files stay private too.
One file up to 10 MB is encrypted with AES-256-GCM before being uploaded directly to private Supabase Storage. The filename, format, size and file nonce are in a separately encrypted manifest. File bytes, manifest and unlock proof use distinct authenticated contexts and independent nonces. The server sees the encrypted size and an opaque object path.
Recipients receive an authorized encrypted stream, never a reusable storage download link. A database transaction enforces one-time retrieval. An interrupted transfer may still consume the secret. Expiry or deletion immediately prevents new retrievals and clears the stored encryption material; physical encrypted-object removal is retried by scheduled cleanup. An already authorized transfer or downloaded copy cannot be recalled.
All file types are accepted within the 10 MB limit. The server cannot scan encrypted files for malware. Files are offered as downloads and are never previewed inside the website. Only open files from trusted senders.
Room controls and safer sharing.
The creator’s individual session authorizes locking a room and deleting its messages. Guests cannot grant themselves creator rights. Locking pauses new joins while current members can resume. Deleting a message removes its active ciphertext and reactions and sends a deletion update to connected members; saved copies and offline devices cannot be recalled.
Reactions use browser AES-GCM encryption with the room, member, message and event bound as authenticated context. Online/Away status is approximate metadata shared only with members, using existing chat updates. Sharing QR codes are created on your device and exclude passwords and management links.
Creator member removal revokes that membership and automatically locks new joins. Other members keep access. Removal does not rotate the shared encryption key: a person with the password can enroll under a fresh identity if joins are unlocked again. Start a new room/password when permanent exclusion is needed.
Trust, and the limits of browser encryption.
This implementation is designed so the normal server data flow never receives a decryption key or plaintext note. It has not been independently security audited. We do not claim protection against a malicious site operator, compromised JavaScript delivery, compromised devices, browser extensions, or a recipient who saves a copy.
For high-risk secrets, use a reviewed tool that matches your threat model. Operators should review the included SECURITY.md before launch and configure their hosting logs and backup retention responsibly.
Read our Privacy Policy for data retention details.