Using GDPR against cold-call marketing emails
<p>I recently received a "cold-call" email from a salesman to my professional email address, <strike>which is in the form <code>firstname.lastname@company.com</code>. The <code>firstname</code> is a very formal version unlikely to be known by non-natives.</strike> We are both based in the UK.</p>

<ul>
<li>The address is assigned to me by my company</li>
<li>It's not uploaded to my personal Linkedin profile <em>(see edit below)</em></li>
</ul>

<p>The message seems personalized and doesn't have an <em>Unsubscribe</em> option.</p>

<p>The salesman claims to have found me through Linkedin. Normally this kind of thing earns a one-way express ticket to the Spam folder, but I'm wondering, can I use GDPR to request either</p>

<ul>
<li>how he found my address, or</li>
<li>that I be removed from his list?</li>
</ul>

<hr>

<p><em>edit</em> The message was sent to an alias of the form <code>easy-name.lastlane.company</code>, as opposed to <code>firstname.lastname@company</code> as I had originally thought. Outlook's interface didn't make it obvious that the alias was used. That one can indeed be easily guessed from my Linkedin profile, but is still not public.</p>

<p>Article 13(1) of <a href="https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32002L0058" rel="nofollow noreferrer">Directive 2002/58/EC</a> (in the UK implemented in <a href="https://www.legislation.gov.uk/uksi/2003/2426/regulation/22/made" rel="nofollow noreferrer">PECR 2003</a>) is about direct marketing. <a href="https://gdpr-info.eu/art-95-gdpr/" rel="nofollow noreferrer">Article 95 GDPR</a> explains the relation between that directive and the GDPR. The GDPR only applies if personal data is processed. </p>

<p>In a comment you confirm that the email address is like firstname.lastname@company.com. The <a href="https://gdpr-info.eu/art-68-gdpr/" rel="nofollow noreferrer">European Data Protection Board</a> has written a <a href="https://edpb.europa.eu/sites/edpb/files/files/news/icann_letter_en.pdf" rel="nofollow noreferrer">letter to the ICANN</a> (regarding <a href="https://en.wikipedia.org/wiki/WHOIS" rel="nofollow noreferrer">WHOIS</a>) where it clarifies if such an email address is personal data:</p>

<blockquote>
  <p>The GDPR does not apply to the processing of personal data which concerns legal persons and in particular undertakings established as legal persons, including the name and the form of the legal person and the contact details of the legal person. While the contact details of a legal person are outside the scope of the GDPR, the contact details concerning natural persons are within the scope of the GDPR, as well as any other information relating to an identified or indentifiable natural person.</p>
  
  <p>The mere fact that a registrant is a legal person does not necessarily justify unlimited publication of personal data relating to natural persons who work for or represent that organisation, such as natural persons who manage administrative or technical issues on behalf of the registrant.</p>
  
  <p>For example, the publication of the personal email address of a technical contact person consisting of firstname.lastname@company.com can reveal information regarding their current employer as well as their role within the organisation. Together with the address of the registrant, it may also reveal information about his or her place of work.</p>
  
  <p>In light of these considerations, the EDPB considers that personal data identifying individual employees (or third parties) acting on behalf of the registrant should not be made publically available by default in the context of WHOIS. If the registrant provides (or the registrar ensures) generic contact email information (e.g. admin@domain.com), the EDPB does not consider that the publication of such data in the context of WHOIS would be unlawful as such.</p>
</blockquote>

<p>So at least because an email address like firstname.lastname@company.com is used, it gets inside the scope of the GDPR. But as <a href="https://gdpr-info.eu/art-95-gdpr/" rel="nofollow noreferrer">Article 95 GDPR</a> explains, only for matters which have no obligations in <a href="https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32002L0058" rel="nofollow noreferrer">Directive 2002/58/EC</a>.</p>

<blockquote>
  <p><em>Can I use GDPR to request how he found my address</em></p>
</blockquote>

<p>As that is outside the scope of 2002/58/EC, you can use the GDPR to request this. See <a href="https://gdpr-info.eu/art-14-gdpr/" rel="nofollow noreferrer">Article 14(2)(f)</a>:</p>

<blockquote>
  <p><strong>Information to be provided where personal data have not been obtained from the data subject</strong></p>
  
  <ol start="2">
  <li><p>In addition to the information referred to in paragraph 1, the controller shall provide the data subject with the following information necessary to ensure fair and transparent processing in respect of the data subject: </p>
  
  <p>(f) from which source the personal data originate, and if applicable, whether it came from publicly accessible sources;</p></li>
  </ol>
</blockquote>

<p>Regarding your second question;</p>

<blockquote>
  <p><em>Can I use GDPR to request that I be removed from his list?</em></p>
</blockquote>

<p>The email you describe is clearly unlawful in respect to Directive 2002/58/EC, but also the GDPR would provide you with <a href="https://gdpr-info.eu/art-17-gdpr/" rel="nofollow noreferrer">the right to erasure</a>. So either way you can request to be removed.</p>

united-kingdom gdpr email