Some smaller companies and lower-profile groups within big companies are going to need more time to sort this out, and some may decide it's not worth the risk of the massive fines no matter how compliant they think they are and will block European users. Nobody knows how aggressive regulators will be in enforcing this so far, nor is their any precedent for how the law will be interpreted by actual courts. Calling people incompetent isn't going to change that.
This is one of the negative consequences of enacting complex regulation targeted mostly at giants like Facebook and Google and then applying it to every side project and business in the entire world no matter how big or small. Sorry.
Lower profile groups within big companies are probably most likely to shut off their services to European users because they have the cautious legal departments of the large company without the important profit center designation which would make compliance a priority.
Who cares? That's not a factor in whether or not you should comply with the law.
> Lower profile groups within big companies are probably most likely to shut off their services to European users because they have the cautious legal departments of the large company without the important profit center designation which would make compliance a priority.
Well, that may be their strategy but it won't work because it is the company that is violating the law, not the lower profile group.
speaking generally here, you know laws aren't always right? we had plenty bad laws to draw from to challenge this particular point, from racial to abortion laws.
gdpr isn't as draconian as these but still has plenty trash in it between the vague wording, the moving target 'state of the art' represents and the weird requirements and absurd implications of the 'right to be forgotten'.
It's the law, it was created by a democratically elected body. Racial and abortion laws are on a different plane altogether, and are not typically the playground of globally acting corporations.
I work in a company that was acquired and we're still our own legal entity. Would our owner be affected if we violate GDPR?
Unlikely. "Instapaper Holdings, Inc." is right in their footer.
Make up your mind.
And this is exactly why this is such a shitshow. Stop attacking people who haven't complied because small developers have other things rather than trying to figure out whether they have to redo their logs if a user asks their data to be deleted. This is almost bullying behavior.
Yep.
> And now you are advocating that they should have already complied with GDPR given its impact!
Obviously yes, because today the law becomes enforceable. Not having done the required work is just plain dumb.
> Make up your mind.
I made up my mind well over a year ago, spent the time required to be compliant (a couple of days) and that was that. Instapaper being as small as it is would not have had to spend more time than that unless they are doing something they shouldn't be doing, are unable to plan or changed tactics in the last 2 days. After all, if they weren't going to make the deadline they had a very long time to announce that, instead they announce it the day before the law becomes enforceable. That's just not ok. At a minimum they should have had their export facility up and running.
> Stop attacking people who haven't complied because small developers have other things rather than trying to figure out whether they have to redo their logs if a user asks their data to be deleted.
I suspect you are in the same boat?
> This is almost bullying behavior.
Right. Well, sorry, it really isn't, it's the perspective of someone who has been in business for a very long time and who feels that the GDPR addresses some fairly urgent matters. Companies have been running roughshod over users' privacy rights for decades and it is one of the worst things to come out of the internet. The level of tracking and data brokering that is going on is utterly disgusting.
If you weren't doing anything you shouldn't be doing the GDPR is going to be a pretty simple affair if you're a small company. Larger companies will have some more work but have more resources.
It surprises me how much this community tolerates such combative cluelessness.
Did you start working on compliance in a timely manner or did you become aware of this a few weeks ago?
Does your company have a clue about what it is doing in general?
Do you take a user centric approach to data ownership?
If those are all 'yes' then compliance is easy. If you don't care, do illegal stuff, are clueless or don't care about your users then compliance is going to be hard, that's what the law intends because those companies should change their ways.
For some reason he is such a fan of this legislation that he is willing to overlook its glaring problems. No objectivity there, I am afraid.
Oh my. Terribly sorry for putting up a political manifesto.
> Either self-interest or useful-idiot.
Take your pick. No third options? Such as a genuine desire to take some of the heat off for SMEs, of which I own several and participate in several others?
> For some reason he is such a fan of this legislation that he is willing to overlook its glaring problems.
Yes, I'm a fan of this legislation. I also was a fan of its predecessor and it's a joy to see companies that don't have their house in order make all kinds of panicked moves. I have a pretty good behind the scenes view of what goes on with respect to privacy abuse by corporations due to the nature of my work. Those companies that do illegal stuff, don't give a damn about their users and that in general are clueless (and which in turn increases the chances of their online properties being compromised) will be the ones that run into the 'glaring problems' The only thing that I see as troublesome with the law is the lack of reciprocity and enforcement across borders. The EU picked a complex and for really small companies expensive way to resolve that and that's something that I see as a real issue.
> No objectivity there, I am afraid.
I think you mean to say you don't agree with me.
There is nothing retroactive here.
I don't really see where the age of the data you store comes into play.
In fact that attitude goes exactly against what the law is trying to achieve in the first place.
I think this is an important realization for any regulator.
So you are not correct on #1.
"It was adopted on 14 April 2016, and after a two-year transition period, becomes enforceable on 25 May 2018."
Source: https://en.wikipedia.org/wiki/General_Data_Protection_Regula...
>And before that one there was another one.
Yes, but that was a different law. It required different things.
> Yes, but that was a different law. It required different things.
It actually required a lot of the same things, but because companies decided to ignore it it was revised.
how do you know that? i mean technically he says they re violating it today, just like we all did the past 2 years because it wasnt enforceable. what changes with their ban tomorrow?
Erase everything.
When you're told the highway near your house has a new speedlimit you can either obey the speed limit, use a detour (which will still be slower on account of it being longer) or you can take your car off the road in huff.
The first one is the only solution that makes sense.
I mean , knowing GDPR , i would guess at best the provision would be something like "a reasonably long amount of time but not long enough to be unreasonable based on appropriate considerations of data subject's patience"
I can imagine something to the effect of stopping further gathering of data (to stop digging the hole deeper), to give your users the option to request what is their right through some kind of form and to park those requests until you're done with the implementation and in the meantime give them continued access.
After all, the law already has a provision in it that you have 30 days to respond, and another 2 months after that if you are for some reason technically incapable and need an extension.
(1) you still hold the data, you are still required to comply with the law and cutting off access does not change that one bit.
(2) the period for a response is long enough that once you would receive requests you could handle them in time even if you processed them manually.
(3) you have been - or should have been - aware of all this for a very long time, either you failed at estimating the impact of the law or you do not know what you have or you changed strategies internally recently and now you're not going to be ready in time because you started way too late.
So in all, all you've managed to achieve with this action is to get the spotlight on you, and it is a 100% certainty that at least Instapaper will be solidly violating the GDPR come tomorrow.
If I were in your shoes I would use my designated representative to contact the authorities for guidance after explaining in detail what the problem is before I would let my end users pay the price for my own incompetence.