UK - Privacy Policy requirements for website with no tracking
<p>Essentially I run a website which is a microblog for anyone to use. The user who creates the content does so on one domain which requires login, stores a cookie etc..</p>
<p>The reader (user) of the blog content does so on a separate domain which <strong>does not</strong>:</p>
<ul>
<li>Attempt to set cookies or store any data outside of the page session such as <code>localstorage</code>.</li>
<li>Utilise any analytics trackers from any party.</li>
<li>Host advertisements either in the form of personalised or otherwise.</li>
</ul>
<p>The reader's entire interaction is with the website itself. It is however served through a CDN which keeps logs for a short period of time to prevent DDoS attacks and other abuse which comes under recital 49 of GDPR:</p>
<blockquote>
<p>The processing of personal data to the extent strictly necessary and proportionate for the purposes of ensuring network and information security, i.e. the ability of a network or an information system to resist, at a given level of confidence, accidental events or unlawful or malicious actions that compromise the availability, authenticity, integrity and confidentiality of stored or transmitted personal data, and the security of the related services offered by, or accessible via, those networks and systems, by public authorities, by computer emergency response teams (CERTs), computer security incident response teams (CSIRTs), by providers of electronic communications networks and services and by providers of security technologies and services, constitutes a legitimate interest of the data controller concerned. This could, for example, include preventing unauthorised access to electronic communications networks and malicious code distribution and stopping ‘denial of service’ attacks and damage to computer and electronic communication systems.</p>
</blockquote>
<p>In my privacy policy I state to the user that no cookies, analytics trackers or PII is collected other than by my CDN provider for the above purpose.</p>
<p>I can't offer an opt-out to tracking as none takes place. Log files that are available to myself from the CDN are kept for three days and the IP address is entirely redacted i.e. <code>0.0.0.0</code>. Is there anything specifically that I do have to mention to the reader if I am not collecting any data other than that required to serve the website to them?</p>
<p>Note: The website is created and hosted within the UK but has a worldwide audience. The majority of readers are within the US.</p>
<p><em>I have done a few days of searching around on top of my existing understanding of GDPR but can't find much information in the case of not collecting information. And <a href="https://law.stackexchange.com/a/49449/11544">this answer</a> covers the user of CDN's specifically.</em></p>

<p>Sounds like you're pretty much set.</p>
<p>Serving a website inherently involves processing of personal data. You have minimized this processing to what you consider the minimum, taking into account your obligation to ensure the security of processing. Your security measures are likely to be covered by an overriding legitimate interest (taking into account Recital 49). Offering an opt-out is likely not appropriate since it would defeat the purpose of these security measures. That is, the data subjects still have a right to contact you and object to the legitimate interest per Art 21, but the objection can most likely be denied.</p>
<p>All your website visitors are protected by the UK GDPR because you, the data controller, are in the UK (GDPR applies to all your processing activities per Art 3(1)).</p>
<p>From the scenario you describe, two GDPR compliance obligations have to be pointed out.</p>
<ul>
<li><p>You are still required to provide a privacy notice per Art 13 GDPR. However, since your processing activities are fairly limited, that notice will be comparatively short. Read the <a href="https://ico.org.uk/for-organisations/guide-to-data-protection/guide-to-the-general-data-protection-regulation-gdpr/individual-rights/right-to-be-informed/" rel="nofollow noreferrer">ICO's guide on the right to be informed</a> for further details and a checklist. I strongly recommend using that checklist and/or just reading Art 13 and Art 15 GDPR instead of relying on some privacy policy generator.</p>
</li>
<li><p>You are serving the website as a CDN. Presumably, this CDN acts as a data processor on your behalf. You would then need to make sure that an appropriate contract is in place that binds them as your data processor, in line with Art 28 GDPR. Again, the <a href="https://ico.org.uk/for-organisations/guide-to-data-protection/guide-to-the-general-data-protection-regulation-gdpr/accountability-and-governance/contracts/" rel="nofollow noreferrer">ICO has guidance on such contracts</a>.</p>
</li>
</ul>
<p>To the degree that the use of the CDN involves data exports into other countries, you would also need to assess whether this is a “restricted transfer”, possibly requiring further protections. The <a href="https://ico.org.uk/for-organisations/guide-to-data-protection/guide-to-the-general-data-protection-regulation-gdpr/international-transfers-after-uk-exit/" rel="nofollow noreferrer">ICO has a page about international transfers</a>, though you can skip the Brexit-specific parts. Note in particular that the United States are not covered by an “adequacy decision” and that the old Privacy Shield is invalid. If you are making a restricted transfer that is not covered by an existing adequacy decision, you will have to make a transfer risk assessment. The ICO does not publish guidelines for such an assessment, but an <a href="https://iapp.org/resources/article/transfer-impact-assessment-templates/" rel="nofollow noreferrer">EU GDPR transfer impact assessment template</a> is available from the IAPP. If the assessment shows that the risks of the transfer are sufficiently small, the transfer can be made on the basis of standard contractual clauses (SCCs). In 2022, the UK has published a new International Data Transfer Addendum (IDTA) to augment/replace the old EU SCCs, though the EU SCCs remain valid for a transition period.</p>

united-kingdom gdpr privacy