Terms
Terms at Threadly.
By commenting on a Threadly-enabled site you agree to these. By signing in to the dashboard to manage one, you also agree. Threadly is currently run as a personal-blog deployment; these terms describe that one-instance operation, not a future multi-tenant product.
Last updated: July 7, 2026.
Acceptance
By posting a comment on a blog that uses Threadly, or by signing in to the dashboard to manage one, you agree to the terms below. If you do not agree, do not post and do not sign in. We do not separately present a click-through — your use is the agreement, in the same way that walking into a library is the agreement to its posted rules.
What you can post
Threadly is for genuine discussion of the blog post you are commenting on. Spam (repetitive promotional content, affiliate links layered onto unrelated threads, SEO-building), illegal content (anything a court in the jurisdiction of the site owner has ruled unlawful), harassment of the post author or other commenters, and content that is more about evading moderation than about saying something are not welcome.
If your comment is held, you see a "pending" state in the widget. It will not appear publicly until the site owner approves it. This is normal, not a punishment; the system may hold or reject when uncertain rather than publish.
How moderation works
Every comment is run through one language-model call before storage. The model returns a verdict (approve / hold / reject) and a one-line reason; both are stored alongside the comment. A "hold" verdict sends the comment to the site owner's queue. The site owner's approve or reject is final from the user's perspective — Threadly does not arbitrate disputes over a single comment.
We do not guarantee any specific moderation accuracy. The system is meant to be a sensible default for small personal blogs where the operator is reading the queue. For higher-stakes settings the site owner reads the queue more carefully, not less.
Content and ownership
You retain authorship of what you write. By posting on a Threadly-enabled site you give that site a non-exclusive license to display the comment on the same site (and only that site), and you give Threadly a non-exclusive license to store and serve it for that purpose. The comment is not licensed for republication elsewhere, redistribution, or use in model training by Threadly.
If a site owner decides to remove your comment, they can do so from their dashboard (or by deleting the whole site, which cascades to all comments). They are responsible for telling you they did, not Threadly.
Site owner responsibilities
Enabling Threadly does not transfer responsibility for the comments on your site to us. You are the publisher of record. You are responsible for the moderation calls you make on top of ours, for telling your readers what kind of discussion you want, and for being the human the moderation system defers to on the queue.
If a reader asks for their comment to be removed from your blog and you agree, that is between you and them. We will not second-guess; we will only mirror the data state.
Our role: hosting service, not publisher
Threadly is a hosting service for comments written by third parties (commenters) on third-party sites (your blog). We are not the publisher of any comment, anywhere. The site owner is the publisher of record for the comments on their site — including the publication choices the owner makes and the moderation policy the owner describes to readers.
We make no warranty as to the content of any comment and we do not pre-screen comments before they reach the site owner's queue. Because comments are written by third parties and hosted on third-party sites, the site owner is responsible for takedown, restoration, and content-policy decisions. If you have a complaint about a comment on a Threadly-enabled site, the first person to contact is the site owner. We will respond promptly to a court order or a fully-credentialed DMCA notice served on us, and only to those.
No warranty, updates, and contact
Threadly is provided as-is, with no uptime SLA, no specific availability window, and no guarantee of uninterrupted moderation in v0. We do our best, the operator is the founder, and the system is built around the assumption that the queue will be read. If a comment of yours is held or you cannot sign in, the site owner is the first person to ask, not us.
Material changes to these terms will appear here with a new "Last updated" date. Continued use after a change is acceptance of the new version.