# More graceful handling of Subscriber Agreement changes **URL:** \ **Category:** Feature Requests\ **Created:** [January 7, 2018, 2:18pm UTC](https://community.letsencrypt.org/t/more-graceful-handling-of-subscriber-agreement-changes/49754 "2018-01-07T14:18:11Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![Patches](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/patches/32/17145_2.png) [@Patches](https://community.letsencrypt.org/u/Patches)\ **Post date:** [January 7, 2018, 6:40pm UTC](https://community.letsencrypt.org/t/more-graceful-handling-of-subscriber-agreement-changes/49754/2 "2018-01-07T18:40:26Z")
The Let's Encrypt Subscriber Agreement contains a clause that says you agree to any future changes they may make. Because of this, Let's Encrypt does not use this feature of the ACME protocol that requires you agree to a new Subscriber Agreement when it is changed. > [@Subscriber agreement update November 15, 2017](https://community.letsencrypt.org/t/subscriber-agreement-update-november-15-2017/45607/1): > > As @josh notes, we’ll be making a very minor update to our subscriber agreement on November 15, 2017. This should be transparent to almost all API users. You do not need to re-agree to the new subscriber agreement. So the feature you want already exists. 😀. But... > [@Subscriber agreement update November 15, 2017](https://community.letsencrypt.org/t/subscriber-agreement-update-november-15-2017/45607/1): > > Last time we updated the subscriber agreement, there were a handful of clients that tried to explicitly re-agree once we updated the subscriber agreement URL, producing errors. The ACME spec has been clarified to indicate that’s not necessary, and I believe the affected clients have been fixed. And this is a [known issue with acmetool](https://github.com/hlandau/acme/issues/288). Hopefully they will fix it by the next update to the agreement. 😉 _[edited because I found the bug already existed after posting]_ --- _[View the full topic](https://community.letsencrypt.org/t/more-graceful-handling-of-subscriber-agreement-changes/49754)._