gdpr data
GDPR: Can I collect non-personally identifiable information?
<p>I'm creating a game that collects data in two ways: Unity Analytics for usage stats, and bug reports that sends me a report of an issue along with several files to help me diagnose the issue. However, GDPR is becoming a rather confusing problem for me.</p>

<p>The data collected with my bug reporter is:</p>

<ul>
<li>A hashed unique device ID</li>
<li>A game save file</li>
<li>System specs</li>
<li>Settings configuration</li>
<li>A short in game video recording (only shows the game window - not the users desktop)</li>
</ul>

<p>None of this is personally identifiable (I'm pretty sure) - I don't collect IPs, names, emails, gamer tags etc. As such, do I need permission from the user to collect this data? Would I still be GDPR compliant?</p>

<p>There are two relevant bodies of EU law to consider here.</p>

<ul>
<li>The GDPR covers processing of personal data. Personal data is any data where the data subject can be identified directly or indirectly.</li>
<li>The ePrivacy directive is also relevant, and covers how you may access and store information on the user's device. Directives are not directly applicable law. Instead every member state translates the directive into national law. In the UK, ePrivacy is implemented by PECR.</li>
</ul>

<h2>Is the data you collect personal data in the sense of the GDPR?</h2>

<p>Yes: that hashed unique device ID or a system-provided advertising ID likely is personal data, and any linked data would then be personal data as well. This is going to be the case in particular if you store user accounts on your server and can connect these bug reports to a user. Consider also whether the game save could include personal data, and whether the video clip could be analyzed to identify the data subject.</p>

<h2>Does this mean collecting this information in bug reports is forbidden?</h2>

<p>No, the GDPR doesn't forbid or allow anything outright. Instead, you should go through the compliance process. In a nutshell:</p>

<ul>
<li>determine the purpose of this processing, e.g. “fixing bugs”</li>
<li>find an Art 6 legal basis for this purpose, e.g. “Art 6(1)(f) legitimate interest” or “Art 6(1)(a) consent”</li>
<li>if the legal basis is legitimate interest, you must balance that interest against the data subject's interests</li>
<li>determine whether your compliance requirements include creating/updating your Records of Processing, or whether you have to write a Data Protection Impact Assessment</li>
<li>implement the processing in a manner that respects GDPR principles such as Transparency and Data Minimization</li>
<li>if the legal basis is legitimate interest you must implement an opt-out solution</li>
<li>if the legal basis is consent, you must request consent first in a manner that satisfies the Art 7 conditions for consent – and allow consent to be revoked easily</li>
<li>prepare to satisfy data subject rights:

<ul>
<li>information requirements per Art 13, usually done in the privacy policy</li>
<li>right to access, rectification, erasure, and data portability</li>
<li>right to object (opt-out) and to restrict processing</li>
</ul></li>
<li>be aware of your general requirements a data controller to process this data securely, e.g. use HTTPS connections to transmit bug reports, take steps to protect your own accounts (e.g. 2FA), and ensure you have a suitable contract with any data processors that act on your behalf, e.g. cloud providers or contractors</li>
</ul>

<p>I would question whether your bug reports really need to include a device ID. That isn't forbidden, it just complicates compliance a bit.</p>

<h2>And what about ePrivacy?</h2>

<p>The ePrivacy directive is known for its cookie consent requirements. But these consent requirements apply when accessing any information on the user's device, or when applying equivalent fingerprinting techniques. Your game save is not an issue because it is necessary for the game. But that device ID and other system information is more difficult.</p>

<h2>So what to do?</h2>

<p>Compliance isn't trivial, but certainly possible. You will likely process the bug reports under your legitimate interest, but might still have to collect consent for accessing a system ID due to ePrivacy.</p>

<p>Such a screen might look like this:</p>

<blockquote>
  <p>Oh no, the game crashed! Do you want to send a bug report to the developers? Your bug report will be protected as per our privacy policy (link).</p>
  
  <p>Your bug report will contain the following information: …</p>
  
  <p>Yes, collect system information and send bug report</p>
  
  <p>No, do not send bug report</p>
</blockquote>

<p>You could make an argument that a bug report can be sent in any case, and that you just need ePrivacy consent to collect useful system information. For example:</p>

<blockquote>
  <p>Oh no, the game crashed! When sending a bug report to developers, do you want to include extra system information (link to details) that helps fixing the problem? In any case, your bug report will be protected as per our privacy policy (link).</p>
  
  <p>Your bug report will contain the following information: …</p>
  
  <p>Yes, send bug report with extra system information</p>
  
  <p>No, send anonymous report</p>
</blockquote>
