Privacy policy

01Visitors and recipients

Opening a link or answering a request needs no account and sets no cookies. No tracking, no analytics, no external resources. If you switch the color theme, your choice is stored only locally in your browser (localStorage) and never sent to the server. Our application stores and logs no IP addresses. If the operator uses protective services in front of it, they are listed under "Service providers". For rate limiting only a keyed hash of the IP address lives in memory for about a minute.

02Signed-in users

Sign-in goes through the operator's identity provider. For requests the server stores your provider ID, email address and name (to show the recipient your name and to notify you). For sent links it stores your provider ID, an optional label, creation and expiry time and the status, so you see them under "Sent" and can withdraw them. It never knows the recipient or the content. A session cookie, needed for up to 8 hours, keeps you signed in.

03Secrets and replies

They are encrypted in your browser before upload. The server stores only ciphertext and cannot read it. Secrets are deleted on first view, on expiry or when reported. Afterwards only a note remains for 30 days (random ID, reason, times, your provider ID and the label), so a link can show whether it was opened, expired, reported or withdrawn and you keep the entry in your list. The note contains no content, no recipient and no IP address. Replies to requests are deleted when opened or after 7 days.

04Requests

The question, owner name and email, public key, passphrase-protected private key and timestamps are stored until the request is deleted or 30 days after it ends.

05Notifications

If enabled, an email or webhook tells the owner that a reply arrived. It never contains the content.

06Service providers

This instance uses the following service providers. They never see the content of secrets: it is encrypted in the browser, and no browser sends the key behind the # to a server.

Cloudflare (delivery and protection). The instance is delivered through Cloudflare (Cloudflare, Inc., USA) as an intermediary and as protection against attacks. Cloudflare technically processes the IP address and request data of every visitor, also when a link is opened, and may set a strictly necessary cookie. The legal basis is our legitimate interest in secure and fast operation (Art. 6(1)(f) GDPR). The transfer to the USA relies on the EU-US Data Privacy Framework and standard contractual clauses; a data processing agreement exists with Cloudflare.

CrowdSec (protection against attacks, with community). To protect against attacks the operator checks requests with CrowdSec (CrowdSec SAS, France). The IP address is processed to detect malicious patterns and block attackers. Detected attacks (the attacker's IP address, type of attack, time) are reported to the CrowdSec community; the IP addresses of normal visitors are not shared. The legal basis is our legitimate interest in the security of the service (Art. 6(1)(f) GDPR).