united-states united-kingdom privacy gdpr
Data Protection Laws
<p>Some Co-workers of mine have been sending customer's personal information, that includes banking details through unsecured plaintext emails. This feels to me like it is definitely breaking laws/regulations but I am not sure what ones. This is going on in the US and in the UK</p>

<p>Is this an illegal practice?</p>

<p>EDIT: 
By unsecured email I just mean a normal email sent between employees over outlook, this is also used to send emails externally and there is no blocker for sending attachments to external emails if someone was to mistype an email address there is nothing to stop this being sent out.</p>

<p>By Plaintext I mean what is sent and received is readable, no hashing, etc. I don't know if this is encrypted decrypted on the send but as the email can be sent externally and internally I doubt it</p>

<p>Article 32 of the GDPR requires companies to adequately secure their data when handling data belonging to EU citizens. This also applies to cross border scenarios where data is transferred between countries.</p>
<p>Technically speaking, the GDPR doesn't set a standard for security: you don't <em>have</em> to encrypt your data, use AES or RSA encryption, or hash and salt passwords. It is your choice on how to secure your data, though the GDPR does mandate specific ways to secure data.</p>
<p>However, not doing so opens yourself up to two consequences:</p>
<ol>
<li><p>The <a href="https://edps.europa.eu/_en" rel="nofollow noreferrer">European data protection supervisor</a> is tasked with the enforcement of regulations. A company can be forced to increase their level security if a valid complaint alleging that inadequate security measures are in place is made</p>
</li>
<li><p>There is a significant amount of security risk, and <em>if</em> a data breach occurs, the GDPR allows authorities to levy heavy fines. Especially heavy fines may occur if it is found that the data was not securely stored.</p>
</li>
</ol>
<p>So the answer is:
A complaint to relevant authorities can force the company to take action, or they will lose access to the European market.</p>

<p>The GDPR requires the Data Controller (i.e. <a href="https://ico.org.uk/for-organisations/guide-to-data-protection/guide-to-the-general-data-protection-regulation-gdpr/key-definitions/controllers-and-processors/" rel="nofollow noreferrer">your company</a>) to <a href="https://ico.org.uk/for-organisations/guide-to-data-protection/guide-to-the-general-data-protection-regulation-gdpr/accountability-and-governance/" rel="nofollow noreferrer">put in place appropriate measures</a> for accountability. These will include appointing a Data Protection Officer (DPO) and implementing polices around the processing of personal data.</p>

<p>So you <em>should</em> be able to go to your DPO and ask to see the policies which describe the safeguards for emailing such data. These should in turn trace to the the <a href="https://ico.org.uk/for-organisations/guide-to-data-protection/guide-to-the-general-data-protection-regulation-gdpr/principles/" rel="nofollow noreferrer">GDPR Principles</a> and identify a <a href="https://ico.org.uk/for-organisations/guide-to-data-protection/guide-to-the-general-data-protection-regulation-gdpr/lawful-basis-for-processing/" rel="nofollow noreferrer">Lawful Basis</a> for every type of processing done with the personal data. This should also cover <a href="https://ico.org.uk/for-organisations/guide-to-data-protection/guide-to-the-general-data-protection-regulation-gdpr/international-transfers/" rel="nofollow noreferrer">international transfers</a> and <a href="https://ico.org.uk/for-organisations/guide-to-data-protection/guide-to-the-general-data-protection-regulation-gdpr/individual-rights/right-to-erasure/" rel="nofollow noreferrer">requests for deletion</a>. Deletion is likely to be particularly problematic: how do you delete someone from a spreadsheet attached to an email sent last year?</p>

<p>If you don't know where to find your policies or who your DPO is then either you don't have one or they aren't doing their job. Either way your company is not complying with the GDPR.</p>

<p>The GDPR applies to <a href="https://ico.org.uk/for-organisations/guide-to-data-protection/guide-to-the-general-data-protection-regulation-gdpr/key-definitions/what-is-personal-data/" rel="nofollow noreferrer">records kept in a filing system or database</a>, so an email which contains the bank details of a single individual is not necessarily covered by the GDPR (e.g. "Joe, can you add this guy to the customer DB..."). However if these emails contain spreadsheet attachments with tables of multiple customers then that would be covered.</p>

<p>Also it matters whether the customers are individuals or other companies. A company does not have the right to privacy that an individual has, so if all your customers are companies then you are probably in the clear, at least as far as the GDPR is concerned.</p>

<p>Having said all that, from a purely practical view the situation you describe sounds dangerously chaotic. Its only a matter of time until something goes badly wrong, and this could put your company on the wrong side of serious damages, regardless of whether you are in violation of the GDPR or not.</p>

<p>From my understanding, while not illegal, it is a very , not to be rude but, unintelligent practice. I can't speak on GDPR or foreign laws as an American. I've seen protected information sent via email, for example an email sent to my mother in which I was asked to look at, contained sensitive data and include an NDA covering the contents of the aforementioned email. That doesn't mean it is an intelligent action. Not to speak in an insulting tone, but I mean objectively. I noticed you stated the network is "internally". </p>

<p>If the email server is configured properly on the server, the practice should be as secure as storing the files on the company's computers and servers. If the data is as confidential as you say, chances are the email server is encrypted and possibly only transits mail to internal relays defined by either certificate validity or whitelists. This would be the same if everyone at the company used something like FTP to connect to remote storage instead. </p>

<p>If you mean cleartext as in the emails content look like this post I'm writing, that could be misleading. Cleartext is referring to the underlying data. I may be confusing something, but I don't know your technical knowledge, so I figured I'd make this point. Just because the text appears normal client-side, most email servers that are properly configured use encryption for transferring data via relays, securing the data from client to server, just like HTTPs.</p>

<p>Your question is a little confusing, since you say "to customers" and "internally". Internally means it says all within the private company network. However, saying it is sent to customers makes me think it is send externally, to addresses like "human@gmail.com". If you do mean that the data is sent externally, then while I don't believe it is illegal, it is quite irresponsible and (not to be rude) stupid. Companies like Google are well known for the fact that they read every bit of data send and received by their users, including these emails containing sensitive data.</p>

<p>Your question in terms of technical specificity makes it hard to answer. If you are concerned about the security of information in transit, it would be smart to bring it up with the technical department. How the underlying systems are configured for a purely internal network is important. If the emails are send externally, then I strongly am against sending sensitive data via email. Instead, store the data on a secured server, and send a link to the user, so that they may click it, on the server be authenticated and have their identity validated, then present them with the information.</p>

<p>Please reply to me if I misunderstood your question or such, and I'll try and append to my response.</p>
