Privacy policy

Short version: we designed this service so that there is almost nothing about you for us to have.

What we store

• The encrypted secret (an AES-256-GCM blob), its creation and expiry timestamps, and whether a passphrase was set. For passphrase-protected secrets we also store a salted, heavily-stretched hash used only to count wrong attempts — it cannot reconstruct the passphrase or decrypt anything. We never hold the decryption key: it exists only in the link, so we cannot read your secrets — by construction, not by promise.
• Nothing else in the database. No accounts, no emails, no IP addresses, no cookies, no analytics, no third-party requests.

What we process transiently

• Your IP address, in memory only, to rate-limit secret creation. It is never written to the database.
• Standard web-server logs (IP, path, timestamp) kept briefly for security and abuse response. Secret links carry the key after the #, which browsers never send — so keys cannot appear in logs. API requests carry keys in request bodies, which are not logged.
• Nothing else: every secret is encrypted and decrypted in your browser, so the server only ever handles encrypted blobs — it never sees plaintext or keys.

Retention

Secrets are deleted on first read, and otherwise self-destruct after 1 day by default — senders may pick any date up to a hard maximum of 30 days. An automated in-process sweep purges expired secrets hourly. Deleted means deleted: there are no backups of secret content.

Your rights & contact

Data controller: CYNDERLAB DIGITAL SL, Vic (Barcelona), Spain. For any privacy request (GDPR arts. 15–22) write to [email protected]. Given the design, in most cases the honest answer will be: we hold no data about you.