Server side analytics events
<p>If I track a 'questionnaire started' event with a user's GUID for analytics purposes server side, could that contravene any UK data laws such as GDPR or the ePrivacy / cookie consent law?</p>
<p>The reason I ask is if users opt-out of anayltics cookies on the site - that doesn't seem to affect storing these server side, because it doesn't use a cookie.</p>
<p>So in this case I am:</p>
<ul>
<li>Respecting their cookie choice (cookie consent)</li>
<li>Not storing any personally identifiable information (GDPR)</li>
</ul>

<p>It may not be possible to identify a GUID as being associated with a specific named natural poerson.  But given information about a small number of specific individuals, it masy wel be possible to determine which of mthem a particular GUID is associatwed with. In any case, when the user logs back in, it is certainly possible to associate the use with the previous sessions and activities of mthe same user, thatmi8s the point of a tracking ID. That makeds the GUID an &quot;online identifier&quot; and makes any data associated with it in the Data Contreoller's database (DC's DB) Personal Dara (PS) and therefore protected under the GDPR.  This does <strong>not</strong> mean that the DC is forbidden to store and retain such data. It does mean thqt ther must be a <strong>lawful basis</strong> for such processing. This may be the Data Subjct's consent, but it may also be the DC's legitimate interest. However, this does mean that all such PD is subject to being disclosed in a data access request under the GDPR, or to being deleted at the request of the DS unless an exception applies.</p>

<p>I think your approach can be compliant, but it's going to be a bit tricky.</p>
<h2>Personal data has a broad definition</h2>
<p>The GUID is almost certainly personal data. Personal data is any information relating to an identifiable person. You should treat all the raw data collected via the survey as personal data. Even if there is no PII-style identifier like a name or telephone number, the GDPR has a very broad concept of identification.</p>
<ul>
<li>Even just being able to “single out” one person's records can count as identification. A GUID facilitates such singling out.</li>
<li>Information can also be personal data if the data subject can only be identified indirectly, by linking your information with other data or with the help of third parties. It doesn't matter whether you will actually perform such linking, only if it's reasonable that you would likely have the means to carry out identification in some scenario.</li>
</ul>
<h2>Any processing needs a legal basis</h2>
<p>To collect, store, or otherwise process personal data (such as survey responses, or analytics events), you need a legal basis.</p>
<ul>
<li><p>For example, you might have a <em>legitimate interest</em>, where you weighed your interests against the data subject's rights and interests and determined that your interests are more important. However, the GDPR provides some factors that you must consider during this balancing test (such as whether the data subject would reasonably expect this processing to occur). The data subject also has a right to object (opt-out), though the objection can be denied in some scenarios.</p>
</li>
<li><p>A more well-known legal basis is <em>consent</em> (opt-in). Consent can authorize nearly any processing, but you must provide enough information up front so that the data subject can make an informed decision. Consent is never the default, but always involves some statement or affirmative action from the data subject, such as clicking an “I agree” button. Withdrawing consent must be as easy as giving it in the first place.</p>
</li>
</ul>
<h2>Consent is needed for accessing or storing information on end user devices, unless strictly necessary</h2>
<p>Consent is widely used as a legal basis on the web because the ePrivacy directive mandates consent before setting or accessing information on the end user's device (such as cookies), unless this access/storage is strictly necessary for a service explicitly requested by the user. This consent requirement is completely independent from the question whether the information on the user's device is personal data. For example:</p>
<ul>
<li>Storing or accessing cookies for analytics purposes is not strictly necessary from the perspective of the user, and therefore requires consent – regardless of whether personal data is involved.</li>
<li>Storing or accessing session cookies might be strictly necessary for user-requested functionality to work, for example in order to connect pieces of a form that is split across multiple pages. Such cookies probably do not require consent.</li>
</ul>
<p>Note that “cookies” are merely the most common technology used for client-side storage of IDs, but ePrivacy is technology-neutral and likely covers all similar technologies, such as LocalStorage, hidden input fields in HTML, URL query parameters, and fingerprinting techniques.</p>
<p>Side note: you consider what happens when “users opt-out of anayltics cookies on the site”. That is not a good mindset towards GDPR/ePrivacy compliance, because analytics cookies require consent. Consent is always opt-in, never the default.</p>
<h2>Using the GUID for multiple purposes</h2>
<p>Things get more tricky when this access has multiple purposes, for example if a cookie with a GUID is strictly necessary for the site to work, but would also be used for analytics purposes.</p>
<p>I am not entirely sure how to resolve this in general. It could be argued that once the information is on the server, subsequent use of the information for different purposes would not be an additional “access” and would not require consent. If the information is also personal data, then Art 6(4) GDPR allows use of personal data for “compatible” purposes. On the other hand, such an argument would defeat the objective of the ePrivacy Directive.</p>
<p>But in this particular instance, things are easier: the legal basis for collecting information through your survey will almost certainly be <em>consent</em>. Consent must be specific to a processing purpose. Consent to data collection through the survey does not imply a legal basis for analytics, unless such metrics are integral part of the study's design (e.g. in a psychological study that measures reaction times, or in an UX study that must track user behaviour while they complete tasks). Given that consent to data collection for the study is specific to a purpose, it is unlikely that reusing the GUID for analytics purposes would be a compatible purpose.</p>
<p>Here, I think the appropriate approach would be as follows:</p>
<ul>
<li>Before subjects can take the survey, they are informed about the processing, in line with the GDPR conditions for consent and your Art 13 information obligations.</li>
<li>Participants are only admitted to the survey if they consent to this processing.</li>
<li>Separately, participants are asked if they optionally want to consent to collection of analytics data. Taking into account Art 7(4) GDPR, this is totally optional and participants can proceed regardless of their choice.</li>
</ul>
<p>Things might be different if you don't generate separate analytics events from the GUID, but just analyze partial survey responses, if such an analysis is compatible with the purpose for which these responses were collected. Mining your existing survey responses stored on your servers would only be subject to GDPR, not to ePrivacy's consent requirements.</p>

gdpr cookies