4 ms·
Tech company backend systems aren't independently owned/operated/engineered silos like a storage company's subsidiaries. Any notion of data having a geographic
by closeparen 9y ago
Tech company backend systems aren't independently owned/operated/engineered silos like a storage company's subsidiaries.
Any notion of data having a geographic home, unless specifically created to address a regulatory requirement, is a performance optimization. In any realistic architecture, there are are a million exceptions to "this Irish user's data is stored in Ireland": offsite backups, cross-datacenter requests within backend systems, offline analytical stores, queries, derived tables, etc. The same engineers who build and operate code for the US would build and operate code for Ireland, and in fact the developer platforms would be designed to hide differences between datacenters as much as possible.
If an Irish citizen logs into GMail in the US, they're not going to hit a frontend proxy in Ireland. Their data is going to be processed, and at least cached, by Google servers in the US.
Data having a geographical location is an incoherent concept in the context of the architectures of modern multinational tech companies. That much is obvious from simply reading their engineering blogs and whitepapers.
It would be a coherent legal standard (and one I favor) to say that an EU citizen's data is subject to EU protections regardless of where it's stored. It would also be coherent (and the one we unfortunately seem headed for) to say that anything an American employee can get over any remote access tool, he's required to hand over in response to a valid court order.
But pretending that data has a location is a weird hack, nowhere near as clear cut as your analogy suggests. Can you imagine, arguing in the courtroom over which member of a trans-continental Paxos group was master at the time a warrant was processed?
- pedrocr 9y agoI know the case was a massive simplification on the technical side, that was on purpose. It wasn't a simplification on the jurisdiction side though. Google does have a subsidiary in Ireland and so handing over the EU data does put you in that conundrum as you definitely are subject to Irish law when dealing with the data of Irish users. That you decided to architect your systems so that data is not geographically separate is your own problem.
- closeparen 9y agoTo my understanding, neither US nor EU law give a crap about the data's geography. And rightly so, because data doesn't have geography. EU privacy laws apply to all EU citizens, and US warrants apply to all US persons capable of facilitating them. The exception for US-owned databases in European datacenters was a bizarre, short-lived loophole created by case law which maps poorly onto the realities of the situations. I'd say it's the companies which have twisted themselves into knots to take advantage of this loophole, and expected that to be an enduring investment, which are having a problem.
- pedrocr 9y agoIn that case how do you propose US-based companies operate in Europe? If it's not possible to follow EU privacy laws because US courts can compell you to break them should Google/Facebook/Microsoft just leave the EU market?
- closeparen 9y agoWhat other choice do they have? With the "data lives in Europe" loophole ending, then yeah, the US will have to suffer the economic consequences of its failure to come to an agreement with the EU.
- pedrocr 9y agoI think there are two cases: 1. An AWS Ireland instance bought by a EU member: here the storage box analogy should apply fully. The data is indeed geographically located and being operated within that geography. US courts need to accept that they need to go through the local authorities to get a warrant for that data just like they would for any physical good. 2. A worldwide distributed database like the Facebook graph: here the analogy breaks down completely and the US courts are taking advantage of that to access anything they like. I'm sure their tune would change if suddenly the Chinese authorities forced the local Facebook subsidiary to hand over all the data of US citizens. For this the solution will need to be an international arbitration for data access. If the database is not geographically bound then the mechanism to ensure its privacy will have to be international as well. I think the Microsoft case was of type 1 and so new laws should not be needed. Cases of type 2 will be much harder and it may very well mean that Facebook becomes de facto illegal in Europe.
- bonesss 9y ago> In any realistic architecture, there are are a million exceptions to "this Irish user's data is stored in Ireland": offsite backups, cross-datacenter requests within backend systems, offline analytical stores, queries, derived tables, etc. ... Data having a geographical location is an incoherent concept in the context of the architectures of modern multinational tech companies. That much is obvious from simply reading their engineering blogs and whitepapers. Italicized for emphasis, because that's the part where one discussion attempts to diverge into two. It's true what you're saying, in exactly that one context: from the point of view of a multinational cloud provider there's a lot of different ingredients coming together to make "a" stew. For what the OP was discussing though: what you're saying is completely wrong. From the context of the Irish Government who is protecting sensitive personal data on Irish citizens and deciding how it, the Irish Government, and their related services should handle data, there is only one legally defensible position as of today: full control of the legal entities handling the data. The EU has very little legal sway outside the EU, there is no baked in legal reciprocity, and your suggestion for data handling laws fall woefully short of the real world issues (like... hate speech legislation, abortion politics, etc). You're thinking about GMail. The legislation is looking at something like the entirety Irish health services and handling sensitive individual research data. From that context the idea of having no data governance and relying on inadequate legal agreements directly contradicts expert opinion and legal requirements. Personal Identification Numbers do a lot to streamline public services, they also change the relative sensitivity of data at rest. Therefore the EU has decided that putting such data in an environment where something like Paxos would be relevant is a complete no-go. Data has a location until it is copied multiple places. The EU has decided they don't want any of those places to be outside their jurisdiction for the good of their citizens.
- closeparen 9y ago>You're thinking about GMail TFA is about GMail. >there is only one legally defensible position as of today: full control of the legal entities handling the data Absolutely! The GDPR does this, and it's perfectly coherent, in that it applies to all EU citizens' data, regardless of where the data is stored or processed. What's incoherent is the (former) US policy that data held by American companies is immune to search if and only if it's located outside the US. >Data has a location until it is copied multiple places Data are copied hundreds to thousands of times as they transit any network. Further, if data at rest are only stored in one place, the company storing it is dangerously irresponsible. HIPAA actually mandates backup and disaster recovery capabilities. The illegal thing would be having too few copies, or an architecture with a single point of failure. >The legislation is looking at something like the entirety Irish health services and handling sensitive individual research data Surely something this sensitive should not rely on the "one weird trick" that US companies are (sometimes? maybe?) not required to comply with court orders for data that they claim lives on EU soil.