Libraries in particular can get help from the Library Freedom Project to set up HTTPS. Some librarians have come to appreciate its importance in protecting information about what library resources (like books) patrons are interested in, for library web sites that allow people to do catalogue searches online, for example.<p><a href="https:&#x2F;&#x2F;libraryfreedomproject.org&#x2F;ourwork&#x2F;digitalprivacypledge&#x2F;" rel="nofollow">https:&#x2F;&#x2F;libraryfreedomproject.org&#x2F;ourwork&#x2F;digitalprivacypled...</a><p>(It&#x27;s true that that&#x27;s not the original poster&#x27;s exact example, which hypothesized a static site that just tells you the library&#x27;s schedule. But I think library catalogues are a super-great example where information is completely public -- it&#x27;s not secret what the library has in its collection -- but information about users&#x27; interest in that information is private and sensitive, and the people providing the information strongly agree with that concern when they stop to think about it; librarians care <i>very much</i> about not revealing who is interested in which books.)