Week 4 — Documentation
- Part
- 5 of 10
- Course
- A six-week GDPR curriculum for small companies
Week 4
You're already through most of it! From here on out it's pretty smooth sailing.
Checking and Documenting Processors
As an example, let's say that you're a customer of mine. That means you have an entry like this in your list: Check Processor: That Antidefault guy
Start checking and documenting your Processors:
- Add a section in your GDPR documentation titled Processors.
- Take the first entry in your list and add it to your Processors section in your documentation:
You'll note that you'll only be able to review the Data Processing Agreement (DPA) if it's present, and that you can only tell if "sufficient guarantees" are given once you've reviewed the DPA. Let's do that!
The DPA review is always in the context of the data they're processing. If your Processor is processing data that falls into a special category you'll want to make sure that they're equipped to handle that data properly. In my case, I'd be mostly processing IP addresses and other data that's associated with people visiting your website. But if you want me to add pictures of your employees on your companies' website, then that's also personal data. And a contact form can have different levels of impact depending on what your business is.
I'd recommend reviewing the whole DPA, but a lot of those sections are standard texts that you'll see again and again as you look at more DPAs. There's a few sections that are of particular interest here though that change based on the business.
The first one is called "General Provisions and Subject Matter of the Contract". Lots of words in that title, but it's simple: It explains what the service is and what data is processed on your behalf, and why. In my case it just tells you that I'm processing data for the purpose of developing, maintaining and hosting your website. That includes any data you want me to put on your website, as well as any data I process when people visit it.
And then in the appendices you find the really interesting stuff:
Appendix A tells you a list of something called "Technical and Organizational Measures". People often just call them "TOMs". Those are the things your Processor does to make sure that your data is safe.
You can see that my physical access controls (A.1) are standard. My technical measures (A.2, A.5, A.6) are over the top (take a look at the Bonus chapter if you want to see how deep that rabbit hole goes). And A.4 shows that I make sure that my Subcontractors (Processors that I use to delegate some of the processing to) are up to the task as well, and are regularly reviewed.
And the best part? Processors also need to list in their DPA who they're subcontracting to. You can see that in Appendix B of my DPA: I use Hetzner (Germany), Github (United States), Amazon Web Services (Germany), and Proton (Switzerland).
But wait.. If Github is in the United States, isn't that against the GDPR?
Good question! Not necessarily. It doesn't really depend on the location, but what guarantees Github gives me. For that, a little bit of context what Github does:
My DPA states that I use Github for "Provision of a platform for managing and hosting software repositories and containers" - that's difficult to grok if you're not familiar with software development, so let me translate it for you: Github is a place where I can manage software (the code of your website) and containers (your website in a form I can put online).
In terms of personal data, that includes only things that are made public on your website anyways. But I've also reviewed their DPA, and it looks as solid as it gets: They have top-notch TOMs in place, and if they're legally forced to give out data they'll inform me about it. They're also certified according to the EU-US Data Privacy Framework (2025) [1]. For my purposes, they're perfectly safe.
Let's Continue
You've just reviewed my DPA, so let's mark it as such:
Are the guarantees I give sufficient for your purposes? That's up to you to decide. If so, document it as such and add a bit of an explanation:
And that's your first Processor checked! Now it's time to check the rest. Are you missing any DPAs? You might've already gotten them as part of your contract with a business, but if not, check their website or send them a mail. Then review them and make sure that they're up to the task.
What if a Processor Isn't up to the Task?
As you go through your list, add another entry to your List of Improvements for each Processor that isn't up to the task:
We'll tackle those next week.