Privacy
What's public, and when
When you seal a message, the title and your optional name become public immediately — they're what make the board interesting to browse. The message itself stays genuinely unreadable — not hidden by our design, not sent to your browser at all — until the unseal date you chose, decided by our server's own clock. Once that date arrives, the message becomes public too, on the same page anyone can already see the title and countdown on.
Moderation
Every seal — title, name, and message — is checked by an AI moderation pass before it publishes, against a rubric that excludes violence or threats, sexual content, slurs or harassment, targeting or identifying private individuals, substances, theology or politics, and illegal instruction. If that check fails or can't be completed for any reason, the seal is rejected and nothing is published — we would rather show you an honest "try again" than publish something unvetted. The text you submit is sent to OpenRouter to run this check, the same way the sibling product on this domain sends text to AI models — see "What we send" below.
What we send, and to whom
The title, message, and optional name you submit are sent from your browser to our server, which forwards that same text to OpenRouter to run the moderation check above. We do not send your IP address, browser identifiers, or any other personal data to OpenRouter — only the text you typed.
What we store
We store the full sealed message (title, name, message body, and the unseal date) so it can be shown once due. We also keep an anonymous daily counter of how many seals came from your connection, used only to enforce a 3-per-day limit and stop abuse. Your IP address is one-way hashed before being used as part of that counter's key; we do not store your raw IP address, and the hash is not reversible back to your IP.
Bot protection (Cloudflare Turnstile)
The seal form uses Cloudflare Turnstile to confirm you're a real visitor rather than an automated script. It runs quietly in your browser and may send some technical signals about your browser/device to Cloudflare for that purpose — never your title, message, or name. If it can't load (for example, an ad blocker), the form still submits normally, but our server can't tell that apart from a bot and will ask you to refresh and try again rather than let the seal through unverified.
Accounts, cookies, tracking
There are no accounts and nothing to sign up for. This site does not set any cookies. We send anonymous, aggregate usage events (e.g. "a seal was created", "a share button was clicked") to our own server so we can see whether the tool is useful — these events do not include your title, message, name, IP address, or any identifier tied to you.
Sale of data
We do not sell any data, ever.
Takedowns
If a sealed message shouldn't be public — even one our moderation approved — contact us and we will remove it. See the README in this project's repository for the exact removal process we use.