@kingannoy If only it were that simple...most of my clients chose to work toward compliance, but some took this tack. They weren't (and aren't) crazy, and there's nothing wrong with blaming the EU for making this choice. It has consequences - some they'll like (fewer cookies) and some they won't (further neutering the possibility of a European Silicon Valley). This one falls somewhere in between.
Silicon valley got you Trump, I'm glad we (the EU) are trying a different tack 😉
@kingannoy Also fair. Our side of the pond may well be too hands-off, and that produces some good and some bad consequences. On the whole, I'd take Silicon Valley over GDPR, but I fully admit my American bias in that judgment. It's totally reasonable to come down on your side. My point was that the heavy-handed EU approach *also* produces some good and some bad consequences., and I think it'd be disingenuous to pretend GDPR has no downside.
I could understand your argument if we were talking about a company has a reason for handling private data, like say, Fit Bit. And if they said something like: "We got caught with our pants down, we'll be back with you as soon as we figured it out".
Instead it's a company with no excuse for gathering anything but your address, low-key insulting our government. They aren't crazy, they are the target of this law and I love their precious little snowflake response.
@kingannoy I think that's a fair distinction, but I'm not sure it necessarily supports that side of the argument. There's something inherently fair about expecting fitbit or google or facebook to handle personal data in a sophisticated, accountable manner. Should we treat a clothing company the same way? That raises one of GDPR's other unintended consequences; the parties it benefits most are the ones it seeks to constrain (by disproportionately affecting less sophisticated competitors).
@kingannoy In actual dollars-and-cents terms, putting up a blocker like this is a net gain compared to spending the resources to achieve full GDPR compliance for many US companies. They just don't sell enough of their products/services in Europe to justify the transaction cost and additional risk.
That is because the negative externalities are never connected to the companies. If companies were held accountable for the damage all this stored data does when (not if) it leaks, they would think twice about hoarding it.
I really like @doctorow comparison to a oily rag business. It is inherently dangerous to hold on to all this data. These companies can only profit from it because those dangers will never hit them but only their customers.
So I understand that it's in this companies best interest to just not do business in the EU. In dollars-and-cents terms it's better for them if they can keep being as un-responsible with their customers' data as they want. They prefer it if those possible negative externalities don't get connected to them.
Totally reasonable free market response.
A clothing company shouldn't have any trouble adhering to the GDPR because they shouldn't be hoarding any data.
How hard can it be to make you database tables for customer addresses and for your mailing list compliant?
I don't think that is hard enough to warrant their response. That is why I conclude they must have been hoarding all data they could find on their customers, and made that such a ingrained part of their business that it's impossible to stop.
It's as if a physical store would say something like:
"We have to close our store. We can't comply with these health and safety standards and getting our building up to the fire code is just too much effort. So sorry... Blame your government (no really)"
@kingannoy Your basic argument is correct. There are a few wrinkles that you may not fully appreciate. First, it's important to separate liability and preemptive regulation as legal levers. You're absolutely right about the negative externalities that a lack of liability has created for companies in this space, but that doesn't mean you necessarily *also* need to tell the company how to store its data in the first place. This is how products liability works (when it works).
@kingannoy Second, GDPR requires dramatically more than complying with best practices, especially for foreign companies. It is not as simple as "privacy good, ergo GDPR good." It is *intentionally* vague, requires foreign entities to submit themselves to the personal jurisdiction of European countries (viz a viz the data transfer mechanisms), and in some cases prohibits what local state or federal laws over here require (and the exceptions for legal compliance only covers EU law).
A Mastodon instance for info/cyber security-minded people.