At a glance (source / learn more)
Similar to #12596 and #12595 we want to allow users to update any data that is currently stored in the database. After identifying a user see #12596 and #12595, we could show a list of all known log tables and their respective columns. The Matomo user could see for example a list of all tables, when selecting a table, the user would see a list of all columns in that table. As most columns are defined in dimension classes, we actually have readable names and some description for each dimension there. If we don’t want to let users edit all fields, we could add a new property “holds potentially personal data” to show only these. However, easiest and most flexible way be to really show all fields.
We would need to see here as well regarding re-processing this data afterwards. In V1, we will not re-process historical data.
We ideally also have an event for plugins to support this feature in case they store personal data outside of log tables.
In V1 or V2 we could store data about how often this has occurred per day/week/month etc.
We would also support the Activity Log feature and trigger an event whenever some data was changed.
We are considering that the Right to rectification, could be offered in Matomo via the new Personal Data Anonymisation & Removal tool for analytics raw data - GDPR compliance #12641
Therefore we are considering letting Super Users delete particular fields of users, but not "Edit" the data. This should be good enough to ensure GDPR compliance when users exercise their right to rectification. Maybe in the future Matomo would offer ability to "Edit" previous metadata (and not Delete), but we don't consider it necessary as part of GDPR compliance.
Right to rectification:
we've decided to implement both a Data anonymising tool that will update all previous date (in a given date range):
We've also Implemented in the new Administration > Privacy > GDPR Tools page in https://github.com/matomo-org/matomo/pull/12558