I’ll try to be a bit more comprehensive this time and cover as many aspects of the regulation that concern developers as I can. And finally, I’m currently working on a project that (among other things) aims to help with covering some GDPR aspects (namely – secure audit logs). “before it was cool” ( protecting sensitive data, the right to be forgotten). I’m also a privacy advocate and I’ve been writing about GDPR-related stuff in the past, i.e. I’m familiar with the “legalese” and how the regulatory framework operates in general. Why am I qualified to do that? A few reasons – I was advisor to the deputy prime minister of a EU country, and because of that I’ve been both exposed and myself wrote some legislation. Instead, I’ll focus on what GDPR means for developers. I will not go into yet another “12 facts about GDPR” or “7 myths about GDPR” posts/whitepapers, as they are often aimed at managers or legal people. In this particular case, it applies to companies that are not registered in Europe, but are having European customers. The regulation is basically a law that must be followed in all European countries (but also applies to non-EU companies that have users in the EU). Especially if you are working in a big company, it’s most likely that there’s already a process for getting your systems in compliance with the regulation. The new European data protection regulation that applies practically to everyone.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |