No, we need @riking to come through with the removal of IP where it’s unnecessarily recorded and should not be first. If that can’t be achieved in a reasonable timeframe we need to get someone else to do it.
All user-related records in user activity (record of likes, bookmarks, topics, replies etc) have been added to the download (commit).
I initially didn’t add this as it seemed like overkill. However @RGJ raised it with me and we had a productive exchange on the question.
Essentially, we decided that the best approach for the purposes of this feature was to include all records of activity tied to the user’s identifier that don’t entail countervailing concerns about the privacy of others or similar rights.
I would emphasise “for the purposes of this feature”, as the purpose of this feature is to take a ‘maximalist’ approach to possible interpretations of the GDPR. It does not attempt to parse ‘likely’ approaches. I’ve laid out some of my own views on the ‘likely’ approaches in this topic (which remain unchanged).
The specifics of the reasoning behind this ‘maximalist’ approach are:
The broadest interpretation of A.4.1 (the definition of ‘Personal Data’ in the GDPR) as it applies to Discourse is any record in the db that contains the user’s user_id, i.e.:
any information … identified or identifiable natural person … identified, directly or indirectly, in particular by reference to … an identification number
Read literally, this definition doesn’t care about how the data is produced (e.g. whether the user is acting or not). It merely requires the data to be related to the user’s identifier in some way.
However, applying that literally would produce a fair amount of duplication (e.g. the records in the directory_items table are duplicative of various other entries).
The point of the extended download is to guard against even the small risk that Article 4.1 could receive a very broad interpretation by some authority or court in Europe.
The factors against including it - size of download, potentially security (?) - do not outweigh the possible benefit of including it.
We also considered whether to include ‘administrative’ records with the user’s user_id such as flags, complaints and staff whispers. We decided against this, reasoning as follows:
They’re already in the territory of information associated with the user purely by their identifier. They are not information about the user per se (i.e. name, email, age, location etc). This is already assuming a wide interpretation of A.4.1.
Whether administrative records intrude on the privacy of other parties, or other relevant concerns (i.e. R. 63.5 & A.15.4) must be determined on a case-by-case basis.
Other parties, such as Facebook, do no include such data in their user download functionality.
I’m having some trouble getting this to work. I’ve enabled the ‘legal extended user download’ setting, refreshed the page and clicked the ‘Download all’ button on the activity page. This results in an archive that contains one CSV file with topics in it. I checked both as an admin and as a regular user. What is the expected output - multiple CSV files, each for a different table?
The expected output is a single csv with headers for each item mentioned in the first post in this topic. If you try it out on my sandbox, this is what you’ll get.
Nope. We had a few users with the same kind of complaint though but it turned out to be a false alarm.
I guess they never scrolled down past the posts. Maybe it’s an idea to move the posts section (i.e. the most unstructured / multiline content) to be the last section.
Thanks Richard. Definitely not seeing those. So just to be sure I’m doing the right thing: this plugin is supposed to replace the ‘Download’ button in the Profile > Activity sidebar, right?
First words of admiration go to @angus for doing such a great job helping everyone here to get those highly useful tools (not only this plugin but other plugins too).
I’ve got one question though: wouldn’t it be better to have this export available to admins only (at least as option for those concerned)?
Isn’t it potentially risky in case when given account password is compromised and then ‘all activity’ is easily downloaded by unauthorized person? (Sorry that is two questions )
I just did a few more tests and tried it on your sandbox too. My results are just the default download - they don’t match your new format. I don’t think I see any errors in sidekiq (at least not in ‘Failed’ - ‘Errors’ is not clickable). Any suggestions how I can best find more information here?
There are now two site settings that enable the extended download:
legal extended user download: When enabled, the “Download All” feature in the User Activity page becomes an extended download.
Please note that, like the normal user download, the extended user download can only be performed by a user once a day.
legal extended user download admin. When enabled, permitted staff can download all the information of any user of the site. They will see an new “Download All” button at the top of the the admin user information of each user.
Options:
Disabled (default)
Admins Only (only admins can use the admin extended download feature)
Admins and Staff (both admins and staff can use the admin extended download feature)
The two settings are severable, i.e. you can enable legal extended user download without giving admins or staff the ability to download all the information of every user, or you can enable legal extended user download admin without giving users the ability to download all of their information.
Due to the security implications of allowing users (even if they’re admins) to download all the information of other users, I’ve been particularly careful with protecting the admin extended user download server methods, however I would appreciate a second set of eyes on that aspect of the changes, particularly considering this feature seems to be quite popular. Perhaps you could take a look @riking if you have the time? (i.e. particularly the changes to the Guardian).
I’ve also added text to the top of the extended csv:
A header (can be edited: Customize > Text Content > “csv_export.extended.title”):
All information of %{username} stored by %{site_name}
“username” is the username of the user who’s information is in the download.
“site_name” is the title site setting.
A note below the header (can be edited: Customize > Text Content > “csv_export.extended.note”):
Please note that some information associated with the user identifier of %{username}
has been excluded from this download due to countervailing privacy and legal interests.
For more information, please contact %{site_contact}.
“username” is the username of the user who’s information is in the download.
“site_contact” is the contact email site setting.
This has all been tested on my sandbox where it is currently live.
@bartv Let me know if these updates fix your issue.
That is primarily referring to the exclusion mentioned below, and also helps if we’ve not included something some authority happens to consider relevant.
for doing such a great job helping everyone here to get those highly useful tools (not only this plugin but other plugins too).
)
。