Plugin de Ferramentas Legais

[angus (Angus McLeod)]

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

Este plugin fornece ferramentas para auxiliar na conformidade legal ao executar um fórum Discourse. As ferramentas serão adicionadas de forma contínua.

Por favor, observe a isenção de responsabilidade abaixo. Este plugin não oferece nenhuma garantia de conformidade legal.

Download Estendido de Usuário

O download estendido de usuário é um único arquivo CSV com as seguintes entradas, cada uma separada por duas linhas em branco:

• Um cabeçalho (pode ser editado: Personalizar > Conteúdo de Texto > “csv_export.extended.title”):

  Todas as informações de %{username} armazenadas por %{site_name}

  • “username” é o nome de usuário do usuário cujas informações estão no download.
  • “site_name” é a configuração do site title.

• Uma nota abaixo do cabeçalho (pode ser editada: Personalizar > Conteúdo de Texto > “csv_export.extended.note”):

  Por favor, observe que algumas informações associadas ao identificador do usuário %{username}
  foram excluídas deste download devido a interesses contrários de privacidade e legais.
  Para mais informações, entre em contato com %{site_contact}.

  • “username” é o nome de usuário do usuário cujas informações estão no download.
  • “site_contact” é a configuração do site contact email.

• Posts. As informações padrão incluídas no download do usuário.

• Conta. Informações da conta e do perfil.

• Contas Externas. Informações de contas externas (se existirem).

• Estatísticas. Informações estatísticas armazenadas sobre o usuário.

• Login e Histórico de Login. Informações sobre logins do usuário.

• Pesquisas. Todos os registros com IP de pesquisas realizadas pelo usuário.

• Visualizações de Tópico. Todas as visualizações de tópico com IP do usuário.

• Cliques em Links de Tópico. Todos os links de tópico com IP clicados pelo usuário.

• Visualizações de Perfil. Todas as visualizações de perfil com IP do usuário.

• Ações. Todas as ações realizadas pelo usuário.

• Histórico. Todos os registros com IP de ações registráveis envolvendo o usuário.

Existem duas configurações do site que habilitam o download estendido:

• legal extended user download: Quando habilitado, o recurso “Baixar Tudo” na página de Atividade do Usuário torna-se um download estendido.

  • Por favor, observe que, como o download normal de usuário, o download estendido de usuário só pode ser realizado por um usuário uma vez por dia.

• legal extended user download admin. Quando habilitado, a equipe permitida pode baixar todas as informações de qualquer usuário do site. Eles verão um novo botão “Baixar Tudo” no topo das informações do usuário do administrador de cada usuário.

  

  Opções:

  • Desabilitado (padrão)
  • Apenas Administradores (apenas administradores podem usar o recurso de download estendido de administrador)
  • Administradores e Equipe (tanto administradores quanto equipe podem usar o recurso de download estendido de administrador)

As duas configurações são separáveis, ou seja, você pode habilitar legal extended user download sem dar aos administradores ou à equipe a capacidade de baixar todas as informações de todos os usuários, ou pode habilitar legal extended user download admin sem dar aos usuários a capacidade de baixar todas as suas informações.

O contexto para este recurso é o GDPR da UE. Veja em particular:

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

Por favor, observe que você deve considerar as implicações de segurança de permitir que usuários, equipe e/ou administradores tenham a capacidade de baixar todas as informações listadas. Este recurso pode não ser adequado em todas as circunstâncias. Mais informações sobre este assunto podem ser encontradas nos tópicos acima.

Uma alternativa ao download direto das informações do usuário é que um membro relevante da equipe (um “Oficial de Proteção de Dados”) compile as informações por meio de consultas ao banco de dados.

Isenção de Responsabilidade

O plugin Legal Tools (o “Plugin”) e seu autor Angus McLeod (o “Autor”) não são advogados nem substituem um advogado ou aconselhamento jurídico. As comunicações entre você e o Autor não são protegidas pelo privilégio advogado-cliente nem como produto de trabalho. O Plugin e seu Autor não podem fornecer qualquer tipo de aconselhamento, explicação, opinião, recomendação ou garantia sobre possíveis direitos legais, recursos, defesas, opções, seleção de formulários ou estratégias.

[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, acabei de tentar exportar dados de um usuário (uma solicitação de GDPR) clicando no botão correto (baixar tudo), mas recebi uma mensagem do sistema informando que a exportação de dados falhou e que eu deveria verificar os logs.

Não consigo determinar se isso é agora um problema dentro do plugin ou um problema do próprio Discourse.
Atualização em 11 de janeiro, 17:40 UTC: A equipe do Discourse acabou de informar que, ao analisar o rastreamento de erros, trata-se de um problema em um plugin de terceiros. @angus, você poderia, por favor, verificar isso? Obrigado.

A instância do Discourse está rodando na versão 2.7.0.beta1 ( 4f72830eb0 )
Atualização em 11 de janeiro, 16:15 UTC: agora na versão 2.7.0.beta1 ( 422f395042 ), mas o erro permanece o mesmo.

Esta é a configuração dentro do plugin:

Nos logs, vejo o seguinte erro:
Exceção de Job: método collect não 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)]

Peço desculpas pela resposta demorada aqui, estive ausente

Reproduzi o problema e corrigi. Por favor, atualize e tente fazer o download novamente. Se possível, me informe como foi o resultado da solicitação.

Update to support split user_archive job

[GuidoD (Guido Drehsen)]

@angus

Estive ausente

Sem problemas, foi um fim de semana e ninguém precisa reagir imediatamente.
Agradeço por este plugin.

@angus

Por favor, atualize e tente o download novamente. Se possível, me informe como foi a solicitação.

Atualizei e tentei novamente.
Funcionou perfeitamente, muito obrigado pela correção. Realmente aprecio seu ótimo trabalho.

Se eu também quisesse incluir registros ‘administrativos’ com o user_id do usuário, como flags, reclamações e sussurros de staff, quais seriam as melhores instruções SQL para obter os dados usando o explorador de dados?
Se necessário, eu poderia fornecer esses dados separadamente ao usuário que solicitou as informações.