Privacy policy
Last updated: April 26, 2026
Summary
Unsaid is built to be anonymous. There are no user accounts, no first-party marketing cookies, and we do not sell your personal information. This page explains what the service and its infrastructure still need to process so the site can work, stay available, and resist abuse.
Content you see and share
Truths you publish and read are stored and displayed for others to see in the app. We keep what is required to run the feed, including the text of each post, its language, identifiers needed for our database, and a timestamp. Posts are public. Do not share secrets or data you are not allowed to make public.
Abuse protection and short-lived technical data
To limit spam, we use a CAPTCHA (Cloudflare Turnstile) and a daily per-IP posting limit. For the limit, a short-lived key tied to your IP may be written to storage at the network edge, with a maximum retention on the order of a day, so a counter can be enforced. The CAPTCHA check is performed when you post; the token is not stored on our server as part of the post. Traffic may pass through the operator’s network (for example Cloudflare) and can be subject to that provider’s logging and security practices as described in their own policies.
No sign-in, no analytics profile
We do not maintain accounts or a profile of you. We do not use your data for targeted advertising. Your browser and device may still send information that is normal for any website, such as IP address and user-agent; our goal is to use the minimum that service providers and the platform need to deliver and protect the app.
Automated translation
If enabled by the operator, Unsaid may generate a translated version of a public post to show it in another language. Translation is derived only from the public post text and may be sent to the configured translation provider.
Your choices
You can choose not to use the site, not to post, or to use a browser and network setup that you trust. Do not use Unsaid if the processing described here is not acceptable to you.
Contact
The project is open on GitHub . You can reach the maintainer via the author site linked in the footer.
Changes
This policy may be updated from time to time. The “Last updated” line at the top of this page will be revised when material changes are made. Your continued use of the site after changes are posted means you understand the new description.