GDPR Compliance Chat Recap – February 21st

(full text on slack)

A centralised GitHub folder was created to gather all info (Roadmap, knowledge base, trac tickets list, etc) while waiting for a final location: https://github.com/gdpr-compliance/info

@idea15 (webdevlaw on slack) indicated that a privacy centre to hold GDPR information for site users, for site administrators/owners, and developers is being build. To be checked how this will be split between wordpress.org and wordpress.com

How 'other systems' deal with the request to see personal data can be found on https://github.com/gdpr-compliance/info/blob/master/KB.md#how-do-others-allow-users-to-download-their-own-data

A discussion was started if the GDPRWP.com interface is way to go and/or if Core should provide actions & filters to provide means to plugins to report their personal data.

@allendav was pointing to https://github.com/allendav/wp-privacy-policy-shortcodes for possible shortcodes to expose privacy policy statements in a consistent way.

@schlessera pointed out that localization might be difficult to handle, how to avoid a mix of languages?

Current global idea is that plugins submit the info using hooks/filters, the admin/controller needs to 'accept' them so that enduser can see the full list, all based on versioning per plugin.

Additional capabilities (like e.g. manage_compliance) could be needed.

#gdpr-compliance #summary