Privacy in ten minutes
When they hear the word GDPR, most people think of a privacy statement on the website, a cookie banner or a document somewhere in the legal department. All of that exists, but it is not where things go wrong.
Things go wrong in ordinary actions. An email with a customer list that goes to the wrong Chris. A shared folder with staff data that the whole company can open. A phone call in which someone poses as a family member and gets hold of an address. An export file that has been sitting in the Downloads folder for three years. Nobody meant any harm, and yet these are all data breaches.
This course is about those actions. You don't need to know any articles of law and you don't need to write any documents. You learn to recognise where people's data sits in your work, what you do and don't do with it, and what to do when it goes wrong anyway.
What the GDPR is
The General Data Protection Regulation has applied across the whole European Union since May 2018. It protects everyone whose data an organisation holds. Think of customers and members, but also job applicants and the organisation's own staff.
The law is long, but the core fits on a card. An organisation may only use people's data when there is a good reason for it. It collects no more than it needs for that purpose, and keeps it no longer than necessary. It protects it well, it is open about what it does, and people can ask what is known about them.
Each country has a data protection authority that supervises this. In the Netherlands that is the Dutch Data Protection Authority. It can impose fines, but for most organisations the fine is not the biggest risk. A customer who gets a letter saying their data ended up with someone else often doesn't come back.
Why it goes wrong with employees, not with policy
An organisation can have everything neatly on paper and still have a data breach every week. Data protection authorities receive many thousands of breach notifications every year, and a large share of them have nothing to do with hackers. They are about data that ended up with the wrong person: an email, a letter, an attachment.
That is not because people are careless. It is because work moves fast and the dangerous actions look exactly like the ordinary ones. An email to the right Chris and an email to the wrong Chris take the same click. Sharing a folder with your team and sharing it with anyone who has the link sit in the same menu.
That is why the employee makes the difference. Policy says what should happen; you are the one who presses Send.
What the organisation does, and what you do
Responsibility for the data lies with the organisation, not with you personally. The organisation should record which data it holds and why, make agreements with suppliers who process data on its behalf, and have a route for requests and data breaches. In lesson 1.3 you see exactly what that means and how to find out how it is arranged where you work.
Your part is smaller, but it is the part where things go wrong most often. You handle what you're working on with care and share no more than necessary. You clear out what can go. And you report it when something goes wrong. That last one above all: a mistake you report the same day can almost always be fixed. A mistake you keep quiet about can't.
- Think back to your last working day, or keep track of what you do for an hour today.
- Write down three moments when you did something with a person's data. For example an email with a name in it or a customer file you opened.
- Next to each moment, note what could have gone wrong. A wrong recipient? Someone looking over your shoulder? A file left somewhere it didn't belong?
- Keep that list. In lesson 5.3 you use it for your own privacy check.
Stuck?
- I don't work with customer data, so this isn't about me. If you work with colleagues, you work with personal data. Think of the rota, leave requests and sick reports. Lesson 1.2 shows how much falls under it.
- I can only find three moments in a whole day. Then you are probably only noticing the obvious cases. Also look at emails with names in the signature, at the CRM, at your calendar and at notes you make during a conversation.
- Isn't this mainly something for the IT department? IT takes care of the technology: passwords, backups, security. But most data breaches are not about technology. No security system stops an email to the wrong recipient.
- Can I be fined personally? The GDPR is aimed at the organisation, not at the individual employee who makes a mistake. What is expected of you is that you work carefully and report a mistake.
- Name, in your own words, three things the GDPR asks of an organisation.
- Why are many data breaches not about hackers? Give an example from your own work.
- Where does responsibility for the data lie: with you or with the organisation? What is your part, then?
- Why is a mistake you report the same day better than a mistake you quietly fix?