Plugin de herramientas legales

[angus (Angus McLeod)]

Repositorio: GitHub - paviliondev/discourse-legal-tools: Tools to help with legal compliance when using Discourse · GitHub

Este plugin proporciona herramientas para ayudar con el cumplimiento legal al ejecutar un foro de Discourse. Las herramientas se agregarán de manera continua.

Tenga en cuenta el descargo de responsabilidad a continuación. Este plugin no ofrece ninguna garantía de cumplimiento legal.

Descarga extendida de usuario

La descarga extendida de usuario es un único archivo CSV con las siguientes entradas, cada una separada por dos líneas en blanco:

• Un encabezado (puede ser editado: Personalizar > Contenido de texto > “csv_export.extended.title”):

  Toda la información de %{username} almacenada por %{site_name}

  • “username” es el nombre de usuario del usuario cuya información está en la descarga.
  • “site_name” es la configuración del sitio title.

• Una nota debajo del encabezado (puede ser editada: Personalizar > Contenido de texto > “csv_export.extended.note”):

  Tenga en cuenta que cierta información asociada con el identificador de usuario de %{username}
  ha sido excluida de esta descarga debido a intereses legales y de privacidad contrapuestos.
  Para más información, póngase en contacto con %{site_contact}.

  • “username” es el nombre de usuario del usuario cuya información está en la descarga.
  • “site_contact” es la configuración del sitio contact email.

• Publicaciones. La información predeterminada incluida en la descarga del usuario.

• Cuenta. Información de la cuenta y del perfil.

• Cuentas externas. Información de cuentas externas (si existe).

• Estadísticas. Información estadística almacenada sobre el usuario.

• Inicio de sesión e historial de inicio de sesión. Información sobre los inicios de sesión del usuario.

• Búsquedas. Todos los registros con dirección IP de las búsquedas realizadas por el usuario.

• Vistas de temas. Todas las vistas de temas con dirección IP del usuario.

• Clics en enlaces de temas. Todos los enlaces de temas con dirección IP en los que el usuario hizo clic.

• Vistas de perfiles. Todas las vistas de perfiles con dirección IP del usuario.

• Acciones. Todas las acciones realizadas por el usuario.

• Historial. Todos los registros con dirección IP de acciones registrables que involucran al usuario.

Existen dos configuraciones del sitio que habilitan la descarga extendida:

• legal extended user download: Cuando está habilitada, la función “Descargar todo” en la página de Actividad del usuario se convierte en una descarga extendida.

  • Tenga en cuenta que, al igual que la descarga normal de usuario, la descarga extendida de usuario solo puede ser realizada por un usuario una vez al día.

• legal extended user download admin. Cuando está habilitada, el personal autorizado puede descargar toda la información de cualquier usuario del sitio. Verán un nuevo botón “Descargar todo” en la parte superior de la información de usuario del administrador de cada usuario.

  

  Opciones:

  • Deshabilitado (predeterminado)
  • Solo administradores (solo los administradores pueden usar la función de descarga extendida de administrador)
  • Administradores y personal (tanto administradores como personal pueden usar la función de descarga extendida de administrador)

Las dos configuraciones son separables, es decir, puede habilitar legal extended user download sin dar a los administradores o al personal la capacidad de descargar toda la información de cada usuario, o puede habilitar legal extended user download admin sin dar a los usuarios la capacidad de descargar toda su información.

El fundamento de esta función es el RGPD de la UE. Véase en particular:

• GDPR countdown and compliance
• Providing data for GDPR
• Problematic IP address fields
• https://meta.discourse.org/t/gdpr-compliance-solution-pls-critique/87908

Tenga en cuenta que debe considerar las implicaciones de seguridad de permitir a los usuarios, al personal y/o a los administradores la capacidad de descargar toda la información enumerada. Esta función puede no ser adecuada en todas las circunstancias. Se puede encontrar más información sobre este tema en los temas anteriores.

Una alternativa a descargar directamente la información del usuario es que un miembro relevante del personal (un “Oficial de Protección de Datos”) compile la información mediante consultas a la base de datos.

Descargo de responsabilidad

El plugin Legal Tools (el “Plugin”), y su autor Angus McLeod (el “Autor”), no son abogados ni un sustituto de un abogado o asesoramiento legal. Las comunicaciones entre usted y el Autor no están protegidas por el privilegio abogado-cliente ni como trabajo producto. El Plugin, y su Autor, no pueden proporcionar ningún tipo de asesoramiento, explicación, opinión, recomendación o garantía sobre posibles derechos legales, recursos, defensas, opciones, selección de formularios o estrategias.

[sam (Sam Saffron)]

@codinghorror how much of this do you think belongs in core? Should we just amend our default “download all my data” to include all this stuff?

[codinghorror (Jeff Atwood)]

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.

[angus (Angus McLeod)]

Update here.

Scope of the download

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.

[bartv (Bart)]

Hey Angus,

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?

[angus (Angus McLeod)]

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.

Do you see any errors at /sidekiq?

@RGJ have you had this issue?

[RGJ (Richard - Communiteq)]

@angus

@RGJ have you had this issue?

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.

[bartv (Bart)]

Could you provide a few of the header rows as an example so I can do a search for them?

[RGJ (Richard - Communiteq)]

See the ‘separator’ lines here.

[bartv (Bart)]

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?

[tm2017]

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 )

[bartv (Bart)]

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?

[angus (Angus McLeod)]

@bartv

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

Please post (or PM) a screenshot of the csv you got from my sandbox with the ip addresses blacked out (if any).

@tm2017

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)?

I think I’ll make this a setting.

@tm2017

Isn’t it potentially risky in case when given account password is compromised and then ‘all activity’ is easily downloaded by unauthorized person?

Potentially. This is partly what I meant by

@angus

Please note, that you should consider the security implications of allowing users to directly download all the listed information.

Nevertheless, some people will need / want the functionality of allowing users to directly download their info. So I think a setting is the move here.

[angus (Angus McLeod)]

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.

[bartv (Bart)]

This new version solves the issue I had before. Thanks for all your hard work on this, Angus!

The extended note is interesting; could you shed some light on which information has been excluded and for which reasons?

[angus (Angus McLeod)]

That is primarily referring to the exclusion mentioned below, and also helps if we’ve not included something some authority happens to consider relevant.

@angus

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.

[GuidoD (Guido Drehsen)]

Como administrador, acabo de intentar exportar los datos de un usuario (una solicitud GDPR) haciendo clic en el botón correcto (descargar todo), pero el sistema me mostró un mensaje indicando que la exportación de datos falló y que debía revisar los registros.

No puedo determinar si esto es ahora un problema dentro del plugin o un problema del propio Discourse.
Actualización 11 de enero, 17:40 UTC: El equipo de Discourse acaba de indicar que, al revisar el rastreo de errores, se trata de un problema en un plugin de terceros. @angus, ¿podrías por favor revisar esto? Gracias.

La instancia de Discourse se está ejecutando en la versión 2.7.0.beta1 ( 4f72830eb0 )
Actualización 11 de enero, 16:15 UTC: ahora en la versión 2.7.0.beta1 ( 422f395042 ), pero el error sigue siendo el mismo.

Esto es lo que está configurado dentro del plugin:

En los registros veo el siguiente error:
Excepción del trabajo: método collect no definido para nil:NilClass

/usr/local/lib/ruby/2.7.0/csv/writer.rb:46:in `<<'
/usr/local/lib/ruby/2.7.0/csv.rb:1230:in `<<'
/var/www/discourse/app/jobs/regular/export_csv_file.rb:66:in `block (3 levels) in execute'
/var/www/discourse/plugins/discourse-legal-tools/lib/export_csv_file_extension.rb:267:in `user_archive_export_extended'
/var/www/discourse/plugins/discourse-legal-tools/lib/export_csv_file_extension.rb:226:in `admin_user_archive_export'
/var/www/discourse/app/jobs/regular/export_csv_file.rb:66:in `each'
/var/www/discourse/app/jobs/regular/export_csv_file.rb:66:in `block (2 levels) in execute'
/usr/local/lib/ruby/2.7.0/csv.rb:658:in `open'
/var/www/discourse/app/jobs/regular/export_csv_file.rb:64:in `block in execute'
/var/www/discourse/app/jobs/regular/export_csv_file.rb:63:in `each'
/var/www/discourse/app/jobs/regular/export_csv_file.rb:63:in `execute'
/var/www/discourse/app/jobs/base.rb:232:in `block (2 levels) in perform'
rails_multisite-2.5.0/lib/rails_multisite/connection_management.rb:76:in `with_connection'
/var/www/discourse/app/jobs/base.rb:221:in `block in perform'
/var/www/discourse/app/jobs/base.rb:217:in `each'
/var/www/discourse/app/jobs/base.rb:217:in `perform'
sidekiq-6.1.2/lib/sidekiq/processor.rb:196:in `execute_job'
sidekiq-6.1.2/lib/sidekiq/processor.rb:164:in `block (2 levels) in process'
sidekiq-6.1.2/lib/sidekiq/middleware/chain.rb:138:in `block in invoke'
/var/www/discourse/lib/sidekiq/pausable.rb:138:in `call'
sidekiq-6.1.2/lib/sidekiq/middleware/chain.rb:140:in `block in invoke'
sidekiq-6.1.2/lib/sidekiq/middleware/chain.rb:143:in `invoke'
sidekiq-6.1.2/lib/sidekiq/processor.rb:163:in `block in process'
sidekiq-6.1.2/lib/sidekiq/processor.rb:136:in `block (6 levels) in dispatch'
sidekiq-6.1.2/lib/sidekiq/job_retry.rb:111:in `local'
sidekiq-6.1.2/lib/sidekiq/processor.rb:135:in `block (5 levels) in dispatch'
sidekiq-6.1.2/lib/sidekiq.rb:38:in `block in <module:Sidekiq>'
sidekiq-6.1.2/lib/sidekiq/processor.rb:131:in `block (4 levels) in dispatch'
sidekiq-6.1.2/lib/sidekiq/processor.rb:257:in `stats'
sidekiq-6.1.2/lib/sidekiq/processor.rb:126:in `block (3 levels) in dispatch'
sidekiq-6.1.2/lib/sidekiq/job_logger.rb:13:in `call'
sidekiq-6.1.2/lib/sidekiq/processor.rb:125:in `block (2 levels) in dispatch'
sidekiq-6.1.2/lib/sidekiq/job_retry.rb:78:in `global'
sidekiq-6.1.2/lib/sidekiq/processor.rb:124:in `block in dispatch'
sidekiq-6.1.2/lib/sidekiq/logger.rb:10:in `with'
sidekiq-6.1.2/lib/sidekiq/job_logger.rb:33:in `prepare'
sidekiq-6.1.2/lib/sidekiq/processor.rb:123:in `dispatch'
sidekiq-6.1.2/lib/sidekiq/processor.rb:162:in `process'
sidekiq-6.1.2/lib/sidekiq/processor.rb:78:in `process_one'
sidekiq-6.1.2/lib/sidekiq/processor.rb:68:in `run'
sidekiq-6.1.2/lib/sidekiq/util.rb:15:in `watchdog'
sidekiq-6.1.2/lib/sidekiq/util.rb:24:in `block in safe_thread'

[angus (Angus McLeod)]

Disculpa la respuesta tardía, he estado fuera .

He reproducido el problema y lo he solucionado. Por favor, actualiza e intenta descargar de nuevo. Si es posible, házmelo saber sobre cómo va la solicitud.

Update to support split user_archive job

[GuidoD (Guido Drehsen)]

@angus

He estado ausente

No hay problema, fue un fin de semana y nadie tiene que reaccionar de inmediato.
Estoy agradecido por este plugin.

@angus

Por favor, actualiza e intenta la descarga de nuevo. Si es posible, avísame cómo fue la solicitud.

Actualicé e intenté de nuevo.
Funcionó perfectamente, muchas gracias por la solución, realmente aprecio tu buen trabajo.

Si quisiera incluir también registros «administrativos» con el user_id del usuario, como banderas, quejas y susurros del personal, ¿cuáles serían las mejores sentencias SQL para obtener los datos con el explorador de datos?
Si es necesario, podría proporcionar estos datos por separado al usuario que solicitó la información.