gdpr
Do I have the right to ask Github to hide my Contribution activity according to General Data Protection Regulation (GDPR)
<p>Do I have the right to ask Github to hide my "Contribution activity" on my public profile page? </p>

<p><a href="https://i.stack.imgur.com/b4Alw.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/b4Alw.png" alt="enter image description here"></a></p>

<p>The "Contribution activity" is extracted from repositories hosted on Github. Looking at the privacy statement, Github considers itself as a hosting service for those repositories. See EU <a href="http://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32000L0031" rel="nofollow noreferrer">Directive 2000/31/EC</a> Article 14 for the exact definition and conditions:</p>

<blockquote>
  <p>Article 14</p>
  
  <p>Hosting</p>
  
  <ol>
  <li><p>Where an information society service is provided that consists of the storage of information provided by a recipient of the service,
  Member States shall ensure that the service provider is not liable for
  the information stored at the request of a recipient of the service,
  on condition that:</p>
  
  <p>(a) the provider does not have actual knowledge of illegal activity or
  information and, as regards claims for damages, is not aware of facts
  or circumstances from which the illegal activity or information is
  apparent; or</p>
  
  <p>(b) the provider, upon obtaining such knowledge or awareness, acts
  expeditiously to remove or to disable access to the information.</p></li>
  <li><p>Paragraph 1 shall not apply when the recipient of the service is acting under the authority or the control of the provider.</p></li>
  <li><p>This Article shall not affect the possibility for a court or administrative authority, in accordance with Member States' legal
  systems, of requiring the service provider to terminate or prevent an
  infringement, nor does it affect the possibility for Member States of
  establishing procedures governing the removal or disabling of access
  to information.</p></li>
  </ol>
</blockquote>

<p><a href="https://gdpr-info.eu/art-2-gdpr/" rel="nofollow noreferrer">Article 2(4) GDPR</a> defines that the GDPR does not apply (to Github) in this case</p>

<blockquote>
  <ol start="4">
  <li>This Regulation shall be without prejudice to the application of Directive 2000/31/EC, in particular of the liability rules of intermediary service providers in Articles 12 to 15 of that Directive.</li>
  </ol>
</blockquote>

<p>Extracting data from the repositories to create a nicely formatted contribution activity list, would still be considered hosting as defined at Directive 2000/31/EC, because Github does not (manually) redact or modify commits.</p>

<p>So if you want to hide your contribution activity, you must delete the contributions. And you should not ask Github to do that, but ask the owners of the repositories. And they might have good reasons to deny your request.</p>

<p>If an owner of a repository denies your request without a good reason, you can ask Github to do so. But Github would then probably deny that request, because they explain in their <a href="https://help.github.com/articles/github-privacy-statement/#data-retention-and-deletion-of-data" rel="nofollow noreferrer">privacy statement</a> that modifying the history is not possible:</p>

<blockquote>
  <p>The email address you have supplied via your Git commit settings will always be associated with your commits in the Git system. If you chose to make your email address private, you should also update your Git commit settings. We are unable to change or delete data in the Git commit history — the Git software is designed to maintain a record — but we do enable you to control what information you put in that record.</p>
</blockquote>

<p><strong>edit</strong></p>

<p>To further clarify why Article 14 of Directive 2000/31/EC applies, see case C-236/08 (Google v. Louis Vuitton) where the European Court of Justice clarifies the meaning of that article (<a href="http://curia.europa.eu/juris/document/document.jsf;jsessionid=9ea7d0f130deb9df5869f7a048b099eac5ff2b9a5a44.e34KaxiLc3eQc40LaxqMbN4Pb3aLe0?text=&amp;docid=83961&amp;pageIndex=0&amp;doclang=EN&amp;mode=lst&amp;dir=&amp;occ=first&amp;part=1&amp;cid=469816" rel="nofollow noreferrer">ECLI:EU:C:2010:159</a>):</p>

<blockquote>
  <ol start="113">
  <li><p>In that regard, it follows from recital 42 in the preamble to Directive 2000/31 that the exemptions from liability established in that directive cover only cases in which the activity of the information society service provider is ‘of a mere technical, automatic and passive nature’, which implies that that service provider ‘has neither knowledge of nor control over the information which is transmitted or stored’.</p></li>
  <li><p>Accordingly, in order to establish whether the liability of a referencing service provider may be limited under Article 14 of Directive 2000/31, it is necessary to examine whether the role played by that service provider is neutral, in the sense that its conduct is merely technical, automatic and passive, pointing to a lack of knowledge or control of the data which it stores.</p></li>
  </ol>
</blockquote>

<p>The way Github creates/shows the contribution activity is in my opinion technical, automatic and passive. That means it is not liable, and that implies that the GDPR does not directly apply, unless data is unlawful, and someone notifies Github of that:</p>

<blockquote>
  <ol start="109">
  <li>The restriction on liability set out in Article 14(1) of Directive 2000/31 applies to cases ‘[w]here an information society service is provided that consists of the storage of information provided by a recipient of the service’ and means that the provider of such a service cannot be held liable for the data which it has stored at the request of a recipient of that service unless that service provider, after having become aware, because of information supplied by an injured party or otherwise, of the unlawful nature of those data or of activities of that recipient, fails to act expeditiously to remove or to disable access to those data.</li>
  </ol>
</blockquote>

<p>Surely the GDPR might be the reason data is unlawful. But you need a reason, in particular based on <a href="https://gdpr-info.eu/art-17-gdpr/" rel="nofollow noreferrer">Article 17 ("right to be forgotten")</a>. For example if personal data of a 12 year old child is processed without permission of it's parent. Without such a reason the legitimate interest of the repository owner will probably prevail (who wants to keep the git history complete).</p>

<p>Assuming that the GDPR applies (which would seem to be the case - regardless of where you are in the world based on the Github Privacy statement), then its arguable that you should be granted this if you have a valid reason in accordance with Article 21(6) of the GDPR which reads </p>

<blockquote>
  <p>"Where personal data are processed for scientific or historical
  research purposes or statistical purposes pursuant to Article 89(1),
  the data subject, on grounds relating to his or her particular
  situation, shall have the right to object to processing of personal
  data concerning him or her, unless the processing is necessary for the
  performance of a task carried out for reasons of public interest."</p>
</blockquote>

<p>(By my reading section 89 allows them to process this data after anonymising it)</p>

<p>Its also relevant to quote Githubs page on how to control your data which includes the data they collect about you -</p>

<blockquote>
  <p>"If you're already a GitHub user, you may access, update, alter, or
  delete your basic user profile information by editing your user
  profile or contacting GitHub Support. You can control the information
  we collect about you by limiting what information is in your profile,
  by updating out of date information, or by contacting <a href="https://github.com/contact" rel="nofollow noreferrer">GitHub Support</a>."</p>
</blockquote>
