Child safety gets its own line in the terms
The terms now name the iOS and Android apps and spell out a zero-tolerance child safety rule, with a report path and a 24-hour clock. Everyone accepts again from 1 November.
Top storyTook the lead from Your GitHub orgs follow you in, now or later #1360. Everyone must accept the terms again from 1 November, and a new child safety section bans five kinds of abuse, with removal, bans, and reports within 24 hours. Held off 3 challengers since.
You open the terms page and scroll to Rules. The old one-liner about sexual content involving minors is gone, replaced by a pointer to a child safety section that now sits further down the page. It reads like a policy, not a footnote. It tells you what you can't do, how to report it, and what happens next.
Credit goes to simonhamp, who wrote the section and named the apps. It bans five things by category, from child sexual abuse material, including drawn, edited, or AI-generated images, to grooming, sextortion, sexualizing a child, and trafficking, and it defines a child as anyone under 18. It promises action within 24 hours, removal of the content, a permanent ban, and a report to authorities such as NCMEC. The Apps section now names the iOS and Android builds from NativePHP (Bifrost Technology, LLC) and sends you to the App Store and Google Play for them, while the Mac app still comes from dev-null.sh. The terms are dated 1 November 2026, and any acceptance stamped before that no longer counts.
One catch. The in-app Report button lives on commits only, and only on approved commits by other people. Its reasons are spam, harassment, harmful or private information, and something else. A profile or a message has no report button at all. For those, the section sends you to email and asks you not to send copies of any images.