4 ms·
Yeah, this is exactly correct and in line with the legal advice I received when working with GDPR-related features at a previous job. The relevant text is Artic
by whakim 5y ago
Yeah, this is exactly correct and in line with the legal advice I received when working with GDPR-related features at a previous job. The relevant text is Article 3 of the GDPR ("Territorial Scope"), and if you're not located in the EU and not clearly intending to offer goods and services to EU data subjects, then you're in the clear.
- XCSme 5y agoBut then isn't Google violating GDPR? Because they do provide goods and services to the EU. Or is the US Google a different company than the one that provides goods in the EU?
- whakim 5y agoIn this particular case, Google is considered the "data processor" (as opposed to GP's blog, which is the "data controller"). Google is certainly subject to the GDPR as a data processor in this case. That being said, the EDBP is clear in their guidelines that using a data processor established in the EU does not itself make the controller subject to the GDPR.