From the consultants I have spoken with and looking at the issue for my own company. Depending on what your service does, the process of GDPR compliance can be incredibly complex and involve rewriting a significant percentage of your code. Even then, you may not be in the clear because it is up for unique interpretations in the courts of 28 distinct countries. It is, quite simply, a mess. Maybe it's one that will work out to users' benefit in the end, but that doesn't help the companies trying to serve them that don't have millions of dollars to spend on compliance.
There should be hardly any change needed as long as the service only gathers data that is required for it and users are willingly using the service.
The problem if for companies that do heavy identification of users against their will like in adtech or companies that gather and resell personal information.
You do not need to be a lawyer to understand GDPR, you merely need the ability to read, and have a few hours to devote to research. Implementing a policy that is compatible with GDPR is not hard. It does require some thought and some time and will need some training across your organisation. If you do not have a market in the EU then it need not worry you at all. Funnily enough, if you bin (or neuter) those social icons and a few .js thingies from your website you'll be well on the way. Now think about how you would like to be treated, personally ... yep - you'll be fine. No lawyers needed and certainly not seven figure sums for handwaving. You really can use research and common sense and some time, to do the job in house effectively.
I might politely suggest that it is a pretty good standard to work to anyway: it is designed to protect the privacy of individual people. I consider myself an individual and perhaps you do too.
And yet billions are being spent on exactly that - because it's an incredibly complex law that can indeed be subject to different interpretations in each country. I have been briefed on this point specific by lawyers in the EU for to whom we paid a fortune, only to decide that it was too risky to allow EU traffic.
It's not just a matter of taking away "a few .js thingies" as you put it.
The purpose of GDPR is protect individual's right to privacy - I doubt you can fault that. You and I are both individuals ...
Have you actually sat down with a copy of the GDPR a clear mind, and some really good coffee and bothered to read it? If you are arguing the toss with me based on something that someone else has told you then go away.
GDPR is designed to protect people - you and I if you like. I'm a fan of it.
You should take a look at this well reasoned blog post about why someone stopped selling their products in the EU - https://www.brentozar.com/archive/2017/12/gdpr-stopped-selli...
There are just far more issues here than you're acknowledging.
But people are arguing with you because you are all over this thread acting like it is the only business choice. Or that we all need to spend millions to make that choice. In truth, it is a risk management decision, not a legal one, because the legal answers are unknowns. You clearly are drawing this into the quadrant of both high likelihood and high consequences... which is fine, for you. But different organizations may have different answers, putting GDPR compliance into a different risk quadrant, and those are their own decisions to make.
If it costs 7 figures to hire consultants, either your business model was parasitic in the first place or your consultants are attempting to fleece you.
(if you don't believe me, email [email protected] and ask - I run the tech team, I'm not nearly as much of an expert on the rules as he is - and if you're emailing him to ask with no intention to pay us anything, that's fine, just make sure to blame me)
there are essentially no situations in which GDPR compliance should be particularly onerous. The principles are pretty simple, and while it will take some time until there is clarity on edge cases, most actions required should be straigtforward.
I’d be fascinated to know what product you build that is so inextricably tied to user data that it will cost “millions” to comply.
Then you obviously haven’t read the whole thing or had to comply with it.
It it possible that you’ve been fleeced by your consultants? You’ve notably avoided talking what you’re doing that would require onerous compliance, details of which would go at least part way towards substantiating our rather unbelievable ideas about the cost of compliance.
The people I’ve met who aren’t fall into three categories:
1. People who don’t know much about the rules and have concocted a distorted version of them
2. People who are running a business that relies on misuse of personal data and who will be directly affected
3. People who have some ideological or politicical viewpoint which generally opposes regulation.
I have encountered no situation where someone has been able to demonstrate to me a convincing case where GDPR compliance is onerous, or indeed more work than any best practices they should have already been following.
Where on Earth are you getting this number from? It sounds entirely fictional to me.
GDPR compliance for small services is a relatively straightforward process.