About GDPR, a compilation
Updated 2018-04-14
GDPR Key Changes
- Breach Notification
- Right to Access
- Right to be Forgotten
- Data Portability
- Privacy by Design
- Data Protection Officers
https://www.eugdpr.org/key-changes.html
Wikipedia
https://en.wikipedia.org/wiki/General_Data_Protection_Regulation
GDPR Requirements in Plain English
This is maybe the best GDPR article I have found:
[https://blog.varonis.com/gdpr-requirements-list-in-plain-english/] (https://blog.varonis.com/gdpr-requirements-list-in-plain-english/)
GDPR – A practical guide for developers
Overall, the purpose of the regulation is to make you take conscious decisions when processing personal data. It imposes best practices in a legal way. If you follow the above advice and design your data model, storage, data flow, API calls with data protection in mind, then you shouldn’t worry about the huge fines that the regulation prescribes – they are for extreme cases, like Equifax for example.
https://techblog.bozho.net/gdpr-practical-guide-developers/
Smashing Magazine
What GDPR adds is new definitions and requirements to reflect changes in technology which simply did not exist in the dialup era. It also tightens up requirements for transparency, disclosure, and process: lessons learned from 23 years of experience.
https://www.smashingmagazine.com/2018/02/gdpr-for-web-developers/
Techcrunch
Another major change incoming via GDPR is ‘privacy by design’ no longer being just a nice idea; privacy by design and privacy by default become firm legal requirements.
https://techcrunch.com/2018/01/20/wtf-is-gdpr/
Noncomplience
In the run-up to May 2018, you will hear a lot about the penalties and fines that can result from a failure to comply with GDPR. These warnings, sadly, are becoming more exaggerated by the day. (Funnily enough, the direst warnings are coming from people trying to sell you a GDPR compliance solution. Responsible data protection professionals have even adopted the hashtag “#GDPRubbish” to showcase the worst of it.)
https://www.connected-uk.com/gdpr-for-business-owners-senior-executives/
Facebook and Cambridge Analytica
However, what is particularly interesting for marketers, is that this scandal feels almost like a movie trailer for the upcoming GDPR legislation in May. This gives us a real working answer to the much-asked GDPR question of ‘how much do you think this will affect consumer behaviour on the whole?’ http://www.thedrum.com/opinion/2018/03/22/why-the-facebookcambridge-analytica-scandal-the-perfect-consumer-storm-ahead-gdpr
Every platform vendor has this same dilemma. The need to drive revenue and monetize their data against the need to protect the data. And we should also expect the typical reaction sequence that Facebook had when such a breach is exposed—Ignorance followed by Denial followed by Outrage. https://www.csoonline.com/article/3263438/privacy/gdpr-is-more-important-than-ever-the-cambridge-analytica-facebook-meltdown.html
GDPR-guiden - verksamt.se (in Swedish)
För att underlätta för dig som har ett mindre företag har verksamt.se tillsammans med Datainspektionen tagit fram den här guiden som tar upp det viktigaste grunderna i dataskyddsförordningen.
https://www.verksamt.se/driva/gdpr-dataskyddsregler/gdpr-guiden
MailChimp and GDPR
https://blog.mailchimp.com/getting-ready-for-the-gdpr/ https://blog.mailchimp.com/gdpr-tools-from-mailchimp/
Slack and GDPR
GDPR Sentry and you
We’re applying it globally for ourselves, instead of just focusing on Europe. All customer data (and all our own much less significant marketing data) is treated in a way that conforms with GDPR.
https://blog.sentry.io/2018/03/14/gdpr-sentry-and-you
Paddle
Because we believe that the changes that GDPR introduces will contribute to making customer data safer online, we will treat customer data from non-EU residents the same way we treat EU residents.