What the application stores.
We store encrypted note content, its salt and nonces, an encrypted unlock proof, hashed access and management capabilities, a random public ID, timestamps, view mode, and note status. The application does not request your name, email address, or an account.
Plaintext notes, raw passwords, and derived encryption keys are not sent to our API. The management token is present in the private management link. Older sharing links also contain fragment key material. New sharing links contain only the public 5-digit ID. Links may remain in browser history or messages where you share them.
When you share a file.
Encrypted file bytes are stored in private Supabase Storage. The original filename and file format are inside an encrypted manifest. We also store an opaque object path, encrypted byte count and a short-lived hashed upload capability. Direct uploads reveal connection metadata to the storage provider. Neither plaintext files nor filenames are sent to our API.
Expiry, one-time consumption and manual deletion immediately block further retrievals and clear encryption material. A durable cleanup queue retries removal of encrypted objects. Upload grants last two hours; deletion tombstones are retained through that period so any late re-upload is inaccessible and removed again. Upload reservations expire after 15 minutes. Actual physical removal depends on storage availability and the configured cleanup schedule.
Status without recipient profiling.
The creator can see whether a note has been successfully retrieved and its first-viewed timestamp. We do not expose recipient identity, IP address, location, or device details in the management page. We do not maintain a per-recipient reading history.
Operational data.
Rate limiting uses short-lived HMAC-hashed network-address buckets, not raw addresses in the application database. Hosting and infrastructure providers may process IP addresses, request paths, timestamps, and other connection metadata in their own logs. Secret IDs may appear in request paths; URL fragments are not sent in HTTP requests.
The application includes no analytics or advertising trackers. It stores only your light or dark theme preference in local storage. Encrypted notes are not saved in browser local storage.
Temporary chat rooms.
Chat messages and member display names are encrypted before sending. Room records also contain the creation/expiry time, member limit, message order, membership identifiers and hashed access credentials. They do not contain plaintext passwords, names or messages.
Your browser keeps a random room membership credential in session storage for reconnection, but never stores the room password, AES key or plaintext messages there. Display names are chosen by participants and are not verified identities. Rooms are excluded from search indexing. Expiry or creator deletion removes room ciphertext and memberships; a status record can remain for up to 30 days. Provider backups follow their retention settings.
Room controls, reactions and online status.
Reaction emoji values are encrypted in your browser. We store encrypted activity envelopes, message/member identifiers and event order. Replaced or removed reaction envelopes can remain until room expiry. Creator message deletion removes the message envelope and its encrypted reaction history, leaving an ordering placeholder. It cannot erase copies already saved or held by offline devices.
Room members can see an approximate Online/Away state. The app stores the latest membership heartbeat, updates it at most every 15 seconds, and treats a recent heartbeat as online for 45 seconds. No exact last-seen timestamp or network address is shown to participants. Locking a room pauses new joins; it does not remove existing members.
Sharing QR codes are generated locally and contain only a public secret or room link. They do not include passwords or private management links, and no external QR service receives the link.
Member removal and retired reporting.
The creator can revoke a guest membership. We retain its removed timestamp and existing encrypted author records until room expiry/end. Removal locks new joins automatically and prevents further access through that membership, while saved copies and the shared encryption key cannot be recalled. There are no verified identities: if new joins are unlocked, a password holder may enroll under a fresh identity.
The reporting interface and submission feature have been retired. Previously submitted reports remain private and are deleted under their original 30-day retention policy. New reports are no longer collected.
Optional UPI support.
The support page shows a public receiving UPI ID. Copy UPI ID writes only that ID to your clipboard; you paste it into your UPI app and choose the amount there. When available, the owner's original receiving QR image is displayed unchanged. Tapping it opens the image in a new tab. This website does not generate payment QR codes or open payment-app links. Secret text, passwords, and sharing or management links are never included in payment details.
Your bank and UPI provider handle payment information. The recipient may receive payer and transaction details through their bank. This website does not collect your UPI PIN, store donation records, or verify whether a payment succeeded. Support is voluntary and is not required to create or open a note.
Retention and deletion.
Every note expires within 7 days. Expired and manually deleted content becomes inaccessible immediately through the API, and its encrypted content and associated encryption material are cleared from active storage. The scheduled cleanup job also clears expired material automatically.
Minimal status records and hashed management capabilities remain for up to 30 days after the scheduled expiration. Rate-limit buckets are cleared after their window. Provider backups and logs follow the operator’s configured retention policies and may outlast active records.
Your choices and control.
Use the management link to delete a note early. Without an account or retained identifying information, we cannot reliably locate notes by a person’s identity or recover lost passwords and links. Never post your management link publicly.
Privacy depends on the devices and channels you use. A recipient can keep a screenshot or copy. Avoid using this service for data that requires contractual, regulatory, or audited handling guarantees.
Service providers and operator.
The intended deployment uses Vercel for application hosting and Supabase for PostgreSQL and private file storage. Their processing, regional settings, backup retention, and terms also apply to a deployed service.
This source distribution does not identify a legal service operator or privacy contact. Before running a public service, the operator must publish their legal identity, contact details, applicable rights process, and actual provider retention settings here.