Skip to content

GDPR and email: what is and isn't allowed?

Emailing personal data is allowed, if you do it carefully. Seven common mistakes, such as CC instead of BCC, and what to do after a data breach.

Brick wall with rows of security cameras, one column of them white

Photo: Lianhao Qu via Unsplash (unsplash.com/photos/LfaN1gswV5c)

Almost every organisation emails personal data every day: a CV, an invoice, a medical report, an overview with customer details. Is that allowed under the GDPR? Yes, if you do it carefully. In this guide you will read what the GDPR requires, which mistakes happen most often and what to do if something goes wrong anyway.

This article gives a general overview and is not legal advice.

What does the GDPR require for email?

The GDPR does not prohibit emailing personal data. It does require you to take appropriate technical and organisational measures to protect that data. What is appropriate depends on the risk: the more sensitive the data and the greater the consequences of a leak, the stronger the security needs to be.

The general principles of the GDPR also apply to email:

  • Purpose limitation: use personal data only for the purpose you collected it for.
  • Data minimisation: don’t email more data than the recipient needs.
  • Confidentiality: make sure only the intended recipient can read the data.
  • Storage limitation: keep data no longer than necessary, in mailboxes too.

Ordinary and special categories of personal data

Not all personal data is equally sensitive. The GDPR recognises special categories of personal data: data about health, racial or ethnic origin, religious or philosophical beliefs, political opinions, trade union membership, genetic and biometric data, and data about a person’s sex life or sexual orientation. Stricter rules also apply to criminal records, and in many countries to national identification numbers (such as the Dutch citizen service number, BSN).

For this data the bar is higher. If you email it, encryption and verification of the recipient are the obvious choice.

Seven common mistakes

1. CC instead of BCC

If you put several external recipients in the CC field, you share every email address with everyone. That is a data breach: the addresses end up with people who are not allowed to see them. It becomes even more painful when the group itself says something about the recipients, such as the clients of a single care provider.

2. The wrong recipient

Autocomplete in your email program makes it easy to pick just the wrong person or organisation. A message with personal data sent to the wrong recipient is also a data breach.

3. Emailing sensitive data without protection

Medical data, a copy of an identity document or a national identification number in an ordinary email: an ordinary email offers no guarantee that the message is encrypted in transit, or that only the right person reads it. For data like this, use encryption and, where necessary, verification of the recipient.

4. More data than needed

Forwarding a full export from the customer system when the recipient only needs one line. Or forwarding a long email thread with all the earlier messages still in it. Send only what the recipient really needs.

5. The password in the same email

A protected attachment with the password in the same message, or in a second email to the same address, adds little protection. Anyone who intercepts or receives the email by mistake has both.

6. Work email to a private address

Forwarding personal data to a private address or a free email or file-sharing service, to carry on working at home, takes it outside your organisation’s view and security.

7. Security as the employee’s choice

Many solutions leave the decision to secure a message to the sender. Anyone who forgets the button or picks the wrong level still sends the email unprotected. However good the solution: if security is a choice, it will sometimes be skipped.

Gone wrong anyway? How to handle a data breach by email

  1. Limit the damage. Ask the unintended recipient to delete the message and not to forward it.
  2. Record the data breach. Every data breach belongs in your internal breach register, even if you don’t have to report it.
  3. Assess the risk. What data is involved, about how many people, and what could the consequences be for them?
  4. Report it if you have to. If the data breach poses a risk to the people concerned, report it to the supervisory authority (in the Netherlands the Autoriteit Persoonsgegevens) within 72 hours of discovering it. If the risk is high, you also inform the people concerned themselves.
  5. Prevent it from happening again. Work out which measure would have prevented the breach, and take it.

Your data protection officer (DPO) or privacy officer can help you with the assessment.

How do you prevent mistakes?

Many of these mistakes are human. That is why it works best when security does not depend on what an employee chooses at the moment of sending:

  • Central policy: the organisation decides which security level applies, for example per address, not the individual employee.
  • Encryption and verification: sensitive messages go out securely and, where necessary, can only be read once the recipient has verified their identity.
  • Checking the content: Data Loss Prevention recognises sensitive data in messages and attachments, and intervenes before the message leaves the organisation.
  • Awareness: keep reminding staff of the risks, even when technology catches a lot.

Do you send newsletters or other mailings? Then also read what the GDPR requires for email marketing.

Secure email without an encryption button

With SecuMailer your organisation sets security centrally. Staff email as they always do, from their own email program, and recipients read the message in their own inbox. If verification is needed, the recipient receives a text message code, for example. That is how SecuMailer helps you comply with the GDPR, without security being a choice.

Read more about Secure Email

← All blogs

Simply secure

Curious what SecuMailer can do for you?

Book a free demo