# What Changed in the META ToS (July 18, 2024) **URL:** \ **Category:** Site feedback\ **Created:** [July 19, 2024, 8:33am UTC](https://meta.discourse.org/t/what-changed-in-the-meta-tos-july-18-2024/317201 "2024-07-19T08:33:53Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![hellekin](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/hellekin/32/51636_2.png) [@hellekin](https://meta.discourse.org/u/hellekin)\ **Post date:** [July 19, 2024, 8:33am UTC](https://meta.discourse.org/t/what-changed-in-the-meta-tos-july-18-2024/317201/1 "2024-07-19T08:33:53Z")
It would be useful to link the mandatory banner to accept new ToS to the changes, so it’s easier to review. Reading the full ToS does not help informing what has actually changed, and while you have not accepted the changes you cannot participate anymore, so it’s a bit problematic. Moreover, there should be a place where one can feedback on the changes, just in case one disagrees and would like further explanations. Right now it feels like you’ve been kicked out of the forum! ---
**Author:** ![merefield](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/merefield/32/176214_2.png) [@merefield](https://meta.discourse.org/u/merefield)\ **Post date:** [July 19, 2024, 8:36am UTC](https://meta.discourse.org/t/what-changed-in-the-meta-tos-july-18-2024/317201/2 "2024-07-19T08:36:17Z")
Seconded. It would be nice to know the delta. Maybe I missed an announcement … ---
**Author:** ![Jagster](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jagster/32/192154_2.png) [@Jagster](https://meta.discourse.org/u/Jagster)\ **Post date:** [July 19, 2024, 9:21am UTC](https://meta.discourse.org/t/what-changed-in-the-meta-tos-july-18-2024/317201/3 "2024-07-19T09:21:43Z")
I got feeling that someone came to idea that consent of users is legal need and there should be timestamp for that. And then other someone remembered that hey we have that neat option to use forced user field and now we are here. Sorry to say this at loud but I keep this as an example of reactive behaviour. ---
**Author:** ![NateDhaliwal](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/natedhaliwal/32/313494_2.png) [@NateDhaliwal](https://meta.discourse.org/u/NateDhaliwal)\ **Post date:** [July 19, 2024, 1:44pm UTC](https://meta.discourse.org/t/what-changed-in-the-meta-tos-july-18-2024/317201/4 "2024-07-19T13:44:22Z")
I agree with this. Also, the user can just check the box without actually clicking on the link. This kinda defeats the purpose. As for this issue, perhaps there could be a `What's changed` part above the checkbox? Additionally, is it me, or is there 2 spaces before ‘terms’? ![image](https://global.discourse-cdn.com/meta/original/4X/9/c/5/9c5ec3c9e7b8b6963cb0218a03e96c9f28236ef7.png) ---
**Author:** ![Moin](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/moin/32/554653_2.png) [@Moin](https://meta.discourse.org/u/Moin)\ **Post date:** [July 19, 2024, 1:57pm UTC](https://meta.discourse.org/t/what-changed-in-the-meta-tos-july-18-2024/317201/5 "2024-07-19T13:57:50Z")
> [@NateDhaliwal](#): > > Additionally, is it me, or is there 2 spaces before ‘terms’? This happens around a lot of links next to a checkbox, for example, in the flag modal or the admin site settings. ![Screenshot_20240719_155426_Chrome](https://global.discourse-cdn.com/meta/original/4X/9/3/3/9332019cd52358faef52cc36fe8207839ae4079d.jpeg) ![Screenshot_20240719_155554_Chrome](https://global.discourse-cdn.com/meta/original/4X/6/d/4/6d4468a838242aca471eadb4ab8a11cb0092d235.jpeg) ---
**Author:** ![awesomerobot](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/awesomerobot/32/142900_2.png) [@awesomerobot](https://meta.discourse.org/u/awesomerobot)\ **Post date:** [July 19, 2024, 3:02pm UTC](https://meta.discourse.org/t/what-changed-in-the-meta-tos-july-18-2024/317201/6 "2024-07-19T15:02:46Z")
> [@NateDhaliwal](#): > > the user can just check the box without actually clicking on the link. This kinda defeats the purpose. The checkbox says “I have reviewed and agree” — so not reading the terms and agreeing is a risk you’re taking on personally. Ultimately no one can be forced to read anything so there’s not much point in requiring a link click. > [@merefield](#): > > It would be nice to know the delta. The diff between the April and July terms is very minor… this is all at the end under the “Changes” header: > The company last updated these terms on July 18, 2024, and may update these terms again. The company will post all updates to the forum. > > ~~The~~~~ company ~~~~last~~~~ updated ~~~~these~~~~ terms ~~~~on~~~~ April ~~~~10~~~~ , ~~~~ 2024 ~~~~,~~ ~~and~~~~ may ~~~~update~~~~ these ~~~~terms~~~~ again ~~~~.~~ ~~The~~~~ company ~~~~will~~~~ post ~~~~all~~~~ updates ~~~~to~~~~ the ~~~~forum~~~~. ~~For updates that contain substantial changes, the company agrees to either e-mail you, if you’ve created an account and provided a valid e-mail address~~. ~~,~~ The ~~~~company~~~~ may ~~~~also~~ or to announce the updates with special messages or alerts on the forum. > > Once you get notice of an update to these terms, you must agree to the new terms in order to keep using the forum. The most notable difference may be the process, because we now have a feature to force a user field to be completed by both new and existing users: [https://github.com/discourse/discourse/pull/27079](https://github.com/discourse/discourse/pull/27079) ---
**Author:** ![Thomas\_DC](https://avatars.discourse-cdn.com/v4/letter/t/5f8ce5/32.png) [@Thomas\_DC](https://meta.discourse.org/u/Thomas_DC)\ **Post date:** [January 7, 2025, 3:51pm UTC](https://meta.discourse.org/t/what-changed-in-the-meta-tos-july-18-2024/317201/8 "2025-01-07T15:51:53Z")
Thank you very much @awesomerobot 🙂 Then, I agree @Jagster that someone came to idea that consent of users is legal need, so it would be very nice to make a feature which generates the diff you posted here, and makes it available in the mandatory banner. 🙂 ---
**Author:** ![Moin](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/moin/32/554653_2.png) [@Moin](https://meta.discourse.org/u/Moin)\ **Post date:** [April 27, 2026, 6:47am UTC](https://meta.discourse.org/t/what-changed-in-the-meta-tos-july-18-2024/317201/9 "2026-04-27T06:47:47Z")
I thought users who posted here or in [What changed in the Meta TOS (April 8, 2024)?](https://meta.discourse.org/t/what-changed-in-the-meta-tos-april-8-2024/303258/) might be interested in the fact that the TOS seem to have changed again. Unfortunately, the date at the end wasn’t updated. It still says > The company last updated these terms on February 13, 2025, and may update these terms again. The company will post all updates to the forum. > > For updates that contain substantial changes, the company agrees to either e-mail you, if you’ve created an account and provided a valid e-mail address, or to announce the updates with special messages or alerts on the forum. But there is information regarding the volunteer mods now, which must have been added at the end of March ([archive.org - Meta TOS - March 20](https://web.archive.org/web/20260320111856/https://meta.discourse.org/tos) doesn’t have the new part, but [archive.org - Meta TOS - April 2](https://web.archive.org/web/20260402152836/https://meta.discourse.org/tos) has it). This is the new part: > Volunteer Moderators > > The company may use volunteer moderators to review reports and moderate content. Volunteer moderators participate on a voluntary basis and are not employees, contractors, or representatives of the company. > > Volunteer moderators may remove or flag content, issue warnings, temporarily suspend users, and escalate violations to company personnel. Volunteer moderators may not create policies, represent the company, or override moderation decisions. > > Volunteer moderators must enforce community rules fairly, treat users respectfully, avoid harassment or discrimination, and not misuse moderation powers. > > Volunteer moderators must keep confidential all user reports, moderation discussions, internal moderation tools, and any non-public user data. Volunteer moderators must comply with applicable privacy laws, including the General Data Protection Regulation where applicable. > > Volunteer moderator privileges are granted at the company’s discretion and may be modified, suspended, or revoked at any time. > > Volunteer moderators must act in good faith and follow the Moderation Policy, [Community Guidelines](https://meta.discourse.org/guidelines), and applicable law. > > To the maximum extent permitted by law, the company is not liable for actions taken by volunteer moderators in connection with moderation activities. > > Each volunteer moderator agrees to indemnify and hold harmless the company and its affiliates, officers, directors, employees, and agents from any claims, damages, liabilities, costs, or expenses arising from: > (a) misuse of moderation tools or privileges; > (b) violation of these Terms or the [Community Guidelines](https://meta.discourse.org/guidelines); or > (c) violation of applicable law or third-party rights.