Currently taking clients

Week 2 — Legal basis

Part
3 of 10
Course
A six-week GDPR curriculum for small companies

Week 2

This week's super easy as well: We'll just look at the personal data you're processing and write down a few notes about it. That's it!

And What Notes Do We Add?

We'll ask a few questions and then write down the answers (we want to be able to show any auditor that we actually did this). For this, create a new Word or Google Docs document called GDPR Documentation. In there you add a first section with the title Processed Personal Data. That's where we'll keep our notes on all the personal data we're processing.

Add a first subsection named after what the personal data is that you're processing, for example:

GDPR Documentation
Processed Personal Data
Email addresses of people who subscribed to my newsletter

And under there we'll write down the answers to three questions: Where is the data processed? How bad would it be if anything happened to the data? And why do I process it?

GDPR Documentation
Processed Personal Data
Email addresses of people who subscribed to my newsletter
Where is the data processed?
On my website and in my CMS.
How bad would it be if anything happened to the data?
Lost
  • They couldn't get my newsletter anymore.
Modified
  • They couldn't get my newsletter anymore.
  • Maybe someone else ends up getting my newsletter instead.
Stolen
  • They might start getting spam mails.
  • Their email address might be submitted or used where they don't want it used.
Why am I processing it?
To send them the newsletter they signed up for.

To actually keep the data safe you need to think about how it'd impact the person whose data it is if anything happened to it. Otherwise you can't actually decide if you are doing enough to keep it safe.

How Do These Categories Work?

The Lost, Modified, and Stolen categories are the different things that can happen to the data. We just write down the different things we can come up with that could potentially happen. Just because the email address got changed doesn't mean that the new one is valid and someone else ends up getting those emails now instead. But it's a possibility.

This gives us an idea of the impact of any of those scenarios. If their email address somehow got deleted from your newsletter list, that's no big thing, they maybe miss a few emails. But they can still resubscribe, and everything's good. If their email address is stolen however, that'd be a bit worse: People don't enjoy getting spam mails.

A Flower Shop

Let's do another example: A contact form on a website for a flower shop.

In there, you have an email field and a text field where people can put in any kind of message.

GDPR Documentation (Flower Shop)
Processed Personal Data
[...other personal data you've documented...]
Data submitted on my website's contact form
Where is the data processed?
On my website and in my email account.
How bad would it be if anything happened to the data?
Lost
  • I wouldn't receive their message.
Modified
  • I might send my response to their message to someone else.
Stolen
  • They might start getting spam mails.
  • Their data might be sold for marketing purposes.
Why am I processing it?
So that people can contact me directly from my website.

Note that once again all the impacts are pretty minor.

A Doctor's Office

But what if the website is for a doctor's office?

GDPR Documentation (Doctor's Office)
Processed Personal Data
[...other personal data you've documented...]
Data submitted on my website's contact form
Where is the data processed?
On my website and in my email account.
How bad would it be if anything happened to the data?
Lost
  • I wouldn't receive their message.
Modified
  • I might send my response to their message to someone else.
  • I might misunderstand their medical issue.
Stolen
  • They might start getting spam mails.
  • Their data might be sold for marketing purposes.
Why am I processing it?
So that people can contact me directly from my website.

Here, the impact changes. It's still just a contact form, the things that could happen are approximately the same, but the impact is far higher: We're dealing with health data here.

In theory, people could enter health data into the contact form of a flower shop. But that never really happens. We can reasonably expect that for a flower shop, any contact request is related to buying flowers. But for a contact form on a website for a doctor's office it's not unreasonable to expect that they enter all kinds of health data: Their medical history, any current symptoms, or maybe just a lot of personal data relating to their body.

We'll return to this example next week. But for now, just go through all of your "Keep safe" entries and think about what the consequences of mishandling that data would be.

Remember: You don't have to go through all entries at once. The nice thing about this system is that as long as you continuously chip away at your list, you'll eventually process all of them.

What if I Don't Actually Need to Process That Data?

If you found any data that you're processing where there's no point in doing so, that's great! That means you have a super easy way of improving your GDPR compliance right now: Just stop processing it. Just be aware that you might be legally required to keep the data for some time, so make sure you're good on that front before you delete it.