Docracy tracked daily ToS changes as diffs so users skipped rereading 27-page contracts

In February 2013 Docracy's Terms of Service Tracker was posted to Hacker News. The problem it addressed was familiar: consumer agreements run dozens of pages, change without notice, and bind users who rarely reread them - as one commenter put it, the alternative to the tracker was to 'dig through 27 pages and see what possibly changed' in iTunes' terms.

Docracy's move was to treat legal text like code. Employees said the service checked each tracked ToS once a day, kept its revisions, and published before-and-after diffs of what changed; one argued that people implicitly bound by a company's terms should be able to keep a copy of them, and that no tracked company had asked Docracy to stop. The same versioning and diff machinery powered Docracy's own document and e-signing services, so the free public tracker also demonstrated the platform.

Watching the text itself caught what reading announcements never would. The tracker's history showed Skype changing its terms in mid-January while the page claimed 'Last updated: February 2013,' then reverting days later; Amazon's tracked ToS already carried new Elastic Transcoder terms before that service was announced, which commenters said journalists could mine for scoops. The discussion also raised a design question the tracker had to answer: whether reproducing long passages of another company's terms was fair use.

Version legal text and publish the diff: readers and journalists care what changed, not the whole document, and labels like 'last updated' lie

A diff spends the reader's attention where the risk is: what changed appears in seconds, while finding the same change in a 27-page reread takes hours.

Monitoring actual text beats trusting metadata: daily polling caught Skype's backdated 'last updated' label and its silent revert, evidence no announcement would supply.

The public-service framing held up: Docracy argued that anyone bound by the terms deserves a retrievable copy, and no tracked company had asked it to stop.

It doubled as a working demo: the same diff and versioning engine powered Docracy's negotiation and e-signing services, so the free tracker showed what the platform could do.

When an audience will never reread the whole agreement, publish the change - and archive the real text, because 'last updated' stamps and announcements cannot be trusted

The February 2013 thread drew 200 points and 49 comments, with readers praising the service, requesting per-document subscription feeds and ways to flag alarming diffs, and debating the copyright of reproduced terms. The tracker did not carry the startup on its own: the page eventually became a notice that the Docracy product was no longer available, steering customers to eversign for e-signing with a free trial. What the case leaves behind is the pattern - publish the change, not the document - with the thread itself as evidence that readers and journalists wanted exactly that.