Terms of service

Verdict follows the releases of the technologies in its catalog and gives each one a verdict: whether it asks something of you, what breaks, and how to migrate. Release and technology pages are public and need no account. Following a technology, declaring the version you are on and the dashboard are yours alone, and those need one.

The catalog is chosen and maintained by us. There is no form to add a technology to it and no queue behind one: a technology enters when we can follow its releases properly, and it can be retired when we no longer can. A retired technology stays readable, and it stays yours if you were following it.

There is one plan, Free. It follows up to 10 technologies and costs nothing. The app never asks for payment details, and there is nothing to cancel.

Every summary is written by a language model that reads one thing: the release notes the project itself published for that release. It is given no other source, and no data about you.

A model can misread. That is why a summary is not the last word on the page: its claims carry the line of the release notes they were read from, and the page links the notes at their source. The quote is there so you can check instead of trust. When a change is expensive to get wrong, read the cited line before you act on the verdict.

You sign in with GitHub, which is asked for your public profile and your email address and nothing else: no access to any repository. You can delete the account at any time from the account page, and deleting it takes the technologies you follow and the versions you declared with it. What is held, and by whom, is in the privacy notice.

Read it, follow what you use, and leave the rest alone: no automated traffic beyond what a reader generates, no attempt to reach another account’s data, no attempt to break the app or the services behind it. An account doing any of those can be ended without notice.

The service is provided as it is. It can change, it can be unavailable, and it can stop. The summaries can be wrong, the release notes they read can themselves be wrong or incomplete, and an upgrade is still your decision and your responsibility. Nothing here is advice, and no liability is accepted for what follows from an upgrade.

These terms can change. The date at the top of this page is the day its text last changed, and it is the only record of that there is. Questions, mistakes you spot, anything else: robertozeppilli@proton.me.