Week 3 — Consent
- Part
- 4 of 10
- Course
- A six-week GDPR curriculum for small companies
Week 3
You're already improving your GDPR compliance by a lot! Last week, you documented and checked all the personal data you're processing, you thought about the potential consequences if things happen to the data, and you wrote down why you're processing it. You've also stopped processing data that you don't need to process.
By default, it's illegal to process people's personal data. There's six exceptions though (GDPR Art. 6[1]):
If they consent (a) the data subject has given consent to the processing of his or her personal data for one or more specific purposes;
If you need to process that data due to contractual obligations (b) processing is necessary for the performance of a contract to which the data subject is party or in order to take steps at the request of the data subject prior to entering into a contract;
If you need to process it to comply with legal requirements (c) processing is necessary for compliance with a legal obligation to which the controller is subject;
If it's necessary to protect someone's 'vital interests' (d) processing is necessary in order to protect the vital interests of the data subject or of another natural person;
If you do it in the public interest (e) processing is necessary for the performance of a task carried out in the public interest or in the exercise of official authority vested in the controller;
If it's important for your business (f) processing is necessary for the purposes of the legitimate interests pursued by the controller or by a third party, except where such interests are overridden by the interests or fundamental rights and freedoms of the data subject which require protection of personal data, in particular where the data subject is a child.
Now, for each "Keep safe" you'll have to decide what reason in GDPR Art. 6 [1] this falls under. And given that you've already written down the concrete reasons last week, it's just a matter of assigning it the appropriate letter.
Of the reasons up there you're most likely not going to use (d) and (e) at all. Most of your data processing is going to be done either due to them giving consent, you needing to fulfill a contract, you having to comply with a law, or you just having a pretty good reason to do so given your business.
If we take last week's examples, we can easily assign reasons to each of them:
The newsletter is not a legitimate business reason. It does help your business, but it sure does not outweigh people's interests here. It's (a), consent. That's why every newsletter signup form either has a checkbox that says "I've read the privacy notice and agree to have marketing stuff sent to me" or at the very least some text like "by signing up to the newsletter I confirm I've read the privacy policy and agree to you sending me marketing stuff".
Let's write down (GDPR Art. 6 para. 1(a)) next to the reason we've put down previously:
The contact form on a flower shop however is a legitimate business reason. The important part here is that you've actually thought about the impact the data could have on the person it relates to, and have documented having done so (that's part of why we're writing it down, but it'll also be important later). And if you still think your business interests outweigh that, you can write down (GDPR Art. 6 para. 1(f)) next to the reason, and you're good.
The contact form on the website of a doctor's office is different in that the impact is significantly higher. It's health data. It is a legitimate business reason to be contactable by patients, but it most likely does not outweigh the patient's rights. For that I'd highly recommend to ask for consent (in the form of a checkbox that has the patient explicitly confirm that they consent to the processing and have been informed according to GDPR):
On High Impact Personal Data
GDPR Art. 35 [2] is titled "Data protection impact assessment". I'll just quote paragraph 1 here, emphasis mine:
"Where a type of processing in particular using new technologies, and taking into account the nature, scope, context and purposes of the processing, is likely to result in a high risk to the rights and freedoms of natural persons, the controller shall, prior to the processing, carry out an assessment of the impact of the envisaged processing operations on the protection of personal data. A single assessment may address a set of similar processing operations that present similar high risks."GDPR Art. 35 [2]
You've already done so! In fact, let's pause here for a second and look back at that: How much effort was it really to collect and then think about those pieces of personal data? Not that much, right? But not doing it is a massive pitfall. Imagine for a second the auditor knocking on your door, and them seeing that you've put no thought into how you're processing health data or other risky categories.
But What's Considered Particularly Risky Data?
If you're following the process, you're already doing what you're required in this regard, particularly risky or not. But here's article 9 paragraph 1 "Processing of special categories of personal data", which outlines what's considered special. Emphasis mine:
"Processing of personal data revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, or trade union membership, and the processing of genetic data, biometric data for the purpose of uniquely identifying a natural person, data concerning health or data concerning a natural person's sex life or sexual orientation shall be prohibited."GDPR Art. 9 [3]
I'd flat out recommend to always get consent for these unless you have a really good reason not to. You can read more about that in GDPR Art. 9 [3].
On Consent
This one I really want to stress. Consent should be freely given, specific, informed and unambiguous. I mentioned above that one can often come across newsletter signup forms that just mention the privacy policy, and then write something like "by signing up, I confirm I've read the privacy policy and agree to have my data processed". That's implicit consent, and that works for most cases. But for data belonging to special categories you need explicit consent (GDPR Art. 9[3]). That generally means at least a checkbox, or preferably something like a signed form.
A side note: Consent can always be revoked. And it should be easy to do so. You can't just continue sending people your newsletter if they don't want that anymore.
Examples You've Probably Run Into Yourself
Here's a few situations you've probably run into yourself already:
Doctor's office The form you have to fill out at the doctor's office, when you visit the first time? They're processing health data, which as a special category needs explicit consent. They give you a copy of the privacy policy and make you sign the thing by hand for a reason.
Cookie banners Tracking cookies are used to track everything you're doing on the internet (Google Ads is the biggest culprit here). That's a business interest, both for Google and you, but it has since been deemed not to be outweighing the person's privacy rights. Hence, consent is required. Cookie banners are its own can of worms I'm not going to open right now, but be aware that they are regulated hard.
As a web developer I usually build the websites for my customers so that cookie banners are not required. That's pretty easy if you don't add any analytics. But if you do need analytics, there's ways to geolock that to outside the EU. I've written more about that on my blog (Proper Paranoia: Geolocking Analytics to Stay GDPR Compliant Without a Cookie Banner (2025)[4]).
Social Networks Take a look at any social network's sign-up page: You always find a privacy related checkbox somewhere on there.
Going Further
By now you know what personal data is processed by you and why.
But it's not always you who does the processing, is it? For example, you're probably not running your website completely on your own. If your website then processes personal data, and that website is run in the cloud (which means on other people's hardware) then they're processing personal data on your behalf.
Controller and Processor
If you are processing personal data for some purpose and are the one deciding how it's getting processed, you're called the Controller.
If someone else processes personal data on your behalf, they're called the Processor.
Yeah, it can be confusing.
Look at it like this: The Controller controls what data is processed, and why and how that's done. Controllers call the shots. Even if they don't delegate part of the processing to a third party, they're still the Controller, because they control the whole thing.
Everyone else who isn't calling the shots is just a Processor.
So, example: If you want to have your own website and you hire me to build and run it for you, then in regards to the data of the people visiting your website you're the Controller and I'm the Processor. You call the shots, I just do the processing. And anyone I hire to do processing of that data on my behalf (e.g. a cloud provider) is also just called a Processor.
But in regards to me processing your personal data in the context of us both doing business, I'm the Controller. I call the shots on how much data I need to process to make something happen, and how it's processed. Anyone I hire to do parts of that for me is again called a Processor.
The whole thing builds a chain. You can hire me to build your website and process data on your behalf, and I can hire people to do some of that processing for me.
You'll Have to Make Sure That I Do a Good Job
Delegating the processing to someone else doesn't relieve you from the responsibility that comes from processing that data. You'll have to make sure that whoever you hire is actually up to the task and GDPR compliant themselves. And they in turn have to make sure that whoever they delegate any data processing to is GDPR compliant themselves. That way the law makes sure that everyone involved is GDPR compliant.
But how do you do that? Well, there's contracts for that. If you're a customer of mine, you already got a Data Processing Agreement from me as part of the contract we made. Take a look at it. In there, I explain what data I'm processing, why I'm processing it, and who I'm delegating parts of the processing to and for what reason. That way you can check if I'm actually GDPR compliant myself.
You're legally required to have a Data Processing Agreement with anyone you're delegating the processing of personal data to. The good news is, anyone who wants to do business in the EU is required to have a Data Processing Agreement in place. Most businesses nowadays have them as part of their Terms of Service. For those who don't, you just have to ask.
Collecting All the Processors
Add Other businesses processing data on my behalf to your List of Things to Look Out For:
Whenever you remember that any personal data goes through the hands of another business, add them to the List of Improvements like this: