4 ms·
GDPR is difficult and costly to implement actually. But this should not be a reason to not have it.
by csunbird 6y ago
GDPR is difficult and costly to implement actually. But this should not be a reason to not have it.
- yardie 6y agoParts of GDPR is difficult to implement. And if your business model involves those parts then it would be costly, ie. costing you business. Other parts are infosec best practices, anyone who is security conscious could look at it and say, "yeah, that makes sense."
- jaybrendansmith 6y agoI'm interested to know what parts are costly? I found it relatively easy to implement processes for 'right to be forgotten' and 'emergency breach notification' as well as the default opt-out of personal data and marketing. Not trivial, but not particularly expensive. The rest is exactly as you say, infosec best practice that my industry required in any case. The only expensive part I could see is right to be forgotten, that is if you expect to get a lot of requests for your particular application's use case.
- yardie 6y agoI’m curious to know as well. I don’t know all parts of GDPR, just the parts I worked on. But others keep telling me it’s super complicated so I’m just assuming there are complicated bits I’m unaware of.