Does Largo need to do anything in response to the 4.9.6 GDPR update?

[benlk]

• review:
  • https://make.wordpress.org/core/2018/05/17/changes-that-affect-theme-authors-in-wordpress-4-9-6/
  • https://developer.wordpress.org/plugins/privacy/suggesting-text-for-the-site-privacy-policy/
  • https://developer.wordpress.org/plugins/privacy/adding-the-personal-data-eraser-to-your-plugin/
  • https://developer.wordpress.org/plugins/privacy/adding-the-personal-data-exporter-to-your-plugin/
• check the comment forms functionality

[benlk]

• simple opt-out of remove the thing where we output the Largo Google Analytics property.
  • why were we collecting that info in the first place? (did it directly feed into https://github.com/INN/largo/wiki/Sites-Using-Largo ?)
  • can we replace the Google Analytics with a Google Form like PressForward's admin-facing popup: https://github.com/PressForward/pressforward/blob/63293755f5002bc54b8bda3869ce7a7b52911e8c/assets/js/checkin.js
  • can we replace the Google Analytics with a dismissable request to "please send us an email by clicking [this link](mailto:labs@inn.org?subject=New+Largo+User&body=Our+site+URL+is+%1$s), we'll use it for the following purposes: <list>

[benlk]

If we have a defined "We will use your email address for the following things" policy, that policy should be stated on labs.inn.org and link out to relevant third-party privacy policies, such as any mailing-list provider we use to contact Largo users.

[benlk]

And if we have a "tell us that you use us" page, that page would be a good place to put a "donate to us" link of some sort.

[benlk]

Will be squeezing part of this encouragement to say hi into the changelog and readme.

[benlk]

See also the California Consumer Privacy Act guidance at https://oag.ca.gov/privacy/ccpa

[benlk]

top term metabox improvements

[benlk]

Closing this because it's not clearly related to any specific improvements anymore.