Can I store the names of arbitrary business associates in my CRM system?
<p>I'm running an agency and I would like to store the names of employees of my client's companies to help me build client relationships.</p>
<p>For example, &quot;Gina works on reception.&quot;</p>
<p>Is this allowed within GDPR? Can I legally do this in the UK?</p>
<p>Why or why not?</p>
<p>Bonus question: If not, what are some ways that I could avoid GDPR breach while still making it easier for my employees to remember the names of random employees we encounter?</p>

<p>The GDPR does not outlaw such processing of personal data. It merely regulates how and for what purposes you can process personal data. In general, you can conduct any processing activity as long as it has a clear purpose and a legal basis.</p>
<p>Here, the purpose would likely be something like “conducting business with my clients” and the legal basis would be a “legitimate interest”. A legitimate interest always requires a balancing test that weighs your interests against the interests and rights of the affected persons. For example, can the affected persons reasonably expect such processing activities? In a professional setting, it can probably expected that business partners keep notes about contact persons so your intended processing could be fine.</p>
<p>The GDPR does impose some general constraints. There are general principles like data minimization and storage limitation – you should only collect data that is necessary for your purpose, and shouldn't store it for longer than necessary. You should think about appropriate technical and organizational measures (TOMs) to protect the processing activity, for example about how your CRM is hosted, how backups are made and how security updates are installed, who has access to the personal data, and how the people with access to the personal data can be trained. For example, such training might inform your employees that they can only use the data in the CRM for business purposes, but absolutely not for personal purposes like asking Gina from reception out for a date.</p>

<p>The <a href="https://law.stackexchange.com/a/79782/17500">answer by Amon</a> is quite correct. But I want to mention a few other  GDPR requirements.</p>
<p>When a Data Controller (DC) first acquires Personal Data (PD) about a Data Subject (DS), the DC must send the DS a notice containing  various information. This is required by <a href="https://gdpr-info.eu/art-13-gdpr/" rel="noreferrer">GDPR Article 13</a> if the data was acquired directly from the DS, and by  <a href="https://gdpr-info.eu/art-14-gdpr/" rel="noreferrer">GDPR Article 14</a> if the PD is obtained from some other source.</p>
<p>An Article 13 notice must include:</p>
<blockquote>
<ul>
<li>1(a) the identity and the contact details of the controller and, where applicable, of the controller’s representative;</li>
<li>1(b)the contact details of the data protection officer, where applicable;</li>
<li>1(c) the purposes of the processing for which the personal data are intended as well as the legal basis for the processing;</li>
<li>1(d) where the processing is based on point (f) of Article 6(1), the legitimate interests pursued by the controller or by a third party;</li>
<li>1(e) the recipients or categories of recipients of the personal data, if any;</li>
<li>1(f) where applicable, the fact that the controller intends to transfer personal data to a third country or international organisation and the existence or absence of an adequacy decision by the Commission, or in the case of transfers referred to in Article 46 or 47, or the second subparagraph of Article 49(1), reference to the appropriate or suitable safeguards and the means by which to obtain a copy of them or where they have been made available.</li>
<li>2(a) the period for which the personal data will be stored, or if that is not possible, the criteria used to determine that period;</li>
<li>2(b) the existence of the right to request from the controller access to and rectification or erasure of personal data or restriction of processing concerning the data subject or to object to processing as well as the right to data portability;</li>
<li>2(c) where the processing is based on point (a) of Article 6(1) or point (a) of Article 9(2), the existence of the right to withdraw consent at any time, without affecting the lawfulness of processing based on consent before its withdrawal;</li>
<li>2(d) the right to lodge a complaint with a supervisory authority;</li>
<li>2(e) whether the provision of personal data is a statutory or contractual requirement, or a requirement necessary to enter into a contract, as well as whether the data subject is obliged to provide the personal data and of the possible consequences of failure to provide such data;</li>
<li>2(f) the existence of automated decision-making, including profiling, referred to in Article 22(1) and (4) and, at least in those cases, meaningful information about the logic involved, as well as the significance and the envisaged consequences of such processing for the data subject.</li>
</ul>
</blockquote>
<p>An article 14 notice is similar, but some of the information to be included is different. It must include:</p>
<blockquote>
<ul>
<li>1(a) The identity and the contact details of the controller and, where applicable, of the controller’s representative;</li>
<li>1(b) the contact details of the data protection officer, where applicable;</li>
<li>1(c) the purposes of the processing for which the personal data are intended as well as the legal basis for the processing;</li>
<li>1(d) the categories of personal data concerned;</li>
<li>1(e) the recipients or categories of recipients of the personal data, if any;</li>
<li>1(f) where applicable, that the controller intends to transfer personal data to a recipient in a third country or international organisation and the existence or absence of an adequacy decision by the Commission, or in the case of transfers referred to in Article 46 or 47, or the second subparagraph of Article 49(1), reference to the appropriate or suitable safeguards and the means to obtain a copy of them or where they have been made available.</li>
<li>2(a) the period for which the personal data will be stored, or if that is not possible, the criteria used to determine that period;</li>
<li>2(b) where the processing is based on point (f) of Article 6(1), the legitimate interests pursued by the controller or by a third party;</li>
<li>2(c) the existence of the right to request from the controller access to and rectification or erasure of personal data or restriction of processing concerning the data subject and to object to processing as well as the right to data portability;</li>
<li>2(d) where processing is based on point (a) of Article 6(1) or point (a) of Article 9(2), the existence of the right to withdraw consent at any time, without affecting the lawfulness of processing based on consent before its withdrawal;</li>
<li>2(e) the right to lodge a complaint with a supervisory authority;</li>
<li>2(f) from which source the personal data originate, and if applicable, whether it came from publicly accessible sources;</li>
<li>2(g) the existence of automated decision-making, including profiling, referred to in Article 22(1) and (4) and, at least in those cases, meaningful information about the logic involved, as well as the significance and the envisaged consequences of such processing for the data subject.</li>
</ul>
</blockquote>
<p>Under either article 13 or 14, if the purposes(s) of processing change, an updated notice must be sent.</p>
<p>Each article lists exceptions, circumstances in which the notice may be omitted.</p>
<p>I believe that the notice requirement is more often overlooked or not complied with than the lawful basis requirement.</p>

united-kingdom gdpr european-union data-protection agency