Ziro
Ziro is a zero-knowledge, temporary text-sharing application that burns after reading. The message is encrypted using AES‑GCM on the browser side before being sent to the server. The server only saves ciphertext and IV, and does not have any plaintext or keys. The decryption key carried by the access link is stored in the Fragment (#) of the URL and is never uploaded. Supports automatic destruction of first visits and deletion of unread TTL expiration, and includes basic crawler/robot access protection.
You need to go to the Upstash Console (https://console.upstash.com/) to create a Redis database to record the UPSTASH_REDIS_REST_URL and UPSTASH_REDIS_REST_TOKEN. See the attached figure. Set it in the configuration wizard to enter the application Usage: Enter the content, select the expiration time, select whether to burn it after reading, create a link, copy and paste the link to see the information. - Zero-knowledge architecture: The key only exists in the browser's URL Fragment (#), and the server cannot "see" the plaintext throughout the process. - Burn after reading: After the link is successfully accessed for the first time, the ciphertext record is deleted immediately (optional). - TTL expiration deletion: Unread content can be configured to automatically expire in 1 hour, 1 day, 1 week, and 30 days. - Basic anti-crawling: Identify common crawlers based on user-agent and other characteristics to avoid accidental triggering and burning after reading. - Lightweight technology stack: Next.js16 + TypeScript + Tailwind, the server uses Upstash Redis to store ciphertext and IV.
