This meme is just too true. What was once in vogue is now dangerous to touch. Handled carefully and competently, though, it’s of course pure gold! Data, I mean. Not asbestos. That’s only bad.

Technical GDPR and privacy compliance, the TL;DR version

Some tips to GTFO 🏃 of the worst “privacy dumpster fires” 🔥 🚒

Mikael Vesavuori
14 min readDec 28, 2020

--

To keep this as short as the TL;DR title promises, I cut out a section that was originally slated for this article. If you like this, then you may also like my short and slightly snarky piece “Some dumb objections I have heard when discussing privacy in the context of analytics”!

Note: Being the author of this article, I represent only myself. I am not a lawyer so don’t see anything here as strictly legal advice. However, being a professional in IT and software development, this is a question I’ve dealt with for a range of clients, small and large, some familiar and others less so with the legal side of GDPR. My expertise is primarily technical, so some of the “softer parts” including processes around DPOs will not be covered here. The perspective I represent is therefore from my own background and experience based on what I’ve gathered and learned. Always verify any claims and plans with your own legal representation!

It’s still hard to get things right when it comes to privacy and data today. Paradoxically — while laws and regulations are actually now becoming firmer and more widely discussed — niche interests, such as marketing and data brokering, combined with the threat of legal

--

--