Let’s build at least something that covers user profiles and comments (if they will be in version 1.0) so that we have it in the product. Can then still be improved later.
Other Drupal CMS tracks: further action required?
The following areas may be relevant and should be checked. In addition to that, we all should keep our eyes open on the full Drupal CMS product to find potential issues for privacy and then raise them to the team.
Events: cover their external maps
Registration for an event: consent for registration
Comments: do we need consent for data storage on the server?
Default content
Following the great feedback in the issue, we summarized our action plan in this comment:
https://www.drupal.org/project/drupal_cms/issues/3480902#comment-15853708
📌
Default content for privacy requirementsActive
Hoping for feedback there so that we can finally execute this.
ADR: Architecture Decision Record
We should provide an ADR for consent management and we’ve opened an issue for this at
https://www.drupal.org/project/drupal_cms/issues/3486990
📌
ADR for consent managementActive
Our track will be part of the next Dries note in Singapore
Drupal CMS and telemetry: consulting
There will be telemetry in Drupal CMS and we will have to provide feedback on how to do that such that we won’t come back later with privacy issues.
uBlock Origin and others block the Klaro library by default
