Does the data protection european regulation (GDPR) apply to processing information obtained from business cards and conversations?
<p>I work at a SME.
When we meet someone (either a potential customer or a potential partner) at an exhibition, meeting, conference, etc., we usually save that person's contact information and topic of interest, so that we can contact them later and maybe send them targeted marketing emails.</p>

<p>This information is usually provided orally or through business cards that we share.</p>

<p>We know that, as an SME, we don’t need to keep records of our processing activities because it's not our main activity and it's not a particularly threat to the individual rights and freedom (so we believe).</p>

<p>Do we need to do something in particular to comply with GDPR, such as letting people know that we will keep their contact info for certain purposes?</p>

<p>The material scope of the GDPR (Article 2) is limited to the processing of personal data (including mere storage) <em>by automated means</em> <strong>or</strong> <em>as part of a filing system</em>.</p>
<p>The question of whether your activity falls within this scope hinges on what you actually do with the data once you take possession of it. You have mentioned <em>saving</em> the contact information of people you have met at conferences, which could refer to simply retaining it for later use, or to the technological process of storing data in a computer. The former, if not done in any structured way (a filing system) would not fall within the scope of the GDPR. The latter, even if poorly executed, such as a photo stored on a business smartphone or a text document thrown onto your workstation's desktop, would always fall within scope as computerised data is processed &quot;by automated means&quot;.</p>
<p>When the contact information you receive identifies a specific person, as distinct from just a corporate switchboard number and company name for example, it is personal data. When you get that personal data from the person it identifies (data subject), and you're otherwise in scope, Article 13 is invoked, requiring you to provide a list of information, &quot;at the time when personal data are obtained&quot;, unless &quot;the data subject already has the information.&quot; This is known as <em>the right to be informed</em>. The requirements differ when personal data are not obtained directly from the data subject.</p>
<p>I would argue it is unreasonable to be expected to provide the information to the data subject over a cup of coffee or in a quick business card exchange, but if you start entering it into a spreadsheet or your CRM, you need to provide the required information, which may be as simple as a follow-up email thanking them for their time and letting them know you'll keep their contact details on file, along with a link to your organisation's privacy policy, assuming it covers this use, or if not, a specific privacy notice.</p>
<p>You will of course be required to comply with other requirements such as the principles of data minimisation and identify a lawful basis, maintain adequate security by implementing technical and organisational measures, hold contracts with any third parties who process personal data on your behalf, and have a process for upholding data subject rights and responding to requests to exercise them - among others - but you should already be doing that for your other processing activities unless exempt.</p>
<h2>Additional information</h2>
<p>Edits have been made as clarifications and questions were forthcoming.</p>
<h3>Email marketing</h3>
<p>You need to consider the applicable country's implementation of Directive 2002/58/EC as amended (&quot;ePrivacy Directive&quot;). For example, in the UK you could send such messages without consent to contacts at incorporated companies or public sector bodies, but would have required consent for sole traders, private individuals, or partners in an unincorporated partnership. In Ireland, you have an exemption to consent for existing customers who were offered the opportunity to opt <em>out</em> when their email address was collected, but must use the email address for marketing within 12 months. Each EU country will have a different implementation of the Directive. In the Netherlands, <a href="https://wetten.overheid.nl/jci1.3:c:BWBR0009950&amp;hoofdstuk=11&amp;paragraaf=11.1&amp;artikel=11.7&amp;z=2019-01-01&amp;g=2019-01-01" rel="nofollow noreferrer">Article 17 of the Telecommunications Act</a> implements Directive 2003/58/EC and thus provisions for direct marketing by email.</p>
<h3>Processing by automated means</h3>
<p>Processing by <em>automated means</em> refers to processing of personal data in electronic, rather than manual form. All electronic processing is within the material scope of the GDPR, while only manual processing that forms or is intended to form part of a filing system is.</p>
<p>Recital 15:</p>
<blockquote>
<p>The protection of natural persons should apply to the processing of personal data by automated means, as well as to manual processing, if the personal data are contained or are intended to be contained in a filing system.</p>
</blockquote>
<p>Art. 4(2):</p>
<blockquote>
<p>‘processing’ means any operation or set of operations which is performed on personal data or on sets of personal data, whether or not by automated means</p>
</blockquote>
<p><a href="https://www.ico.org.uk/" rel="nofollow noreferrer">ICO</a> guidance <em><a href="https://ico.org.uk/for-organisations/guide-to-data-protection/guide-to-the-general-data-protection-regulation-gdpr/what-is-personal-data/what-is-personal-data/" rel="nofollow noreferrer">What is personal data?</a></em>:</p>
<blockquote>
<p>The GDPR covers the processing of personal data in two ways:</p>
<ul>
<li>personal data processed wholly or partly by automated means (that is, information in electronic form); and</li>
<li>personal data processed in a non-automated manner which forms part of, or is intended to form part of, a ‘filing system’ (that is, manual information in a filing system).</li>
</ul>
</blockquote>

privacy gdpr european-union data-protection